Merge branch 'main' into DOCSS-1857-remove-h5-6

rosieyohannan · web-flow · commit 884f206d0add · 2025-09-10T09:40:43.000+01:00
diff --git a/docs/guides/modules/deploy/pages/configure-deploy-markers.adoc b/docs/guides/modules/deploy/pages/configure-deploy-markers.adoc
@@ -78,6 +78,8 @@ This configuration would yield a value with the following format `12345`.
 
 === 1.2. Update the deploy status to running
 
+WARNING: The `circleci run release update` command is only for use with deploy markers. If you are using the CircleCI xref:release-agent-overview.adoc[release agent] for Kubernetes deployments, do NOT use the `update` commands. The release agent automatically handles status updates for you.
+
 After deploying your application, you can update the status of the deployment to `RUNNING` by running the `circleci run release update` command in a new step.
 
 [,yml]
diff --git a/docs/guides/modules/deploy/pages/configure-your-kubernetes-components.adoc b/docs/guides/modules/deploy/pages/configure-your-kubernetes-components.adoc
@@ -126,6 +126,8 @@ Substitute the placeholders above based on your application's details:
 +
 CAUTION: If you are using Argo Rollouts for a given component, be sure to set the `release-strategy` parameter to `progressive`.
 
+WARNING: The `circleci run release update` command is only for use with deploy markers. If you are using the CircleCI xref:release-agent-overview.adoc[release agent] for Kubernetes deployments, do NOT use the `update` commands. The release agent automatically handles status updates for you.
+
 . Define a new job to monitor the release, referencing the `release plan` created above as part of the _deployment_ job:
 +
 [,yaml]
diff --git a/docs/guides/modules/toolkit/pages/environment-cli-usage-guide.adoc b/docs/guides/modules/toolkit/pages/environment-cli-usage-guide.adoc
@@ -156,6 +156,8 @@ For more information on using the `circleci run release plan` command, see the x
 
 ==== Update
 
+WARNING: The `circleci run release update` command is only for use with deploy markers. If you are using the CircleCI xref:deploy:release-agent-overview.adoc[release agent] for Kubernetes deployments, do NOT use the `update` commands. The release agent automatically handles status updates for you.
+
 A subcommand of `release`. Use the `circleci run release update` command to update the status of the deployment.
 
 *Flags*

Original file line number	Diff line number	Diff line change
`@@ -126,6 +126,8 @@ Substitute the placeholders above based on your application's details:`
`126`	`126`	`+`
`127`	`127`	CAUTION: If you are using Argo Rollouts for a given component, be sure to set the `release-strategy` parameter to `progressive`.
`128`	`128`
	`129`	+WARNING: The `circleci run release update` command is only for use with deploy markers. If you are using the CircleCI xref:release-agent-overview.adoc[release agent] for Kubernetes deployments, do NOT use the `update` commands. The release agent automatically handles status updates for you.
	`130`	`+`
`129`	`131`	. Define a new job to monitor the release, referencing the `release plan` created above as part of the _deployment_ job:
`130`	`132`	`+`
`131`	`133`	`[,yaml]`