Installing Kubernetes via `helm install` using a SHA instead of image tag
PreviousMigration/ Install to External Database fails with: "migrations found.."NextRelation "Token" does not exist
Last updated
Last updated
Issue:
When installing Immuta on Kubernetes using helm, customer is trying to use tags encrypted in SHA instead of image:
Often the above will be met with a "...denied the request..." related error
Cause:
1) The SHA256 hashed tag is misplaced in the values file. It should be under the `digest` field in the values file. Putting it in the `repository` field, the existing tag will still be applied and used.
2) IHC v4.13.3+/ IEHC Charts
Resolution:
The helm values file should look something like this: