Skip to content

dynamic resource allocation: use generated name for ResourceClaim from template #113722

Closed
@pohly

Description

@pohly

What would you like to be added?

Right now, the name is specified as <pod name>-<claim source name inside pod spec>. That's easy and deterministic, but may lead to conflicts with ResourceClaims that were created earlier, either automatically or manually.

Let's investigate the alternative: generate the name and let code which needs to know it search the API server or in a local cache via some label.

Why is this needed?

Avoids conflicts.

Metadata

Metadata

Assignees

No one assigned

    Labels

    kind/featureCategorizes issue or PR as related to a new feature.priority/backlogHigher priority than priority/awaiting-more-evidence.sig/nodeCategorizes an issue or PR as relevant to SIG Node.triage/acceptedIndicates an issue or PR is ready to be actively worked on.

    Type

    No type

    Projects

    Status

    ✅ Done

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions