Learn how to connect an Argo CD instance on Azure Kubernetes Service to a self-hosted Octopus Deploy server

Octopus Deploy Blog offers insights, tutorials, and updates on DevOps, continuous delivery, and infrastructure automation. Covering topics such as deployment pipelines, release management, and configuration management, Octopus Deploy Blog provides resources for DevOps engineers and software teams. Developers can learn about automating deployments, managing infrastructure as code, and implementing CI/CD practices through Octopus Deploy's blog posts and case studies.

OctopusDeploy

Connecting Argo CD on Azure Kubernetes Service to a self-hosted Octopus Deploy server requires specific networking configuration. Key steps include retrieving the cluster's outbound IP address for firewall rules, opening ports 443 (for initial API registration) and 8443 (for gRPC communication), and handling DNS resolution through custom ConfigMaps. For high-availability setups with load balancers, HTTP/2 support must be enabled on port 8443. Additional configuration is needed for local Certificate Authorities, requiring base64-encoded root CA certificates in Helm chart overrides.

Connecting an AKS Argo CD instance to a self-hosted Octopus Deploy server