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.

Sign up for GitHub

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

Jump to bottom

Kubectl run should produce deployment and job #14954

Closed
bgrant0607 opened this issue Oct 1, 2015 · 5 comments
Closed

Kubectl run should produce deployment and job #14954

bgrant0607 opened this issue Oct 1, 2015 · 5 comments
Assignees
@janetkuo
Labels
area/app-lifecycle area/usability priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release.
Milestone
v1.2

Comments

@bgrant0607
Copy link
Member

Forked from #1743.

Kubectl run should produce deployment and job rather than replication controller and raw pods.

Initially using an experimental generator version, which we can make the default once these APIs reach beta+ maturity.
@bgrant0607 bgrant0607 added kind/enhancement priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. area/app-lifecycle area/usability labels Oct 1, 2015
@bgrant0607 bgrant0607 mentioned this issue Oct 2, 2015
Closed
@aronchick
Copy link
Contributor

+1!

@derekwaynecarr
Copy link
Member

The OpenShift run command does this today.

@smarterclayton @ironcladlou @deads2k

On Thursday, October 1, 2015, David Aronchick notifications@github.com
wrote:

+1!

—
Reply to this email directly or view it on GitHub
#14954 (comment)
.

@smarterclayton
Copy link
Contributor

Yeah, I overrode the generator for default always to create the deployment
equivalent. I did not rev our generator identifier version

On Oct 2, 2015, at 3:07 AM, Derek Carr notifications@github.com wrote:

The OpenShift run command does this today.

@smarterclayton @ironcladlou @deads2k

On Thursday, October 1, 2015, David Aronchick notifications@github.com
wrote:

+1!

—
Reply to this email directly or view it on GitHub
<
#14954 (comment)

.

—
Reply to this email directly or view it on GitHub
#14954 (comment)
.

@bgrant0607
Copy link
Member Author

While these are still experimental we can't make it the default.

@bgrant0607 bgrant0607 added this to the v1.2-candidate milestone Nov 5, 2015
@bgrant0607
Copy link
Member Author

Both of these should be at least beta in 1.2.

@janetkuo janetkuo self-assigned this Nov 11, 2015
@janetkuo janetkuo mentioned this issue Nov 13, 2015
Merged
3 tasks
@bgrant0607 bgrant0607 modified the milestones: v1.2-candidate, v1.2 Nov 19, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@janetkuo janetkuo

Labels
area/app-lifecycle area/usability priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release.
Projects
None yet
Milestone
v1.2
Development

No branches or pull requests
5 participants
@aronchick @smarterclayton @janetkuo @derekwaynecarr @bgrant0607