Repository navigation
[Backport release-1.6] fix(kubernetes): break bootstrap-token Job out of Helm hook to unblock fresh installs - #4541
Merged
myasnikovdaniil merged 1 commit intoOct 16, 2026
Conversation
…k fresh installs Backport of #3887 to release-1.6. The fix reached main only, so every 1.6 release still ships the Job as a post-install/post-upgrade hook and hits the deadlock #3875 describes: the chart upgrade waits for MachineDeployment and the child HelmReleases, workers cannot register without the bootstrap-token Secret, and the hook that creates that Secret only runs once the wait has already succeeded. The wait cannot succeed without nodes, so the upgrade times out and Flux retries the same cycle indefinitely. This is deterministic rather than flaky, and it takes out every tenant Kubernetes cluster on the platform at once. Anyone reading the tracker finds #3875 closed, upgrades to 1.6.4 expecting the fix, and lands in the same state, which is why this backport matters more than the usual one. (cherry picked from commit adc9c56) Assisted-by: LLM Signed-off-by: IvanHunters <[email protected]>
Contributor
|
Important Review skippedAuto reviews are disabled on base/target branches other than the default branch. Please check the settings in the CodeRabbit UI or the ⚙️ Run configuration
You can disable this status message by setting the Use the checkbox below for a quick retry:
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
IvanHunters
marked this pull request as ready for review
October 6, 2026 19:13
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 join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
What this PR does
Backports #3887 to
release-1.6. The fix reachedmainonly:v1.6.3andv1.6.4both still ship the bootstrap-token Job as apost-install,post-upgradeHelm hook, andgit tag --containson the merge commit returnsv1.7.0-alpha.1and nothing from the 1.6 line. Tracked as #4539.#3875 describes the deadlock this removes: the chart upgrade waits for
MachineDeploymentand the child HelmReleases, workers cannot register without thebootstrap-token-<id>Secret in the guest cluster, and the hook that creates that Secret only runs once the wait has already succeeded. The wait cannot succeed without nodes, so the upgrade times out and Flux retries the same cycle indefinitely.It is deterministic rather than flaky, and it takes out every tenant Kubernetes cluster on the platform at once. What makes the backport worth filing separately: anyone hitting this on 1.6.3 finds #3875 closed in the tracker, upgrades to 1.6.4 expecting the fix, and lands in exactly the same state.
Observed on a production cluster before the manual workaround: machines stuck in
Provisionedwith noNODENAME, VMIsRunningwith IPs assigned, guest clusters reportingNo resources foundfor nodes, and no bootstrap-token Secret anywhere in the guestkube-system. Creating the Secret by hand brought nodes up within 90 seconds on each affected tenant.git cherry-pick --mainline 1of the merge commit applied cleanly with no conflicts, and nothing was changed on top: the diff here is identical to what merged onmain.Validation,
helm unittestinpackages/apps/kubernetesincludingtests/talos_templates_test.yamlwhich this change extends:Screenshots
Not applicable, no UI changes.
Downstream repositories
Release note