Skip to content
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

Merged
merged 1 commit into from
Jul 26, 2022

Conversation

cdoern
Copy link
Contributor

@cdoern cdoern commented Jul 25, 2022

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?

when using podman pod create --share, if --share=none or --share="" is specified, the pod's infra container is not created

@openshift-ci openshift-ci bot added the do-not-merge/release-note-label-needed Enforce release-note requirement, even if just None label Jul 25, 2022
@openshift-ci openshift-ci bot added release-note and removed do-not-merge/release-note-label-needed Enforce release-note requirement, even if just None labels Jul 25, 2022
cmd/podman/pods/create.go Outdated Show resolved Hide resolved
test/e2e/pod_infra_container_test.go Outdated Show resolved Hide resolved
test/e2e/pod_infra_container_test.go Outdated Show resolved Hide resolved
test/e2e/pod_infra_container_test.go Outdated Show resolved Hide resolved
@Luap99
Copy link
Member

Luap99 commented Jul 25, 2022

Also your release note does not make sense if you read it without the context of this PR. Please mention the command podman pod create

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>
@TomSweeneyRedHat
Copy link
Member

LGTM
and happy green test buttons

@rhatdan
Copy link
Member

rhatdan commented Jul 26, 2022

@Luap99 PTAL

Copy link
Member

@Luap99 Luap99 left a 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.

@cdoern
Copy link
Contributor Author

cdoern commented Jul 26, 2022

@Luap99 is that note better?

@Luap99
Copy link
Member

Luap99 commented Jul 26, 2022

SGTM but do we need correct capitalization and punctuation, @mheon @edsantiago?

@Luap99
Copy link
Member

Luap99 commented Jul 26, 2022

/approve
/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Jul 26, 2022
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jul 26, 2022

[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 /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Jul 26, 2022
@openshift-merge-robot openshift-merge-robot merged commit 7f0fab1 into containers:main Jul 26, 2022
@edsantiago
Copy link
Member

@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.

@Luap99
Copy link
Member

Luap99 commented Jul 26, 2022

I am talking about the release notes block, we can change it after it merges AFAIK.

@mheon
Copy link
Member

mheon commented Jul 26, 2022

Yes, perfectly fine to do that.

@github-actions github-actions bot added the locked - please file new issue/PR Assist humans wanting to comment on an old issue or PR with locked comments. label Sep 21, 2023
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Sep 21, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. lgtm Indicates that a PR is ready to be merged. locked - please file new issue/PR Assist humans wanting to comment on an old issue or PR with locked comments. release-note
Projects
None yet
Development

Successfully merging this pull request may close these issues.

share-nothing pod does not start the infra container
7 participants