Kubernetes Argo CD

Deploys Argo CD on Kubernetes using the official Argo Helm chart (argo-cd v7.7.12), with configurable resource limits for the server, controller, repo-server, and Redis components, optional namespace creation, and optional ingress for external browser access with automatic TLS certificate provisioning.

What Gets Created

When you deploy a KubernetesArgocd resource, OpenMCF provisions:

• Namespace — created only when createNamespace is true
• Helm Release (Argo CD) — deploys Argo CD from the argo-cd chart at https://argoproj.github.io/argo-helm, pinned to version 7.7.12, with atomic rollback enabled and a 10-minute timeout; configures resource requests/limits for the server, application controller, repo-server, and embedded Redis
• Ingress — when enabled, exposes the Argo CD server externally at the specified hostname with TLS termination via a cert-manager ClusterIssuer derived from the hostname's domain

Prerequisites

• Kubernetes credentials configured via environment variables or OpenMCF provider config
• A Kubernetes namespace that already exists, or set createNamespace to true
• cert-manager with a ClusterIssuer named after the parent domain (e.g., example.com) if enabling ingress with TLS
• An ingress controller running in the cluster if enabling external access

Quick Start

Create a file argocd.yaml:

apiVersion: kubernetes.openmcf.org/v1
kind: KubernetesArgocd
metadata:
  name: my-argocd
  labels:
    openmcf.org/provisioner: pulumi
    pulumi.openmcf.org/organization: my-org
    pulumi.openmcf.org/project: my-project
    pulumi.openmcf.org/stack.name: dev.KubernetesArgocd.my-argocd
spec:
  namespace: argocd
  createNamespace: true
  container: {}

Deploy:

openmcf apply -f argocd.yaml

This creates an Argo CD instance in the argocd namespace with default resource limits (1000m CPU / 1Gi memory limits, 50m CPU / 100Mi memory requests) and no external ingress. Access the UI locally with the port-forward command from stack outputs.

Configuration Reference

Required Fields

Optional Fields

Examples

Development Instance with Minimal Resources

A lightweight Argo CD instance for development or testing with reduced resource allocations:

apiVersion: kubernetes.openmcf.org/v1
kind: KubernetesArgocd
metadata:
  name: dev-argocd
  labels:
    openmcf.org/provisioner: pulumi
    pulumi.openmcf.org/organization: my-org
    pulumi.openmcf.org/project: my-project
    pulumi.openmcf.org/stack.name: dev.KubernetesArgocd.dev-argocd
spec:
  namespace: argocd-dev
  createNamespace: true
  container:
    resources:
      limits:
        cpu: "500m"
        memory: "512Mi"
      requests:
        cpu: "50m"
        memory: "64Mi"

Production Instance with Ingress

A production Argo CD deployment exposed externally with higher resource limits:

apiVersion: kubernetes.openmcf.org/v1
kind: KubernetesArgocd
metadata:
  name: prod-argocd
  labels:
    openmcf.org/provisioner: pulumi
    pulumi.openmcf.org/organization: my-org
    pulumi.openmcf.org/project: my-project
    pulumi.openmcf.org/stack.name: prod.KubernetesArgocd.prod-argocd
spec:
  namespace: argocd
  createNamespace: true
  container:
    resources:
      limits:
        cpu: "2000m"
        memory: "2Gi"
      requests:
        cpu: "250m"
        memory: "512Mi"
  ingress:
    enabled: true
    hostname: argocd.example.com

Using Foreign Key References

Reference an OpenMCF-managed namespace instead of hardcoding the name:

apiVersion: kubernetes.openmcf.org/v1
kind: KubernetesArgocd
metadata:
  name: platform-argocd
  labels:
    openmcf.org/provisioner: pulumi
    pulumi.openmcf.org/organization: my-org
    pulumi.openmcf.org/project: my-project
    pulumi.openmcf.org/stack.name: prod.KubernetesArgocd.platform-argocd
spec:
  namespace:
    valueFrom:
      kind: KubernetesNamespace
      name: platform-namespace
      field: spec.name
  container:
    resources:
      limits:
        cpu: "2000m"
        memory: "4Gi"
      requests:
        cpu: "500m"
        memory: "1Gi"
  ingress:
    enabled: true
    hostname: argocd.platform.example.com

Stack Outputs

After deployment, the following outputs are available in status.outputs:

Related Components

• KubernetesNamespace — provides the target namespace via valueFrom reference
• KubernetesDeployment — application deployments managed by Argo CD
• KubernetesHelmRelease — alternative for deploying Helm charts when full GitOps is not needed