kubectl run from a manifest file #63214

jeremywadsack · 2018-04-26T19:59:17Z

Is this a BUG REPORT or FEATURE REQUEST?:

/kind feature

What happened:

As discussed in #48684 we also have a use case where we would like to spin up a pod, run a command, and throw away the pod. kubectl run seems to support this except that it gets very complicated to bring up a pod matching the environment of an existing deployment. Specifically, attaching secrets.

The commonly cited example is to spin up a pod to run database migrations during a deployment.

That PR has to do with adding an --end-from option to the kubectl run but on further discussion, the use of --override seems to have resolved some of the problems. However, that has it's own issues, as @javanthropus mentioned:

This seems a little backwards logically though because we want the manifest to be the base definition, where the additional command line options provide overrides. It's also a mess to have to pass the entire manifest on the command line.

I would like to be able to specify the image on the command-line and override the spec. Specifically, I'd like to have a static manifest to load from and then add a tag to the image from our script so I can make sure I'm using the right image.

Something like this (which currently ignores the command-line:)

kubectl run -shell --image image:${TAG:-latest} --restart=Never --overrides $overrides -- bin/rails db:migrate

Going further, as with the create and apply commands, it would be great if the manifest could be supplied in either JSON or YAML formats.

Agreed because all our other configuration files are in YAML. I ended up with this so we could store the manifest in YAML like we do everything else:

--overrides $(ruby -r json -r yaml -e 'puts JSON.dump YAML.load_file("shell.yml")')

But I ran into further issues where if --restart=Never is on the run command, it launches a Pod, but ignores the command line and just runs the default command in the Docker image.

What you expected to happen:

It would be great to have a -f option like apply does:

kubectl run -it --rm --restart=Never --filename pod.json

Anything else we need to know?:

Environment:

Kubernetes version (use kubectl version):

$ kubectl version
Client Version: version.Info{Major:"1", Minor:"8", GitVersion:"v1.8.6", GitCommit:"6260bb08c46c31eea6cb538b34a9ceb3e406689c", GitTreeState:"clean", BuildDate:"2017-12-21T06:34:11Z", GoVersion:"go1.8.3", Compiler:"gc", Platform:"darwin/amd64"}
Server Version: version.Info{Major:"1", Minor:"9+", GitVersion:"v1.9.6-gke.1", GitCommit:"cb151369f60073317da686a6ce7de36abe2bda8d", GitTreeState:"clean", BuildDate:"2018-04-07T22:06:59Z", GoVersion:"go1.9.3b4", Compiler:"gc", Platform:"linux/amd64"}

The text was updated successfully, but these errors were encountered:

jeremywadsack · 2018-04-26T20:02:06Z

@kubernetes/sig-cli-feature-requests

k8s-ci-robot · 2018-04-26T20:02:14Z

@jeremywadsack: Reiterating the mentions to trigger a notification:
@kubernetes/sig-cli-feature-requests

In response to this:

@kubernetes/sig-cli-feature-requests

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.

fejta-bot · 2018-07-25T20:59:53Z

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

jeremywadsack · 2018-07-26T03:29:24Z

/remove-lifecycle stale

cody1996 · 2018-10-24T03:17:25Z

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 · 2019-01-18T12:40:23Z

Any news on this?

zeppelinen · 2019-04-01T11:27:09Z

any updates or workarounds?

timjkelly · 2019-06-13T19:43:57Z

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 · 2019-09-11T19:49:00Z

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

jeremywadsack · 2019-09-11T19:55:19Z

/remove-lifecycle stale

ondrejhlavacek · 2019-11-26T12:05:56Z

+1 here!

alex-kovshovik · 2019-12-20T18:32:26Z

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

lkoba · 2019-12-20T19:08:54Z

@alex-kovshovik

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 · 2019-12-20T21:58:17Z

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 · 2020-03-19T22:04:09Z

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

jeremywadsack · 2020-03-23T17:48:30Z

/remove-lifecycle stale

fejta-bot · 2020-06-21T18:42:12Z

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 · 2020-06-22T16:07:28Z

/remove-lifecycle stale

fejta-bot · 2021-05-12T04:24:34Z

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

jeremywadsack · 2021-05-12T05:19:50Z

Just had a convo with someone today about spinning up a container for shell 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 <https://github.com/kubernetes/community>. /lifecycle stale — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#63214 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAB25LH4KJNXCT65KFHX22LTNH7JFANCNFSM4E45K2VQ> .

-- Jeremy Wadsack

k8s-triage-robot · 2021-08-10T05:44:04Z

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/stale is applied
After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
After 30d of inactivity since lifecycle/rotten was 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

dylanPowers · 2021-08-13T17:17:45Z

/remove-lifecycle stale

collimarco · 2021-11-10T22:07:55Z

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.

collimarco · 2021-11-10T23:51:08Z

I also confirm that using --overrides causes the program to completely ignore the command after -- ...

k8s-triage-robot · 2022-02-09T00:40:15Z

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/stale is applied
After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
After 30d of inactivity since lifecycle/rotten was 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

dylanPowers · 2022-02-09T01:56:55Z

/remove-lifecycle stale

k8s-triage-robot · 2022-05-10T02:41:30Z

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/stale is applied
After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
After 30d of inactivity since lifecycle/rotten was 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

k8s-triage-robot · 2022-06-09T03:21:54Z

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/stale is applied
After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
After 30d of inactivity since lifecycle/rotten was 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

dk-github · 2022-06-09T09:57:11Z

/remove-lifecycle rotten

