PodDisruptionBudget progress to v1?

[Jordan Liggitt]

Hello sig-apps / sig-scheduling,

I'm sweeping through the APIs currently in beta , and am looking for some information about the PodDisruptionBudget API.

What is the roadmap and timeline to v1 for this API? These are the issues I could find:

• https://github.com/kubernetes/kubernetes/issues/25321 described promotion to v1 as a no-op, but that issue is now closed.
• https://github.com/kubernetes/kubernetes/issues/45398 describes a specific pain point (immutability of PDB objects).

Letting API objects stay in perpetual beta state sends mixed signals to the community about fitness for use, long-term plans, and overall support level. Clarifying the plan for this API would be very helpful.

Thanks in advance,

Jordan

[Bobby Salamat]

I totally agree that we should not leave our API in alpha/beta state for a long time.

Regarding PDB, David knows better how critical the requirements listed in https://github.com/kubernetes/kubernetes/issues/25321 are. AFAIK, "disruption rate" and "spreading by PDB" are not implemented. Given that the issue was filed over two years ago, we should probably revisit it and find the "MVP" for the feature to move to GA.

To be more focused, if we keep the current functionality of PDB and only make it updatable, would it be enough to move the API to GA?

Thanks,

Bobby

--
You received this message because you are subscribed to the Google Groups "kubernetes-sig-scheduling" group.
To unsubscribe from this group and stop receiving emails from it, send an email to kubernetes-sig-sch...@googlegroups.com.
To post to this group, send email to kubernetes-s...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/kubernetes-sig-scheduling/CAMBP-pLbtn7QUkwRKviz9FY9usmKAitK4h-ka5HydnSyrCVkGw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.