Deployments to GA

[soltysh]

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)

[0xmichalis]

@kubernetes/sig-apps-misc

[idvoretskyi]

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

[0xmichalis]

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

[0xmichalis]

Maybe we need to have this in a different place?

[soltysh]

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

[idvoretskyi]

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

[erictune]

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

…

On Fri, Mar 3, 2017 at 5:04 AM, Ihor Dvoretskyi ***@***.***> 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 <#194 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AHuudukz0_WMy4FW9EFgU_1usegftc9Xks5riA_EgaJpZM4MSGrf> .

[soltysh]

Done.

[craigbox]

Does this also cover moving ReplicaSets to GA?

[0xmichalis]

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

[0xmichalis]

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

[0xmichalis]

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 #287

[idvoretskyi]

@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).

[0xmichalis]

@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?

[idvoretskyi]

@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 #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

[luxas]

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

[craigbox]

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 Inter-pod affinity/anti-affinity #60)

I'm happy to help with the triage.

[janetkuo]

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

[krmayankk]

@janetkuo does this mean Deployments and StatefulSets are GA in 1.9 ?

[enisoc]

Yup! So are DaemonSet and ReplicaSet.

[janetkuo]

@krmayankk re GA in 1.9: Check out this blogpost for 1.9 release http://blog.kubernetes.io/2017/12/kubernetes-19-workloads-expanded-ecosystem.html

[luxas]

This is now shipped! Thanks everyone in SIG Apps for the great teamwork 🎉