[pull] master from gardener:master - #1891
Merged
Merged
Conversation
* Skip automatic etcdEncryptionKey rotation for hibernated shoots * Prefactor: hibernationutils * Add HibernationScheduleProblematic constraint * check conflicts only during the next maintenance * Adress PR Feedback * Rename automatic rotation constraint Assisted-by: OpenCode (gpt-5.6-terra) * Report all blocked automatic rotations Assisted-by: OpenCode (gpt-5.6-terra) * Add rotation period helper tests Assisted-by: OpenCode (github-copilot/gpt-5.6-luna) --------- Co-authored-by: Tim Ebert <timebertt@gmail.com>
* Make `rebootstrap-gardenlet.sh` work for shoot `gardenlet`s as well Previously, this only worked for seed gardenlets, but shoot gardenlets might also need to get rebootstrapped (e.g., in case their client certificate expired for whatever reason). Assisted-by: Claude <claude@anthropic.com> Signed-off-by: rfranzke <rafael.franzke@sap.com> * Support `gardener.cloud/operation=renew-kubeconfig` on self-hosted shoot `Gardenlet`s Previously, this didn't work and the `gardenlet` was failing and crash-looping eventually. Assisted-by: Claude <claude@anthropic.com> Signed-off-by: rfranzke <rafael.franzke@sap.com> * Renew kubeconfig of shoot `Gardenlet`s when rotating garden cluster CA During a garden cluster CA rotation, the gardener-operator already annotates seed `Gardenlet`s to trigger kubeconfig renewal. Extend this to shoot `Gardenlet`s (those with the `self-hosted-shoot-` name prefix) by annotating them with `gardener.cloud/operation=renew-kubeconfig`. Assisted-by: Claude <claude@anthropic.com> Signed-off-by: rfranzke <rafael.franzke@sap.com> * Address PR review feedback Signed-off-by: rfranzke <rafael.franzke@sap.com> --------- Signed-off-by: rfranzke <rafael.franzke@sap.com>
…riggering seed reconciliation (#15437) * Ensure global observability secret is synced before seed reconciliation Commit `d393a96` added rotation for the global observability ingress secret. However, it missed a race condition that is only visible in real Gardener landscapes. The rotation assumes the following order: t0: The secrets manager generates a new global observability ingress secret in the runtime cluster and copies it to the `garden` namespace in the virtual garden cluster. t1: The gardener-controller-manager (GCM) sees the new secret in the `garden` namespace and propagates it to each seed namespace. t2: The gardener-operator annotates the seeds for reconciliation. t3: The gardenlet picks up and deploys the new global observability ingress secret in the seed. This path works, but t1 and t2 swap if the gardener-operator triggers seed reconciliation before the GCM copies the new secret to the corresponding seed namespaces. This commit propagates the `last-rotation-initiation-time` label to the secret replicas, and adds a step to the gardener-operator rotation flow between t1 and t2. The step blocks until every seed namespace in the virtual garden holds a replica whose `last-rotation-initiation-time` is greater than or equal to the one on the original secret in the runtime cluster. This enforces the t1-before-t2 ordering: the operator does not annotate the seeds until the GCM has finished propagating the new secret. * Deduplicate secret creation in observability rotation tests The tests that exercise empty and non-numeric `last-rotation-initiation-time` label values inlined the full secret creation. This adds a string-based helper that carries the label value as a string.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
4 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
See Commits and Changes for more details.
Created by
pull[bot] (v2.0.0-alpha.4)
Can you help keep this open source service alive? 💖 Please sponsor : )