-
Notifications
You must be signed in to change notification settings - Fork 2.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
use container restart policy if user specifies one #19676
Conversation
Fixes: containers#19671 Signed-off-by: Daniel J Walsh <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think this should be other way around, all containers must inherit pod policy only and default pod-policy
should be Always
. See:https://kubernetes.io/docs/concepts/workloads/pods/pod-lifecycle/#restart-policy
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Changes LGTM
Another reminder to write commit messages.
That's not how it was designed. We wanted a container to always by able to override the restart policy if explicitly set by the user and otherwise inherit the pod's default. Note that this is |
Yes in Kubernetes world, I don't think a container can specify a restart policy in the kube.yaml. In Pod's though they can so we should honor the more specific setting. @flouthoc ^^ @containers/podman-maintainers PTAL |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM , I confused between podman kube
and podman pod
/lgtm
/approve
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: flouthoc, rhatdan The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
/cherry-pick v4.6 |
@vrothberg: new pull request created: #19682 In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
@vrothberg Please cherry-pick to Podman v4.6.1-rhel ASAP. Two BZ's spun your way to allow for that. https://bugzilla.redhat.com/show_bug.cgi?id=2233222 and https://bugzilla.redhat.com/show_bug.cgi?id=2233218 |
/cherry-pick v4.6.1-rhel |
@mheon: new pull request created: #19692 In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
Fixes: #19671
Does this PR introduce a user-facing change?