Skip to main content

Installing IOMETE with Argo CD

Argo CD installs the IOMETE Helm chart without access to your cluster, so a few things a Helm install creates on its own are created once by a cluster administrator instead.

Supported Versions

Argo CD is supported on chart versions after 4.0.2. Earlier versions aren't supported.

Installing​

  1. Follow the On-Premises Deployment Guide up to and including Prepare Your Values File.

  2. Create a Secret for your credentials, so none of them sit in the Argo CD Application:

    kubectl create secret generic iomete-credentials -n iomete-system \
    --from-literal=db-password='<database password>' \
    --from-literal=db-admin-password='<database admin password>' \
    --from-literal=storage-secret-key='<object storage secret key>'

    Leave out storage-secret-key unless you use S3-compatible storage.

  3. Add these lines to your values file, and remove any passwords or keys from it:

    example-data-plane-values.yaml
    argocd: true
    serviceAccount:
    create: true
    crds:
    create: false
    webhook:
    create: false

    database:
    passwordSecret:
    name: iomete-credentials
    key: db-password
    adminCredentials:
    user: postgres
    passwordSecret:
    name: iomete-credentials
    key: db-admin-password

    # S3-compatible storage only
    storage:
    type: s3_compatible
    s3CompatibleSettings:
    endpoint: "<object storage endpoint>"
    accessKey: "<object storage access key>"
    secretKeySecret:
    name: iomete-credentials
    key: storage-secret-key

    On AWS S3, Google Cloud Storage or Azure, keep your existing storage block instead. Azure's storage account key stays in the values file, since the chart has no Secret form for it.

    If your values file has minioSettings, move its endpoint and access key into s3CompatibleSettings and delete minioSettings. The chart ignores it once s3CompatibleSettings is set.

    With workload identity (EKS, GKE or Azure), the init job runs as iomete-data-plane-init under Argo CD. Have the cloud side trust system:serviceaccount:iomete-system:iomete-data-plane-init as well as lakehouse-service-account, or the init job fails with a 403 on storage.

    The chart generates its own encryption key, tokens and signing keys on the first install and keeps them, so leave those settings empty.

  4. Have a cluster administrator create the Spark Operator CRDs and webhook:

    • For the CRDs, follow step 2 of Option 2: Have an Administrator Create Them.

    • For the webhook, run:

      helm template data-plane iomete/iomete-data-plane-enterprise \
      --namespace iomete-system \
      --version "$IOMETE_VERSION" \
      --values example-data-plane-values.yaml \
      --set webhook.create=true \
      --set argocd=false \
      --show-only templates/lakehouse-runtime/spark-operator-webhook.yaml \
      > spark-operator-webhook.yaml

      kubectl apply -f spark-operator-webhook.yaml
  5. Tell Argo CD when IOMETE's Spark applications are healthy. Its built-in check waits for Spark executors, which IOMETE's Spark Connect server doesn't start, so the Application otherwise stays Progressing. Add this to the argocd-cm ConfigMap (under configs.cm if you install Argo CD with its Helm chart):

    argocd-cm
    data:
    resource.customizations.health.sparkoperator.k8s.io_SparkApplication: |
    hs = {}
    local state = ""
    if obj.status ~= nil and obj.status.applicationState ~= nil and obj.status.applicationState.state ~= nil then
    state = obj.status.applicationState.state
    end
    if state == "RUNNING" or state == "COMPLETED" then
    hs.status = "Healthy"
    elseif state == "FAILED" or state == "SUBMISSION_FAILED" then
    hs.status = "Degraded"
    else
    hs.status = "Progressing"
    end
    hs.message = "SparkApplication is " .. (state ~= "" and state or "being submitted")
    return hs
  6. Create the Argo CD Application. Put the contents of your values file under valuesObject:

    iomete-data-plane.yaml
    apiVersion: argoproj.io/v1alpha1
    kind: Application
    metadata:
    name: iomete-data-plane
    namespace: argocd
    spec:
    project: default
    source:
    repoURL: https://chartmuseum.iomete.com
    chart: iomete-data-plane-enterprise
    targetRevision: "<chart-version>"
    helm:
    releaseName: data-plane
    valuesObject:
    argocd: true
    # ...the rest of your values file
    destination:
    server: https://kubernetes.default.svc
    namespace: iomete-system
    syncPolicy:
    automated:
    prune: true
    selfHeal: true
    kubectl apply -f iomete-data-plane.yaml

Upgrading​

  1. Set IOMETE_VERSION to the new chart version.
  2. If the release notes say the CRDs changed, follow Upgrading the CRDs.
  3. If you change namespaces in your values file, re-apply the webhook (step 4).
  4. Change targetRevision to the new chart version.
Moving from a Helm install

Don't run helm uninstall on the old release. It deletes every resource Argo CD now manages, and the data plane is down until Argo CD re-creates them. Delete only Helm's release record instead, which leaves every resource, including the webhook, in place:

kubectl delete secret -n iomete-system -l owner=helm,name=data-plane

Known Limits​

  • After you rotate the CA certificate, restart the gateway and MCP server yourself:

    kubectl rollout restart deployment iom-gateway iom-mcp-server -n iomete-system
  • Install checks that need the cluster are skipped, for example the CA certificate Secret's key. A wrong setting shows up later as a pod that doesn't start.

  • The console's configuration comparison and runtime snapshot are empty.

  • Install the optional Grafana chart with Helm, not Argo CD: Argo CD recreates its storage on every sync.