From 7cce254d78e755c7e87aab066c7495d409acb57b Mon Sep 17 00:00:00 2001 From: Trent Mohay Date: Thu, 29 Jan 2026 15:39:29 +1100 Subject: [PATCH 1/2] add warning for name-uniqueness --- src/pages/docs/argo-cd/instances/index.md | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/src/pages/docs/argo-cd/instances/index.md b/src/pages/docs/argo-cd/instances/index.md index 0a36c4f4be..2930fd41fa 100644 --- a/src/pages/docs/argo-cd/instances/index.md +++ b/src/pages/docs/argo-cd/instances/index.md @@ -56,6 +56,11 @@ kubectl config view ::: 1. Enter the unique name for the instance. This name is used to generate the Kubernetes namespace, as well as the Helm release name. + + :::div{.warning} + The gateway's name must be unique across all spaces in your Octopus Deploy instance. Otherwise the existing gateway's settings will be overwritten, causing deployment failures. + ::: + 2. Select at least one [environment](https://octopus.com/docs/infrastructure/environments) the instance will be responsible for servicing. 3. If required, change the [in-cluster](https://kubernetes.io/docs/concepts/services-networking/dns-pod-service/#services) URL of the Argo CD API Server service. In many cases the default value provided will work. 4. Optionally, add the URL used to access Argo CD's web frontend. This will be used for linking from Octopus to Argo CD to aid with deployment investigations. From 4a3e00c47f200d8d90e270171f86f414ffba50e3 Mon Sep 17 00:00:00 2001 From: Trent Mohay Date: Thu, 29 Jan 2026 15:51:34 +1100 Subject: [PATCH 2/2] try and fix lint --- src/pages/docs/argo-cd/instances/index.md | 8 +++----- 1 file changed, 3 insertions(+), 5 deletions(-) diff --git a/src/pages/docs/argo-cd/instances/index.md b/src/pages/docs/argo-cd/instances/index.md index 2930fd41fa..777a51357d 100644 --- a/src/pages/docs/argo-cd/instances/index.md +++ b/src/pages/docs/argo-cd/instances/index.md @@ -56,11 +56,9 @@ kubectl config view ::: 1. Enter the unique name for the instance. This name is used to generate the Kubernetes namespace, as well as the Helm release name. - - :::div{.warning} - The gateway's name must be unique across all spaces in your Octopus Deploy instance. Otherwise the existing gateway's settings will be overwritten, causing deployment failures. - ::: - + :::div{.warning} + The gateway's name must be unique within a cluster. Otherwise the existing gateway's settings will be overwritten, causing deployment failures. + ::: 2. Select at least one [environment](https://octopus.com/docs/infrastructure/environments) the instance will be responsible for servicing. 3. If required, change the [in-cluster](https://kubernetes.io/docs/concepts/services-networking/dns-pod-service/#services) URL of the Argo CD API Server service. In many cases the default value provided will work. 4. Optionally, add the URL used to access Argo CD's web frontend. This will be used for linking from Octopus to Argo CD to aid with deployment investigations.