-
Notifications
You must be signed in to change notification settings - Fork 2.5k
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
pod create --share none should not create infra #15059
Conversation
Also your release note does not make sense if you read it without the context of this PR. Please mention the command |
for podman pod create, when we are not sharing any namespaces there is no point for the infra container. This is especially true since resources have also been decoupled from the container recently. handle this on the cmd level so that we can still create infra if set explicitly resolves containers#15048 Signed-off-by: Charlie Doern <cdoern@redhat.com>
LGTM |
@Luap99 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.
code LGTM but the release note line should be changed. It does not make much sense when you read it as one line without additional context.
@Luap99 is that note better? |
SGTM but do we need correct capitalization and punctuation, @mheon @edsantiago? |
/approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: cdoern, Luap99 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 |
@Luap99 this merged before I got a chance to look at it; and now that I'm looking, I don't know what capitalization you refer to. If this needs (or might need) a followup PR, could you please elaborate? If not, no problem. |
I am talking about the release notes block, we can change it after it merges AFAIK. |
Yes, perfectly fine to do that. |
for podman pod create, when we are not sharing any namespaces there is no point for the infra container.
This is especially true since resources have also been decoupled from the container recently.
handle this on the cmd level so that we can still create infra if set explicitly
resolves #15048
Signed-off-by: Charlie Doern cdoern@redhat.com
Does this PR introduce a user-facing change?