-
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
Add --podman-only
flag to podman generate kube
#19211
Add --podman-only
flag to podman generate kube
#19211
Conversation
I hate the --add-reserved option name, No idea what it means from looking at the option. From my quick read this adds options to the kube.yaml, that would not be allowed in kubernetes, but Podman will use, correct? |
Correct |
How about |
That works for me. I'll also make the docs more descriptive |
3c3675b
to
d26a6c5
Compare
--add-reserved
flag to podman generate kube
--podmanonly
flag to podman generate kube
d26a6c5
to
6ee4a7c
Compare
Would |
Otherwise code LGTM. Swagger is angry though. |
I am not crazy with options with "-" in them. But we already have --read-only, I guess there is precedent. |
Adds an `--podman-only` flag to `podman generate kube` to allow for reserved annotations to be included in the generated YAML file. Associated with: containers#19102 Signed-off-by: Jake Correnti <jakecorrenti+github@proton.me>
6ee4a7c
to
d0602e8
Compare
--podmanonly
flag to podman generate kube
--podman-only
flag to podman generate kube
Looks like a flake |
/approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: jakecorrenti, 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 |
/hold cancel |
Adds a
--podman-only
flag topodman generate kube
to allow for podman-only reserved annotations to be included in the generated YAML file. These annotations cannot be used by Kubernetes.Associated with: #19102
Does this PR introduce a user-facing change?