Skip to content

[v18] Document support for kube canaries in Managed Updates #62780

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.

Sign up for GitHub

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

Merged
sclevine merged 2 commits into from
Jan 13, 2026
Merged

[v18] Document support for kube canaries in Managed Updates #62780

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
1a60381
Document support for kube canaries in Managed Updates
sclevine Jan 5, 2026
c97ca2d
Update docs/pages/reference/deployment/managed-updates-v2.mdx
sclevine Jan 6, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 4 additions & 4 deletions docs/pages/reference/deployment/managed-updates-v2.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -208,12 +208,12 @@ of a failed update that might not be caught by earlier groups due to environment

**Key characteristics:**

- Up to five Linux agent hosts are selected automatically and updated first.
- Up to five total Linux and Kubernetes agents are randomly selected and updated first.
- If any canary fails to update, the group is marked as failed and not updated.
- Subsequent groups will not be updated until the group successfully updates.
- Kubernetes agents are not currently selected as canaries.
- tbot-only installations are not selected as canaries, but agents may be deployed
alongside tbot to detect tbot update failures.
- Linux and Kubernetes agents can be placed in separate groups to ensure both are covered by canaries.
- tbot-only installations are not selected as canaries. However, agents may be deployed
alongside tbot to detect tbot update failures, roll back both the agent and tbot, and fail the canary.

**Example configuration:**

Expand Down
Loading