Datasance PoT Operator — Helm repository

Human-friendly index for the Datasance PoT Helm chart. Charts are pre-configured for datasance.com/v3 and images from ghcr.io/datasance. Release v3.8.0-rc.1.

Download configuration

values.yaml — default values for the latest publish on this site (stamped for this mirror)
values-3.8.0-rc.1.yaml — defaults for chart version 3.8.0-rc.1
iofog-operator-3.8.0-rc.1.tgz — chart tarball
index.yaml — Helm repository index

# Or via Helm CLI (after helm repo add)
helm show values iofog-operator/iofog-operator --version 3.8.0-rc.1 > my-values.yaml
helm pull iofog-operator/iofog-operator --version 3.8.0-rc.1 --untar

Quick install

helm repo add iofog-operator https://datasance.github.io/iofog-operator
helm repo update
helm install pot iofog-operator/iofog-operator \
  --namespace iofog-system --create-namespace \
  --version 3.8.0-rc.1 \
  --set controlplane.spec.auth.bootstrap.password='ReplaceMe1!'

Embedded bootstrap password: at least 12 characters, one uppercase letter, and one special character. Use passwordSecretRef or a values file instead of --set in production.

Install from a values file

helm show values iofog-operator/iofog-operator --version 3.8.0-rc.1 > my-values.yaml
# edit my-values.yaml
helm install pot iofog-operator/iofog-operator \
  --namespace iofog-system --create-namespace \
  --version 3.8.0-rc.1 \
  -f my-values.yaml

LoadBalancer and externalTrafficPolicy

Defaults use LoadBalancer for controller and router Services. When externalTrafficPolicy is omitted, the operator sets Local on LoadBalancer Services (and Cluster on NodePort).

Local preserves client source IP and suits many cloud load balancers.

Cluster may be required when your cluster networking or LoadBalancer controller does not support Local well — for example Services that stay <pending> or never receive an external address. Set per service in values:

controlplane:
  spec:
    services:
      controller:
        type: LoadBalancer
        externalTrafficPolicy: Cluster
      router:
        type: LoadBalancer
        externalTrafficPolicy: Cluster

Verify

kubectl get pods -n iofog-system
kubectl get svc -n iofog-system
kubectl get controlplanes.datasance.com -n iofog-system

External auth

helm upgrade pot iofog-operator/iofog-operator \
  --namespace iofog-system \
  --version 3.8.0-rc.1 \
  --set controlplane.spec.auth.mode=external \
  --set controlplane.spec.auth.issuerUrl=https://auth.example.com/realms/myrealm \
  --set controlplane.spec.auth.client.id=controller \
  --set controlplane.spec.auth.client.secret='...'

Container images (this release)

ghcr.io/datasance/operator:3.8.0-rc.1
ghcr.io/datasance/controller:3.8.0-rc.1
ghcr.io/datasance/router:3.8.0-rc.1
ghcr.io/datasance/operator-bundle:3.8.0-rc.1 (OLM)

Greenfield v3.8. No in-place upgrade from v3.7 or legacy Datasance/helm. Uninstall the old operator and CRDs before installing v3.8.

Documentation

Chart README — full values reference and examples
values.schema.json — JSON Schema for values
Operator repository — source, manifests, OLM
Release v3.8.0-rc.1 — release notes and artifacts

Other mirror

Using Eclipse ioFog? Add repo https://eclipse-iofog.github.io/iofog-operator — same chart name, different CRD group and registry.