Skip to content

ArgoCD: Add warning regarding gateway name uniqueness #3019

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
rain-on merged 2 commits into from
Jan 29, 2026
Merged

ArgoCD: Add warning regarding gateway name uniqueness #3019

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
7cce254
add warning for name-uniqueness
rain-on Jan 29, 2026
4a3e00c
try and fix lint
rain-on Jan 29, 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
3 changes: 3 additions & 0 deletions src/pages/docs/argo-cd/instances/index.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -56,6 +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 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.
Expand Down