-
Notifications
You must be signed in to change notification settings - Fork 525
[GEP-28] Prepare Shoot
control plane namespace to be different from its technical ID
#11382
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[GEP-28] Prepare Shoot
control plane namespace to be different from its technical ID
#11382
Conversation
eb1d7dd
to
ac2f102
Compare
/assign |
/assign |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice PR, only nits from my side. Otherwise lgtm
ac2f102
to
c995224
Compare
770a895
to
230a755
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for improving the names. It will hopefully make the code easier to understand in both autonomous as well as ordinary shoot cluster scenarios.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks!
/lgtm
LGTM label has been added. Git tree hash: 5f5a26620cc31c15356acc1fab54d5a949b3e7f9
|
- to make it very clear for the autonomous case - in the future, this is no longer necessarily the same as the technical ID of the shoot (at least for ASCs)
- in order to mark a Shoot as "autonomous", there must be exactly one pool that sets the controlPlane field - currently, it's not allowed to set this (we are not there yet) - for gardenadm bootstrapping, the Shoot manifest is read via file, i.e., validation is not called (at least for now, otherwise we have to introduce a feature gate, let's see how it goes)
The control plane namespace for ASCs will be `kube-system`, otherwise we'll fall back to the technical ID.
or make them more clear
- gardenlet and gardener-operator always run in the cluster like garden/shoot, so there is no need to make a DNS lookup - they can always use the cluster-internal kubeconfig
f796187
to
1376d0f
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/lgtm
/approve
LGTM label has been added. Git tree hash: 86f9dc366abc39f2c756343aa91f5019eef1955c
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: ScheererJ The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
/retest |
@rfranzke: The following test failed, say
Full PR test history. Your PR dashboard. Command help for this repository. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here. |
How to categorize this PR?
/area ipcei
/kind enhancement
What this PR does / why we need it:
Shoot.SeedNamespace
toShoot.ControlPlaneNamespace
.spec.provider.workers[].controlPlane
inShoot
API.status.technicalID
Which issue(s) this PR fixes:
Part of #2906
Special notes for your reviewer:
/cc @timebertt @ScheererJ
Release note: