docs: gossip removal in kOps 1.37 and migration guide - #18651
Merged
Merged
Conversation
Member
Author
|
/cc @upodroid |
Update the gossip docs for the removal that shipped in kOps 1.37, with the deprecation and removal timeline, the changes shipped in kOps 1.36, and a step-by-step guide for migrating existing gossip clusters to None-DNS using kOps 1.36 before upgrading. Note that nodes no longer install or run protokube, and that the gossipConfig and dnsControllerGossipConfig cluster spec fields are deprecated, have no effect, and are rejected by validation when set. Align the 1.36 release notes with the removal plan from kubernetes#18240, use None-DNS wording in the docs that still described clusters as created without DNS, and remove the outdated AWS China guide, which documented kOps 1.10 procedures and is superseded by the None-DNS support in the getting started guide.
Member
|
/lgtm |
rifelpet
approved these changes
Jul 31, 2026
Contributor
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: rifelpet The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
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
3 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.
Update the gossip docs for the removal that shipped in kOps 1.37, with the deprecation and removal timeline, the changes shipped in kOps 1.36, and a step-by-step guide for migrating existing gossip clusters to None-DNS using kOps 1.36 before upgrading. Note that nodes no longer install or run protokube, and that the gossipConfig and dnsControllerGossipConfig cluster spec fields are deprecated, have no effect, and are rejected by validation when set.
Align the 1.36 release notes with the removal plan from #18240, use None-DNS wording in the docs that still described clusters as created without DNS, and remove the outdated AWS China guide, which documented kOps 1.10 procedures and is superseded by the None-DNS support in the getting started guide.
/cc @rifelpet @ameukam