Rotating Credentials
This guide demonstrates how to update credentials referenced in the Immuta Enterprise Helm chart (IEHC).
Kubernetes secrets
Edit secrets
Validate that secret
immuta-secretexists in the current namespace.kubectl get secret/immuta-secretEdit secret
immuta-secretin place.kubectl edit secret/immuta-secretEdit secret
immuta-legacy-secretin place. Skip this step if the legacy query engine and fingerprint services are disabled (the default).kubectl edit secret/immuta-legacy-secretRestart pods.
kubectl rollout restart deployment --all --selector "app.kubernetes.io/component=audit,app.kubernetes.io/component=secure"
Legacy query engine
Validate that secret
immuta-legacy-secretexists in the current namespace.Get the query engine replica count, this value will be referenced in subsequent step(s).
Scale the replica count down to
1.Get the query engine pod name, this value will be referenced in subsequent step(s).
Update the placeholder value with a query engine superuser password.
Update the placeholder value with a query engine replication password.
Update the placeholder value with a query engine feature password.
Scale the replica count back up to the previous value by updating the placeholder value.
Apply Helm values
Update credentials in the
immuta-values.yamlfile.Perform a Helm upgrade to apply the changes made to
immuta-values.yaml. Update the placeholder value with your own release name.
Last updated
Was this helpful?

