Skip to content
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

[Backport release-1.27] Add ControlNode deletion to docs on how to remove a controller node #3825

Merged
merged 1 commit into from
Dec 18, 2023

Conversation

k0s-bot
Copy link

@k0s-bot k0s-bot commented Dec 18, 2023

Automated backport to release-1.27, triggered by a label in #3823.
See .

There's nothing that would handle automatic removal of those objects,
currently. Documenting the manual deletion is the least we can do about
this.

Signed-off-by: Tom Wieczorek <[email protected]>
(cherry picked from commit 086b243)
(cherry picked from commit b9a02a0)
@k0s-bot k0s-bot requested a review from a team as a code owner December 18, 2023 12:15
@jnummelin jnummelin changed the title [Backport release-1.27] [Backport release-1.28] Add ControlNode deletion to docs on how to remove a controller node [Backport release-1.27] Add ControlNode deletion to docs on how to remove a controller node Dec 18, 2023
@jnummelin jnummelin added the backport/release-1.26 PR that needs to be backported/cherrypicked to release-1.26 branch label Dec 18, 2023
@ncopa ncopa merged commit c7f1c5e into release-1.27 Dec 18, 2023
6 checks passed
@ncopa ncopa deleted the backport-3823-to-release-1.27 branch December 18, 2023 12:54
@k0s-bot
Copy link
Author

k0s-bot commented Dec 18, 2023

Successfully created backport PR for release-1.26:

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backport/release-1.26 PR that needs to be backported/cherrypicked to release-1.26 branch
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants