Enhancements: Deployments to GA

Created on 3 Mar 2017 · 22Comments · Source: kubernetes/enhancements

Feature Description

One-line feature description (can be used as a release note): Deployments to GA
Primary contact (assignee): @janetkuo
Responsible SIGs: @kubernetes/sig-apps-proposals
Design proposal link (community repo): https://github.com/kubernetes/community/blob/master/contributors/design-proposals/deployment.md
Reviewer(s) - (for LGTM) recommend having 2+ reviewers (at least one from code-area OWNERS file) agreed to review. Reviewers from multiple companies preferred: @kargakis @tnozicka
Approver (likely from SIG/area to which feature belongs): @smarterclayton @erictune
Feature target (which target equals to which milestone):
- Alpha release target (x.y)
- Beta release target (x.y)
- Stable release target (x.y)

siapps stagstable

Source

soltysh

❤1

Most helpful comment

Yup! So are DaemonSet and ReplicaSet.

enisoc on 13 Dec 2017

👍2

All 22 comments

@kubernetes/sig-apps-misc

kargakis on 3 Mar 2017

@soltysh can you update the feature naming? As we have "Deployments" since 1.1 release, we need more clarification what this feature is about.

idvoretskyi on 3 Mar 2017

@idvoretskyi this is not a specific feature but a progress tracker for moving Deployments to GA.

kargakis on 3 Mar 2017

Maybe we need to have this in a different place?

kargakis on 3 Mar 2017

This is the right place, since everyone expects major feature to be tracked here.

soltysh on 3 Mar 2017

@kargakis no, we have to leave it here as @soltysh mentioned.

idvoretskyi on 3 Mar 2017

Deployments is already beta, right, so those boxes need to be checked too?

On Fri, Mar 3, 2017 at 5:04 AM, Ihor Dvoretskyi notifications@github.com
wrote:

@kargakis https://github.com/kargakis no, we have to leave it here as
@soltysh https://github.com/soltysh mentioned.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/kubernetes/features/issues/194#issuecomment-283947709,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AHuudukz0_WMy4FW9EFgU_1usegftc9Xks5riA_EgaJpZM4MSGrf
.

erictune on 3 Mar 2017

Done.

soltysh on 3 Mar 2017

Does this also cover moving ReplicaSets to GA?

craigbox on 25 Apr 2017

@craigbox we will need a separate issue I think, although I would expect ReplicaSets to be GA once we move Deployments to GA.

kargakis on 28 Apr 2017

As part of moving Deployments to GA, we are going to fix in 1.7 the biggest issue Deployments have so far which is hash collisions. Got an update to the Deployment proposal merged yesterday that reflects the new API field (https://github.com/kubernetes/community/pull/477). Implementation is in https://github.com/kubernetes/kubernetes/pull/44774

kargakis on 28 Apr 2017

As part of moving Deployments to GA, we are going to fix in 1.7 the biggest issue Deployments have so far which is hash collisions. Got an update to the Deployment proposal merged yesterday that reflects the new API field (kubernetes/community#477). Implementation is in kubernetes/kubernetes#44774

Opened https://github.com/kubernetes/features/issues/287

kargakis on 29 Apr 2017

@soltysh @kargakis @mfojtik I've updated the feature description to fit the new template. Please, fill the empty fields in the new template (their actual state was unclear).

idvoretskyi on 3 May 2017

@idvoretskyi based on the new template, I am wondering if umbrella issues like this one make sense anymore. This issue specifically tracks moving Deployments to GA but I doubt it provides the visibility that separate self-contained issues provide. Thoughts?

kargakis on 7 May 2017

@kargakis sorry about missing this from the horizon.

I would like to keep the Deployments feature issue if the progress is still expected ("deployment" is the feature, while others are enhancements). At the same time, I would propose to close https://github.com/kubernetes/features/issues/287 in favor of the current one. But I'd like to hear the different thoughts if there are any.

cc @soltysh @kubernetes/sig-apps-feature-requests

idvoretskyi on 31 May 2017

I think keeping this umbrella issue is fine; can reference to specific major fixes that are upcoming...

luxas on 31 May 2017

As a matter of process, if the intention is to have a separate issue for moving each feature between states (zero to alpha, alpha to beta, beta to GA, or variations thereof), I would like to request:

the title of issues be in the format of "Deployments to GA" for ease of scanning
a label on each showing the state transition, "stage/ga"
regularly closing the old features for things which have launched (f.ex #60)

I'm happy to help with the triage.

craigbox on 1 Jun 2017

👍1

This is covered by another umbrella issue for workloads APIs: #353