Deploying Container Observability frontend and backend

Use this method when you want to deploy the frontend by running Helm commands manually from the command line. You control the chart version, values file, and release lifecycle yourself, which is useful for ad‑hoc installs, troubleshooting, or simple environments without GitOps.

helm upgrade --install opscruise-frontend virtana-repo/virtana-co-controller \
  --namespace <first_8_chars_of_org_ID>-frontend --create-namespace \
  --set tags.frontend=true \
  -f <ORG_ID>-common-values.yaml \
  --version <LATEST_VERSION>

Use this approach to manage frontend deployment declaratively through GitOps with Argo CD Applications. Argo CD continuously reconciles the desired state from your Git repository, automatically handling upgrades, rollbacks, drift correction, and namespace creation for the frontend stack. Create a file named virtana-dp-frontend-argo.yaml and apply it to your Argo CD controller. Ensure you set the tags.frontend parameter to true.

apiVersion: argoproj.io/v1alpha1
kind: Application
metadata:
  name: virtana-dp-frontend
  namespace: argocd
  finalizers:
    - resources-finalizer.argocd.argoproj.io
spec:
  destination:
    server: https://kubernetes.default.svc
    namespace: <first_8_chars_of_org_ID>-frontend
  source:
    chart: virtana-co-controller
    repoURL: https://virtana.gitlab.io/helm-charts
    targetRevision: <LATEST_VERSION> 
    helm:
      releaseName: opscruise-frontend
      parameters:
        - name: "tags.frontend"
          value: "true"
      values: |
        <contents of ORG_ID-common-values.yaml>
  syncPolicy:
    automated:
      prune: true
      selfHeal: true
    syncOptions:
      - CreateNamespace=true

Use this option when you want to provision and manage the frontend as part of a broader, infrastructure‑as‑code workflow. Terraform drives the Helm release, enabling you to version, parameterize, and automate frontend deployments alongside other platform resources in a single, repeatable pipeline. Define a helm_release resource in your Terraform configuration (for example, virtana-dp-frontend.tf). Set the tags.frontend value to true.

resource "helm_release" "frontend" {
  create_namespace = true
  chart            = "virtana-co-controller"
  name             = "opscruise-frontend"
  namespace        = "${substr(var.org_id, 0, min(length(var.org_id), 8))}-frontend"
  repository       = "https://virtana.gitlab.io/helm-charts"
  version          = var.helm_version
  timeout          = 600
  wait             = true

  values = [
    templatefile("${path.module}/../values/ORG_ID-common-values.yaml", {
      deployment_mode       = "VP_ONPREM"
      storage_class         = var.storage_class
      docker_password       = var.docker_password
      docker_username       = var.docker_username
      frontend_dns          = "${var.org_id}-oc-${var.cp_endpoint}"
      tenant_name           = var.tenant_name
      ui_parent_app_url     = var.ui_parent_app_url
      keycloak_hostname     = var.keycloak_hostname
      keycloak_password     = var.keycloak_password
      keycloak_username     = var.keycloak_username
      global_view_hostname  = var.global_view_hostname
    })
  ]

  set {
    name  = "tags.frontend"
    value = "true"
  }
}

Enter the following command to deploy a CO backend instance. This approach is well-suited for quick, ad-hoc deployments or environments where a full GitOps or IaC pipeline is not yet in place.

helm upgrade --install opscruise-backend virtana-repo/virtana-co-controller \
  --namespace <CLUSTER_NAME> --create-namespace \
  --set tags.backend=true \
  -f <ORG_ID>-common-values.yaml \
  -f <ORG_ID>-<CLUSTER_NAME>-values.yaml \
  --version <LATEST_VERSION>

You can use this approach to manage each backend instance declaratively through an Argo CD Application custom resource. The manifest points to the virtana-co-controller Helm chart, sets tags.backend=true, and inlines the merged contents of both the common and per-cluster values files. Create a file named virtana-dp-CLUSTER_NAME-argo.yaml and apply it to your Argo CD controller. Ensure you set the tags.backend parameter to true.

apiVersion: argoproj.io/v1alpha1
kind: Application
metadata:
  name: virtana-dp-CLUSTER_NAME
  namespace: argocd
  finalizers:
  - resources-finalizer.argocd.argoproj.io
spec:
  destination:
    server: "https://kubernetes.default.svc"
    namespace: <CLUSTER_NAME>
  source:
    chart: virtana-co-controller
    repoURL: "https://virtana.gitlab.io/helm-charts"
    targetRevision: <LATEST_VERSION> 
    helm:
      releaseName: opscruise-backend
      parameters:
        - name: "tags.backend"
          value: "true"
      values: |
        <contents of ORG_ID-common-values.yaml + ORG_ID-CLUSTER_NAME-values.yaml>
  syncPolicy:
    automated:
      prune: true
      selfHeal: true
    syncOptions:
    - CreateNamespace=true

You can use this option to provision and manage each CO backend instance as part of a broader infrastructure-as-code workflow using Terraform's helm_release resource. Terraform renders two values files via templatefile, the shared ORG_ID-common-values.yaml for global settings and a per-cluster ORG_ID-CLUSTER_NAME-values.yaml for cluster-specific parameters like machine type and cluster name, and merges them in order before passing them to Helm.

Define a helm_release resource in your Terraform configuration (for example, virtana-dp-backend.tf). Set the tags.backend value to true.

resource "helm_release" "backend" {
  create_namespace = true
  chart            = "virtana-co-controller"
  name             = "opscruise-backend"
  namespace        = var.cluster_name
  repository       = "https://virtana.gitlab.io/helm-charts"
  version          = var.helm_version
  timeout          = 1200
  wait             = true

  values = [
    templatefile("${path.module}/../values/ORG_ID-common-values.yaml", {
      deployment_mode       = "VP_ONPREM"
      storage_class         = var.storage_class
      docker_password       = var.docker_password
      docker_username       = var.docker_username
      frontend_dns          = "${var.org_id}-oc-${var.cp_endpoint}"
      tenant_name           = var.tenant_name
      ui_parent_app_url     = var.ui_parent_app_url
      keycloak_hostname     = var.keycloak_hostname
      keycloak_password     = var.keycloak_password
      keycloak_username     = var.keycloak_username
      global_view_hostname  = var.global_view_hostname
    }),
    templatefile("${path.module}/../values/ORG_ID-CLUSTER_NAME-values.yaml", {
      machine_type = var.machine_type
      cluster_name = var.cluster_name
    })
  ]

  set {
    name  = "tags.backend"
    value = "true"
  }
}