After stackabletech/commons-operator#111 is now finally fixed, we can enable restart-controller everywhere. IIRC superset-op and airflow-op already did this.
restart-controller enabled
No unneeded restart (for this the StatefulSet needs to be created last!)
TIPP: Use this command to check the StatefulSet generations:
kubectl get sts -A -l restarter.stackable.tech/enabled=true -o jsonpath='{range .items[*]}{.metadata.namespace}/{.metadata.name}{"\t\t"}{.metadata.generation}{"\n"}{end}'
Release notes
All products now have the restart-controller enabled, so that the Pods are automatically restarted on config changes (either ConfigMaps or Secrets)
After stackabletech/commons-operator#111 is now finally fixed, we can enable restart-controller everywhere. IIRC superset-op and airflow-op already did this.
restart-controller enabled
No unneeded restart (for this the StatefulSet needs to be created last!)
TIPP: Use this command to check the StatefulSet generations:
kubectl get sts -A -l restarter.stackable.tech/enabled=true -o jsonpath='{range .items[*]}{.metadata.namespace}/{.metadata.name}{"\t\t"}{.metadata.generation}{"\n"}{end}'Release notes
All products now have the restart-controller enabled, so that the Pods are automatically restarted on config changes (either ConfigMaps or Secrets)