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.
Argo CD is supported on chart versions after 4.0.2. Earlier versions aren't supported.
Installing
-
Follow the On-Premises Deployment Guide up to and including Prepare Your Values File.
-
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-keyunless you use S3-compatible storage. -
Add these lines to your values file, and remove any passwords or keys from it:
example-data-plane-values.yamlargocd: trueserviceAccount:create: truecrds:create: falsewebhook:create: falsedatabase:passwordSecret:name: iomete-credentialskey: db-passwordadminCredentials:user: postgrespasswordSecret:name: iomete-credentialskey: db-admin-password# S3-compatible storage onlystorage:type: s3_compatibles3CompatibleSettings:endpoint: "<object storage endpoint>"accessKey: "<object storage access key>"secretKeySecret:name: iomete-credentialskey: storage-secret-keyOn AWS S3, Google Cloud Storage or Azure, keep your existing
storageblock 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 intos3CompatibleSettingsand deleteminioSettings. The chart ignores it onces3CompatibleSettingsis set.With workload identity (EKS, GKE or Azure), the init job runs as
iomete-data-plane-initunder Argo CD. Have the cloud side trustsystem:serviceaccount:iomete-system:iomete-data-plane-initas well aslakehouse-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.
-
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.yamlkubectl apply -f spark-operator-webhook.yaml
-
-
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-cmConfigMap (underconfigs.cmif you install Argo CD with its Helm chart):argocd-cmdata: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 thenstate = obj.status.applicationState.stateendif state == "RUNNING" or state == "COMPLETED" thenhs.status = "Healthy"elseif state == "FAILED" or state == "SUBMISSION_FAILED" thenhs.status = "Degraded"elsehs.status = "Progressing"endhs.message = "SparkApplication is " .. (state ~= "" and state or "being submitted")return hs -
Create the Argo CD Application. Put the contents of your values file under
valuesObject:iomete-data-plane.yamlapiVersion: argoproj.io/v1alpha1kind: Applicationmetadata:name: iomete-data-planenamespace: argocdspec:project: defaultsource:repoURL: https://chartmuseum.iomete.comchart: iomete-data-plane-enterprisetargetRevision: "<chart-version>"helm:releaseName: data-planevaluesObject:argocd: true# ...the rest of your values filedestination:server: https://kubernetes.default.svcnamespace: iomete-systemsyncPolicy:automated:prune: trueselfHeal: truekubectl apply -f iomete-data-plane.yaml
Upgrading
- Set
IOMETE_VERSIONto the new chart version. - If the release notes say the CRDs changed, follow Upgrading the CRDs.
- If you change
namespacesin your values file, re-apply the webhook (step 4). - Change
targetRevisionto the new chart version.
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.