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.9.5-rc.1.

Download configuration

# Or via Helm CLI (after helm repo add)
helm show values iofog-operator/iofog-operator --version 3.9.5-rc.1 > my-values.yaml
helm pull iofog-operator/iofog-operator --version 3.9.5-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.9.5-rc.1 \
  --set auth.bootstrap.password='ReplaceMe1!x'

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

The ControlPlane resource is named pot unless name is set. The Helm release name does not change that name.

Install from a values file

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

LoadBalancer and externalTrafficPolicy

Defaults use LoadBalancer for controller, router, and NATS. The NATS internal Service (nats-server) is ClusterIP. When externalTrafficPolicy is auto, 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:

services:
  controller:
    type: LoadBalancer
    externalTrafficPolicy: Cluster
  router:
    type: LoadBalancer
    externalTrafficPolicy: Cluster
  nats:
    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.9.5-rc.1 \
  --set auth.mode=external \
  --set auth.issuerUrl=https://auth.example.com/realms/myrealm \
  --set auth.client.id=controller \
  --set auth.client.secret='...'

Container images (this release)

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

Other mirror

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