From 1a60381767c195e2eed6274fc8859d20bdb295b0 Mon Sep 17 00:00:00 2001 From: Stephen Levine Date: Mon, 5 Jan 2026 15:16:57 -0500 Subject: [PATCH 1/2] Document support for kube canaries in Managed Updates --- docs/pages/reference/deployment/managed-updates-v2.mdx | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/docs/pages/reference/deployment/managed-updates-v2.mdx b/docs/pages/reference/deployment/managed-updates-v2.mdx index 2f222deb42edd..5988fc5f01015 100644 --- a/docs/pages/reference/deployment/managed-updates-v2.mdx +++ b/docs/pages/reference/deployment/managed-updates-v2.mdx @@ -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, rollback both the agent and tbot, and fail the canary. **Example configuration:** From c97ca2dd34beb9675cdec354d25b9b095175b593 Mon Sep 17 00:00:00 2001 From: Stephen Levine Date: Tue, 6 Jan 2026 13:04:15 -0500 Subject: [PATCH 2/2] Update docs/pages/reference/deployment/managed-updates-v2.mdx Co-authored-by: Paul Gottschling --- docs/pages/reference/deployment/managed-updates-v2.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/pages/reference/deployment/managed-updates-v2.mdx b/docs/pages/reference/deployment/managed-updates-v2.mdx index 5988fc5f01015..0ac1ec1b9708b 100644 --- a/docs/pages/reference/deployment/managed-updates-v2.mdx +++ b/docs/pages/reference/deployment/managed-updates-v2.mdx @@ -213,7 +213,7 @@ of a failed update that might not be caught by earlier groups due to environment - Subsequent groups will not be updated until the group successfully updates. - 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, rollback both the agent and tbot, and fail the canary. + alongside tbot to detect tbot update failures, roll back both the agent and tbot, and fail the canary. **Example configuration:**