Re: [kubernetes/kubernetes] kubectl run from a manifest file (#63214)
k8s-ci-robot
@jeremywadsack: Reiterating the mentions to trigger a notification:
@kubernetes/sig-cli-feature-requests
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.
—
You are receiving this because you are on a team that was mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.
fejta-bot
Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close.
Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale
Jeremy Wadsack
/remove-lifecycle stale
cody1996
Is this feature not available now? I saw a flag named "filename" in the Reference, but it doesn't seem to work. The version I am using is 1.12.1.
bhack
Any news on this?
Alexander Naydenko
any updates or workarounds?
TJ Kelly
Any update on this? I'd love to be able to define everything in a manifest file instead of having a mile-long command using overrides.
fejta-bot
Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close.
Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale
—
Jeremy Wadsack
/remove-lifecycle stale
Ondřej Hlaváček
+1 here!
—
You are receiving this because you are on a team that was mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.
Alex Kovshovik
Passing --overrides works, but the JSON has to be 1 line with no spaces or should be put into single quotes - 'overrides here'.
This breaks down when I'm trying to make it part of CI YAML config file.
It would be very nice if I could indeed specify the Pod manifest in a file.
The following works however:
kubectl run migrator --image registry.gitlab.com/shovik-group/shovik-com --overrides='{"spec":{"containers":[{"name":"migrator","image":"registry.gitlab.com/shovik-group/shovik-com","envFrom":[{"secretRef":{"name":"shovik-com"}}],"args":["bin/shovik_com","eval","ShovikCom.Release.migrate()"]}]}}' --restart=Never --image-pull-policy=Always --attach --rm
Koba
https://gist.github.com/lkoba/e73dcc13bd8d81907b1f4069a19979ec
I use this to run pod manifests, it works with multiline commands, volumes, secrets, labels, etc.
You may need to adapt it to your needs. At the moment it only works with Pod manifest files.
It depends on jq and y2j to parse json and convert yaml files to json.
Alex Kovshovik
This is great, thanks for sharing! To reduce the number of dependencies, I saved my manifest file as JSON - no need for y2j. jq was already installed on that system (container).
Thank you @lkoba
fejta-bot
Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close.
Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale
—
Jeremy Wadsack
/remove-lifecycle stale
fejta-bot
Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close.
Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale
Mike Stewart
/remove-lifecycle stale
fejta-bot
Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close.
Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale
klimov-gett
I think this may also be a worthy alternative to k8s jobs
(which also don't have any supplement for the --rm option apart from feature-gate TTLAfterFinished )
In cases where parallelism and concurrency are not needed, i.e.: you only need to run one pod (but with multiple containers) to completion and delete it immediately after, using something like run --rm -f [filename] makes a lot of sense.
fejta-bot
Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
If this issue is safe to close now please do so with /close.
Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten
Mike Stewart
/remove-lifecycle rotten
fejta-bot
Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close.
Send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale
Jeremy Wadsack
/remove-lifecycle stale
On Wed, Feb 10, 2021 at 7:10 PM fejta-bot <notifi...@github.com> wrote:
> Issues go stale after 90d of inactivity.
> Mark the issue as fresh with /remove-lifecycle stale.
> Stale issues rot after an additional 30d of inactivity and eventually
> close.
>
> If this issue is safe to close now please do so with /close.
>
> Send feedback to sig-contributor-experience at kubernetes/community
> /lifecycle stale
>
> —
> You are receiving this because you were mentioned.
> Reply to this email directly, view it on GitHub
> or unsubscribe
> <https://github.com/notifications/unsubscribe-auth/AAB25LEC5Q7LTSRBAYGWXMLS6NDA3ANCNFSM4E45K2VQ>
> .
>
--
Jeremy Wadsack
fejta-bot
Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close.
Send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale
—
Jeremy Wadsack
access is a common pattern.
/remove-lifecycle stale
On Tue, May 11, 2021 at 9:24 PM fejta-bot ***@***.***> wrote:
> Issues go stale after 90d of inactivity.
> Mark the issue as fresh with /remove-lifecycle stale.
> Stale issues rot after an additional 30d of inactivity and eventually
> close.
>
> If this issue is safe to close now please do so with /close.
>
> Send feedback to sig-contributor-experience at kubernetes/community
> /lifecycle stale
>
> —
> You are receiving this because you were mentioned.
> Reply to this email directly, view it on GitHub
> or unsubscribe
> <https://github.com/notifications/unsubscribe-auth/AAB25LH4KJNXCT65KFHX22LTNH7JFANCNFSM4E45K2VQ>
> .
>
--
Jeremy Wadsack
Kubernetes Triage Robot
The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.
This bot triages issues and PRs according to the following rules:
- After 90d of inactivity,
lifecycle/staleis applied - After 30d of inactivity since
lifecycle/stalewas applied,lifecycle/rottenis applied - After 30d of inactivity since
lifecycle/rottenwas applied, the issue is closed
You can:
- Mark this issue or PR as fresh with
/remove-lifecycle stale - Mark this issue or PR as rotten with
/lifecycle rotten - Close this issue or PR with
/close - Offer to help out with Issue Triage
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale
—
You are receiving this because you are on a team that was mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.
Triage notifications on the go with GitHub Mobile for iOS or Android.
Dylan Powers
/remove-lifecycle stale
Marco Colli
We need to run a complex pod definition (with configmaps, secrets, regcred, labels, etc.) and overrides seems really strange and error-prone (e.g. different base templates produced by different kubectl versions may produce errors and unexpected behaviors with the override).
Please add an -f option to pass the full pod spec (YAML) like apply -f... It would be much cleaner.
Basically run should be like apply + attach (at the same time).
Workaround: Currently we use apply + exec to use our custom pod spec... However we need to use a sleep command in order to keep the empty pod alive (before the exec). The other solution would be better.
Marco Colli
I also confirm that using --overrides causes the program to completely ignore the command after -- ...
Kubernetes Triage Robot
The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.
This bot triages issues and PRs according to the following rules:
- After 90d of inactivity,
lifecycle/staleis applied - After 30d of inactivity since
lifecycle/stalewas applied,lifecycle/rottenis applied - After 30d of inactivity since
lifecycle/rottenwas applied, the issue is closed
You can:
- Mark this issue or PR as fresh with
/remove-lifecycle stale - Mark this issue or PR as rotten with
/lifecycle rotten - Close this issue or PR with
/close - Offer to help out with Issue Triage
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale
—
Reply to this email directly, view it on GitHub, or unsubscribe.
Triage notifications on the go with GitHub Mobile for iOS or Android.
You are receiving this because you are on a team that was mentioned.
Dylan Powers
/remove-lifecycle stale
—
Reply to this email directly, view it on GitHub, or unsubscribe.
Triage notifications on the go with GitHub Mobile for iOS or Android.
You are receiving this because you are on a team that was mentioned.
Kubernetes Triage Robot
The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.
This bot triages issues and PRs according to the following rules:
- After 90d of inactivity,
lifecycle/staleis applied - After 30d of inactivity since
lifecycle/stalewas applied,lifecycle/rottenis applied - After 30d of inactivity since
lifecycle/rottenwas applied, the issue is closed
You can:
- Mark this issue or PR as fresh with
/remove-lifecycle stale - Mark this issue or PR as rotten with
/lifecycle rotten - Close this issue or PR with
/close - Offer to help out with Issue Triage
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are on a team that was mentioned.
Kubernetes Triage Robot
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.
This bot triages issues and PRs according to the following rules:
- After 90d of inactivity,
lifecycle/staleis applied - After 30d of inactivity since
lifecycle/stalewas applied,lifecycle/rottenis applied - After 30d of inactivity since
lifecycle/rottenwas applied, the issue is closed
You can:
- Mark this issue or PR as fresh with
/remove-lifecycle rotten
- Close this issue or PR with
/close - Offer to help out with Issue Triage
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle rotten
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are on a team that was mentioned.
Dmitry Kovalev
/remove-lifecycle rotten
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are on a team that was mentioned.
Kubernetes Triage Robot
The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.
This bot triages issues and PRs according to the following rules:
- After 90d of inactivity,
lifecycle/staleis applied - After 30d of inactivity since
lifecycle/stalewas applied,lifecycle/rottenis applied - After 30d of inactivity since
lifecycle/rottenwas applied, the issue is closed
You can:
- Mark this issue or PR as fresh with
/remove-lifecycle stale - Mark this issue or PR as rotten with
/lifecycle rotten
- Close this issue or PR with
/close - Offer to help out with Issue Triage
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are on a team that was mentioned.
Kubernetes Triage Robot
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.
This bot triages issues and PRs according to the following rules:
- After 90d of inactivity,
lifecycle/staleis applied - After 30d of inactivity since
lifecycle/stalewas applied,lifecycle/rottenis applied - After 30d of inactivity since
lifecycle/rottenwas applied, the issue is closed
You can:
- Mark this issue or PR as fresh with
/remove-lifecycle rotten
- Close this issue or PR with
/close - Offer to help out with Issue Triage
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle rotten
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are on a team that was mentioned.
Kubernetes Triage Robot
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.
This bot triages issues according to the following rules:
- After 90d of inactivity,
lifecycle/staleis applied - After 30d of inactivity since
lifecycle/stalewas applied,lifecycle/rottenis applied - After 30d of inactivity since
lifecycle/rottenwas applied, the issue is closed
You can:
- Reopen this issue with
/reopen - Mark this issue as fresh with
/remove-lifecycle rotten
- Offer to help out with Issue Triage
Please send feedback to sig-contributor-experience at kubernetes/community.
/close not-planned
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are on a team that was mentioned.
Kubernetes Prow Robot
Closed #63214 as not planned.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are on a team that was mentioned.
Kubernetes Prow Robot
@k8s-triage-robot: Closing this issue, marking it as "Not Planned".
In response to this:
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.
This bot triages issues according to the following rules:
- After 90d of inactivity,
lifecycle/staleis applied- After 30d of inactivity since
lifecycle/stalewas applied,lifecycle/rottenis applied- After 30d of inactivity since
lifecycle/rottenwas applied, the issue is closedYou can:
- Reopen this issue with
/reopen- Mark this issue as fresh with
/remove-lifecycle rotten- Offer to help out with Issue Triage
Please send feedback to sig-contributor-experience at kubernetes/community.
/close not-planned
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.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are on a team that was mentioned.