Added SHA256 digest support to the helm deployment template #1647
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description of the change
Add SHA256 digest support to the deployment template and add the "digest" parameter to values.yaml
Benefits
It is easy to pull images with specific SHA digest values when the need arises.
Possible drawbacks
We used it in our production environment for a while and haven't seen any drawbacks yet.
Additional information
The deployment template update to support the SHA digest helped us explicitly specify the SHA digest for particular architecture-based images when facing issues in the cluster that are irrelevant to sealed secrets and image pull. Having the SHA digest support helped us not have a roadblock to deploying and using sealed secrets smoothly. So, I am sharing the update we did and used with the community.