Using digest and newTag outputs both when docs indicate newTag is ignored #5664
Labels
lifecycle/frozen
Indicates that an issue or PR should not be auto-closed due to staleness.
needs-kind
Indicates a PR lacks a `kind/foo` label and requires one.
needs-triage
Indicates an issue or PR lacks a `triage/foo` label and requires one.
kustomize/api/types/image.go
Line 23 in ed09399
Since #4406 this is no longer true. If tag and digest are both specified, both tag and digest will be included in the new image string. This is probably fine for the majority of use cases, but if previously relying on the digest for immutability and tag for human readability, this unexpectedly results in resource updates/restarts when the tag is changed (which previously wasn't included in the resulting output) but the digest is unchanged.
The text was updated successfully, but these errors were encountered: