[kubernetes/kubernetes] umbrella issue for HA (replicated) API Server (#57213)
Mehdy Bohlool
API Server relies on etcd for HA. But it also has internal objects/states that need to be initialized based on API objects in etcd. Example of that is CRDs that need a http handler. This issue is to keep track of all states we have in API server and make sure all of them are HA ready. Note that most of them are already HA.
- CRD http handler: Coordination required between API servers to mark a CRD as ready (#57042)
- Admission Webhooks: All API servers should became aware of webhooks before they mark as ready. Webhooks should be activated when all API servers are aware of them. (need an issue)
- Audit api server code for more issues
@kubernetes/sig-api-machinery-misc
—
You are receiving this because you are on a team that was mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.
Walter Fender
cc @cheftako
Jenny Buckley
Xiang Li
/cc @rphillips
Lucas Käldström
fejta-bot
Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close.
Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale
fejta-bot
Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
If this issue is safe to close now please do so with /close.
Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten
/remove-lifecycle stale
Jenny Buckley
/remove-lifecycle rotten
/lifecycle frozen
Jenny Buckley
/lifecycle frozen
Lucas Käldström
What's the status of this issue from a SIG API Machinery standpoint?
Dr. Stefan Schimanski
What's the status of this issue from a SIG API Machinery standpoint?
This topic was discussed in last sig-api-machinery meeting. But there is not more than general acknowledgement of the issue. Nobody came up with a design to solve it.
Lubomir I. Ivanov
this is an old one, but leaving it open.
/remove-sig cluster-lifecycle
^ please request discussion if needed.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are on a team that was mentioned.