Exception Request for MaxUnavailable for StatefulSet

[Mayank Kumar]

• Enhancement name: MaxUnavailable for StatefulSet
  
• Enhancement status (alpha/beta/stable): Alpha
  
• SIG: Apps 
  
• Owners: Mayank Kumar,  Ken Owens
  
• k/enhancements repo issue #: https://github.com/kubernetes/enhancements/issues/961
  
• PR #’s: See board: https://github.com/kubernetes/kubernetes/pull/82162
• Additional time needed (in days): Requesting extension to EOD Mon. Mar. 15 (one week)
  
• Reason this enhancement is critical for this milestone:  This is an alpha feature that has been requested for a long time by many users. This is also critical for our internal work at Salesforce for our storage features.
  
• Risks from adding code late: Relatively low , alpha feature, not enabled by default so doesnt affect workloads unless explicitly enabled by customers
  
• Risks from cutting enhancement: Skipping this feature by another 3 months , leading to overall availability by default in EKS/GKE by another 3-6 months.

[Nabarun Pal]

Hi Mayank,

Considering all the circumstances, we have decided to DENY this exception request. At this point in time, we are really considering only release-blocking features. Moreover, the implementation PR (https://github.com/kubernetes/kubernetes/pull/82162) has failing tests and pending reviews.

We hope that you opt-in this enhancement through SIG Apps for the next release cycle.

Best,
Nabarun Pal // Kubernetes 1.21 Release Lead

[Mayank Kumar]

• Enhancement name: MaxUnavailable for StatefulSet
  
• Enhancement status (alpha/beta/stable): Alpha
  
• SIG: Apps 
  
• Owners: Mayank Kumar,  Ken Owens
  
• k/enhancements repo issue #: https://github.com/kubernetes/enhancements/issues/961
  
• PR #’s: See board: https://github.com/kubernetes/kubernetes/pull/82162

• Additional time needed (in days): 2 days, waiting on one review/lgtm, no code changes needed so far
  
• Reason this enhancement is critical for this milestone:  This is an alpha feature and gated , that has been requested for a long time by many users. This is also critical for our internal work at Salesforce for our storage features.
  
• Risks from adding code late: All code changes are in the PR, no additional code changes needed. Alpha feature which is gated and which is disabled by default, so very little risk.
  
• Risks from cutting enhancement: Skipping this feature by another 3 months , leading to overall availability by default in EKS/GKE by another 3-6 months. This feature has been delayed for a year now. Stateful customers will not be able to take advantage of this feature to get faster rollouts. Affecting lot of internal Salesforce customers as well.

[Maciej Szulik]

On behalf of sig-apps leads (Janet, Ken and myself) we're supporting this exception.

--
You received this message because you are subscribed to the Google Groups "kubernetes-sig-release" group.
To unsubscribe from this group and stop receiving emails from it, send an email to kubernetes-sig-re...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/kubernetes-sig-release/CAJArg-o39xLKpaCge-6GMqOP%2BXKJbJHjX8JqgnLCJeSiyg0d8Q%40mail.gmail.com.

[Savitha Raghunathan]

Hi Mayank,

Thank you for filing the exception request! Currently, we are only considering critical and release blocking issues for the v1.22 release. From the slack discussion, it is evident that this is not a release-blocker. Hence, DENYING this exception request.

We look forward to seeing this KEP in v1.23. If you have any questions, please feel free to reach out to us in the #sig-release slack channel.

Regards,

Savitha,

1.22 Release Team Lead

--
To unsubscribe from this group and stop receiving emails from it, send an email to release-team...@kubernetes.io.