This guide demonstrates how to update credentials referenced in the Immuta Enterprise Helm chart (IEHC).
Kubernetes namespace
The following section(s) presume the IEHC was deployed into namespace immuta
and that the current namespace is immuta
.
Using an alternative editor
Set environment variable KUBE_EDITOR
to specify an alternative text editor.
Validate that secret immuta-secret
exists in the current namespace.
Edit secret immuta-secret
in place.
Edit secret immuta-legacy-secret
in place. Skip this step if the legacy query engine and fingerprint services are disabled (the default).
Restart pods.
Considerations when using the legacy query engine
The following section is only necessary if the legacy query engine and fingerprint services have been enabled.
Validate that secret immuta-legacy-secret
exists 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.
Update credentials in the immuta-values.yaml
file.
Perform a Helm upgrade to apply the changes made to immuta-values.yaml
. Update the placeholder value with your own release name.