feat: update Argo CD Gateway installation instructions and add Terraform bootstrap guide by ATGardner · Pull Request #3043 · OctopusDeploy/docs

ATGardner · 2026-03-02T06:48:26Z

related to this ticket

src/pages/docs/argo-cd/instances/terraform-bootstrap.md

steve-fenton-octopus

Hey @ATGardner

I've suggested using headings to visually separate the code blocks. Headings automatically provide bookmarks, though you can also control them if you want to:

## My heading

## My second example {#bookmark-name}

ATGardner · 2026-03-02T08:22:26Z

Hey @ATGardner

I've suggested using headings to visually separate the code blocks. Headings automatically provide bookmarks, though you can also control them if you want to:
## My heading

## My second example {#bookmark-name}

i committed all your suggestions @steve-fenton-octopus

steve-fenton-octopus

Ace! Thanks for the changes.

flin-8 · 2026-03-03T04:24:31Z

src/pages/docs/argo-cd/instances/argo-user.md

 The RBAC policies are stored within the `argocd-rbac-cm` configmap.

-The following shows an Octopus user which has read only access to all applications, cluster and log data.
+The following shows an Octopus user which has read only access to all applications, cluster and log data, and sync permissions for applications.


Can you also update the modDate for this file please 🙇

flin-8 · 2026-03-03T04:31:16Z

src/pages/docs/argo-cd/instances/terraform-bootstrap.md

+
+# ─── Octopus Deploy ───────────────────────────────────────────────────────────
+octopus_api_url  = "https://my-instance.octopus.app"
+octopus_grpc_url = "my-instance.octopus.app:443"


From memory the gRPC port is 8443

good catch. thanks.

flin-8

LGTM + comments

ATGardner · 2026-03-03T08:47:21Z

i am still waiting for this pr to be merged first, because without it, deploying with an argo cd application actually fails (the registration pod works, but the gateway pod fails to start, due to an issue with the certificates secret).
once it is merged, probably as chart 1.19.0, i'll update the samples to use it. otherwise customers might copy-paste the current example, and things will just not work for them out-of-the-box.

ATGardner · 2026-03-26T16:36:19Z

src/pages/docs/argo-cd/instances/terraform-bootstrap.md

+
+  manifest = {
+    apiVersion = "argoproj.io/v1alpha1"
+    kind       = "Application"


this doesn't work right now, because at the terraform plan stage there is no Application crd available in the cluster.
it might be fixed using something like

# Step 1 — bootstrap Argo CD terraform apply -target=helm_release.argocd -target=time_sleep.wait_for_argocd # Step 2 — deploy everything else terraform apply

but do we want to go there?

Slack conversation: https://octopusdeploy.slack.com/archives/C08QKUX0LHW/p1772416095932619

flin-8 · 2026-03-30T23:26:47Z

src/pages/docs/argo-cd/instances/terraform-bootstrap.md

+        --insecure \
+        --grpc-web
+
+      echo ">>> Generating API token for the octopus account..."


We recommend customers create a new user, so we should add a new uers here (if easy), or add comments in the script to say customers should create a new user for production use.

the template is already creating the octopus user, and uses that user to create the apikey

https://github.com/OctopusDeploy/docs/pull/3043/changes#diff-d423956430ef3f8733afeb6fddf1ceb7cc3dd5630455f07a5d59d19cfbb88153R185

Ah my bad - I didn't read properly...

flin-8

LGTM

…orm bootstrap guide

Co-authored-by: Steve Fenton <99181436+steve-fenton-octopus@users.noreply.github.com>

- Update modification date to March 3, 2026. - Revise installation steps to include namespace creation and token generation. - Provide detailed YAML configuration for Argo CD application.

…ount Create a dedicated "octopus" service account with API key capability and necessary permissions for Octopus Deploy. This change ensures that the admin account retains login-only access, allowing the bootstrap script to generate the octopus token without interactive login requirements.

Add a new resource to deploy the Octopus Argo CD Gateway using Argo CD's application management, allowing Argo CD to manage the Helm lifecycle. This change ensures better integration and management of the gateway installation process.

Updated the modification dates in 'argo-user.md' and 'terraform-bootstrap.md' to ensure they reflect the correct timeline. This improves clarity and accuracy in the documentation.

…bles Clarify the process for installing Argo CD and the Argo CD Gateway by specifying the provisioning of required token secrets. Remove unnecessary variables related to the gateway name and chart version to streamline the configuration.

ATGardner self-assigned this Mar 2, 2026