k8s-triage-robot · 2022-09-07T10:04:20Z

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/stale is applied
After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
After 30d of inactivity since lifecycle/rotten was 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

k8s-triage-robot · 2022-10-07T10:22:27Z

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/stale is applied
After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
After 30d of inactivity since lifecycle/rotten was 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

k8s-triage-robot · 2022-11-06T10:57:28Z

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/stale is applied
After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
After 30d of inactivity since lifecycle/rotten was 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

k8s-ci-robot · 2022-11-06T10:57:34Z

@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/stale is applied

After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied

After 30d of inactivity since lifecycle/rotten was 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

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.

k8s-ci-robot added needs-sig Indicates an issue or PR lacks a `sig/foo` label and requires one. kind/feature Categorizes issue or PR as related to a new feature. labels Apr 26, 2018

k8s-ci-robot added sig/cli Categorizes an issue or PR as relevant to SIG CLI. and removed needs-sig Indicates an issue or PR lacks a `sig/foo` label and requires one. labels Apr 26, 2018

k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jul 25, 2018

k8s-ci-robot removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jul 26, 2018

k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Sep 11, 2019

k8s-ci-robot removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Sep 11, 2019

k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Mar 19, 2020

k8s-ci-robot removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Mar 23, 2020

bhack mentioned this issue Apr 14, 2020

Kubernetes container microsoft/vscode-remote-release#12

Open

k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jun 21, 2020

k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label May 12, 2021

k8s-ci-robot removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label May 12, 2021

k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Aug 10, 2021

k8s-ci-robot removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Aug 13, 2021

collimarco mentioned this issue Nov 11, 2021

Multiple ways to run a command cuber-cloud/cuber-gem#1

Closed

k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Feb 9, 2022

k8s-ci-robot removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Feb 9, 2022

k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label May 10, 2022

k8s-ci-robot added lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Jun 9, 2022

k8s-ci-robot removed the lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. label Jun 9, 2022

k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Sep 7, 2022

k8s-ci-robot added lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Oct 7, 2022

k8s-ci-robot closed this as not planned Won't fix, can't repro, duplicate, stale Nov 6, 2022

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

kubectl run from a manifest file #63214

kubectl run from a manifest file #63214

jeremywadsack commented Apr 26, 2018 •

edited

Loading

jeremywadsack commented Apr 26, 2018

k8s-ci-robot commented Apr 26, 2018

fejta-bot commented Jul 25, 2018

jeremywadsack commented Jul 26, 2018

cody1996 commented Oct 24, 2018

bhack commented Jan 18, 2019

zeppelinen commented Apr 1, 2019

timjkelly commented Jun 13, 2019

fejta-bot commented Sep 11, 2019

jeremywadsack commented Sep 11, 2019

ondrejhlavacek commented Nov 26, 2019

alex-kovshovik commented Dec 20, 2019

lkoba commented Dec 20, 2019

alex-kovshovik commented Dec 20, 2019

fejta-bot commented Mar 19, 2020

jeremywadsack commented Mar 23, 2020

fejta-bot commented Jun 21, 2020

mike-stewart commented Jun 22, 2020

fejta-bot commented May 12, 2021

jeremywadsack commented May 12, 2021 via email

k8s-triage-robot commented Aug 10, 2021

dylanPowers commented Aug 13, 2021

collimarco commented Nov 10, 2021

collimarco commented Nov 10, 2021

k8s-triage-robot commented Feb 9, 2022

dylanPowers commented Feb 9, 2022

k8s-triage-robot commented May 10, 2022

k8s-triage-robot commented Jun 9, 2022

dk-github commented Jun 9, 2022

k8s-triage-robot commented Sep 7, 2022

k8s-triage-robot commented Oct 7, 2022

k8s-triage-robot commented Nov 6, 2022

k8s-ci-robot commented Nov 6, 2022

kubectl run from a manifest file #63214

kubectl run from a manifest file #63214

Comments

jeremywadsack commented Apr 26, 2018 • edited Loading

jeremywadsack commented Apr 26, 2018

k8s-ci-robot commented Apr 26, 2018

fejta-bot commented Jul 25, 2018

jeremywadsack commented Jul 26, 2018

cody1996 commented Oct 24, 2018

bhack commented Jan 18, 2019

zeppelinen commented Apr 1, 2019

timjkelly commented Jun 13, 2019

fejta-bot commented Sep 11, 2019

jeremywadsack commented Sep 11, 2019

ondrejhlavacek commented Nov 26, 2019

alex-kovshovik commented Dec 20, 2019

lkoba commented Dec 20, 2019

alex-kovshovik commented Dec 20, 2019

fejta-bot commented Mar 19, 2020

jeremywadsack commented Mar 23, 2020

fejta-bot commented Jun 21, 2020

mike-stewart commented Jun 22, 2020

fejta-bot commented May 12, 2021

jeremywadsack commented May 12, 2021 via email

k8s-triage-robot commented Aug 10, 2021

dylanPowers commented Aug 13, 2021

collimarco commented Nov 10, 2021

collimarco commented Nov 10, 2021

k8s-triage-robot commented Feb 9, 2022

dylanPowers commented Feb 9, 2022

k8s-triage-robot commented May 10, 2022

k8s-triage-robot commented Jun 9, 2022

dk-github commented Jun 9, 2022

k8s-triage-robot commented Sep 7, 2022

k8s-triage-robot commented Oct 7, 2022

k8s-triage-robot commented Nov 6, 2022

k8s-ci-robot commented Nov 6, 2022

jeremywadsack commented Apr 26, 2018 •

edited

Loading