Open obs-gh-danielmartin opened 5 months ago
This issue is currently awaiting triage.
SIG CLI takes a lead on issue triage for this repo, but any Kubernetes member can accept issues by applying the triage/accepted
label.
The triage/accepted
label can be added by org members by writing /triage accepted
in a comment.
The Kubernetes project currently lacks enough contributors to adequately respond to all issues.
This bot triages un-triaged issues according to the following rules:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the issue is closedYou can:
/remove-lifecycle stale
/close
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues.
This bot triages un-triaged issues according to the following rules:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the issue is closedYou can:
/remove-lifecycle rotten
/close
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle rotten
/lifecycle frozen
https://github.com/kubernetes-sigs/kustomize/blob/ed09399cd1fa66b9290058ea909025385400f434/api/types/image.go#L23
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.