Skip to content

[GEP-28] Use technicalID from Cluster instead of Worker.Namespace#265

Merged
Nuckal777 merged 1 commit intoironcore-dev:mainfrom
timebertt:gardenadm-worker
Nov 21, 2025
Merged

[GEP-28] Use technicalID from Cluster instead of Worker.Namespace#265
Nuckal777 merged 1 commit intoironcore-dev:mainfrom
timebertt:gardenadm-worker

Conversation

@timebertt
Copy link
Copy Markdown
Contributor

Proposed Changes

To support self-hosted shoots with managed infrastructure, the Worker controller/delegate needs to use the technical ID from Cluster.shoot.status.technicalID for prefixing the names of machine-related objects. The Worker namespace is kube-system for self-hosted shoots.
This PR is similar to gardener/gardener@22f4295 (#13485).

Part of gardener/gardener#13485


machineClassProviderSpec[metal.LabelsFieldName] = map[string]string{
metal.ClusterNameLabel: w.cluster.ObjectMeta.Name,
metal.ClusterNameLabel: w.cluster.Shoot.Status.TechnicalID,
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This seems unrelated?

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

So far, w.cluster.ObjectMeta.Name has always been the technical ID (shoot--foo--bar). Now, it could also be kube-system for self-hosted shoots with managed infrastructure. So, I assume that the label value should keep its value – also if you ever want to bootstrap self-hosted shoots :)

@Nuckal777 Nuckal777 merged commit 8568ed6 into ironcore-dev:main Nov 21, 2025
9 checks passed
@github-project-automation github-project-automation bot moved this to Done in Roadmap Nov 21, 2025
@timebertt timebertt deleted the gardenadm-worker branch November 21, 2025 15:37
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

Status: Done

Development

Successfully merging this pull request may close these issues.

3 participants