#Kubernetes ComponentStatus finally deprecated in 1.19.
I’m still a little grumpy that my team got disbanded back in 2016, before I could get full Component registration merged.https://github.com/kubernetes/kubernetes/pull/93570 …
-
-
Replying to @KarlKFI
I also wish that was completed. It's even more obvious now that we need a way to register non-pod endpoints, and that we need to monitor system components and add-ons.
1 reply 0 retweets 8 likes -
Replying to @bgrant0607
I haven’t been paid to do any upstream work since then or I might have done it myself. It’s kind of a lot of work for someone to do as a side project tho, especially with the SIG politicking and KEP process.
1 reply 0 retweets 2 likes -
Replying to @KarlKFI @bgrant0607
I was honestly afraid of KEP process, but it has turned out to be a big net positive IMO. Much easier to review big things early, and it hasn't been too much of a drag for small things.
1 reply 2 retweets 7 likes -
Replying to @thockin @bgrant0607
I’m not complaining about the KEP process, per say. For a substantial enhancement like this tho, it’s a multi-month process to propose, pitch, get approval, implement, review, and merge. And it’s longer if you can’t get approval and need to demonstrate PoC on a fork or CRD.
2 replies 0 retweets 1 like -
It’s just really hard to do a long project like that for free in your spare time. It would need to benefit some specific other project your employer wants done.
2 replies 0 retweets 1 like
Yes, it takes at least a year to take a new API from inception to GA, and longer to address feedback once people start using it, and then it needs to be maintained forever. So not really feasible for most independent contributors.
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.