docs(DOC-1618): restore k8s compatibility known issue and add troubleshooting page#2388
Merged
Merged
Conversation
…shooting page PR #2228 accidentally dropped the known-issue warning for 1.34+ control plane clusters paired with older tenant clusters. Restores it for the combinations affected by the pod Ready=False sync bug (ENGNODE-105 / vcluster#3578) and adds a troubleshooting page documenting symptoms, cause, and fix status. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
✅ Deploy Preview for vcluster-docs-site ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
Contributor
Contributor
djwfyi
added
backport-v0.34
The observedGeneration bug (ENGNODE-105 / vcluster#3578) is gated on tenant version < 1.34, not simply "older than host". Narrow the known-issue marker to the tenant=1.33 column across the 1.34/1.35/1.36 host rows, matching engineering's confirmed compatibility table. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
The note and troubleshooting page said the bug hits any tenant older than the control plane, which overstates the actual gate confirmed in vcluster PR #4037: tenant on 1.33 or earlier with control plane on 1.34 or later. Tighten the wording accordingly. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
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
2 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.
Content Description
Adds the "Known issues" warning in the Kubernetes compatibility matrix for 1.34+ control plane clusters paired with an older tenant cluster (1.33 or 1.34). The warning now points at the actual bug hitting these version combinations today: pods stuck at
Ready=Falsedue to a QoS class immutability issue and anobservedGenerationmismatch (tracked upstream in vcluster#3578, fix in progress in vcluster#4037).Also adds a new troubleshooting page documenting the symptoms, root cause, and current workaround/fix status, and points the matrix footnote at it.
Preview Link
Internal Reference
Closes DOC-1618
Also tracked in ENGNODE-105.
AI review: mention
@claudein a comment to request a review or changes. See CONTRIBUTING.md for available commands.@netlify /docs