/sig storage
/sig node
/sig scalability

@saad-ali

/stage alpha

@palnabarun - KEP has just been approved as implementable; can we start tracking it?

Hi @wojtek-t , the 1.18 Enhancements team will reach out when the release cycle for 1.18 begins to flip the tracked status and set the milestone.

Thank you for the updates on this enhancement.

@wojtek-t Thanks for the update. We'll track this for 1.18.

For your awareness, the release schedule is:

Monday, January 6th - Release Cycle Begins
Tuesday, January 28th EOD PST - Enhancements Freeze
Thursday, March 5th, EOD PST - Code Freeze
Monday, March 16th - Docs must be completed and reviewed
Tuesday, March 24th - Kubernetes 1.18.0 Released

Please make sure all the k/k PRs link here so we can track them.

/milestone v1.18

Hello, @wojtek-t I'm 1.18 docs lead.
Does this enhancement work planned for 1.18 require any new docs (or modifications to existing docs)? If not, can you please update the 1.18 Enhancement Tracker Sheet (or let me know and I'll do so)
If so, just a friendly reminder we're looking for a PR against k/website (branch dev-1.18) due by Friday, Feb 28th, it can just be a placeholder PR at this time. Let me know if you have any questions!

Yes we will add some doc - I will open it by the deadline.

Hey @wojtek-t, code freeze is March 5. Please link any PRs that are needed to complete this for 1.18, so we can track them in the release team. Thanks!

We seem to be code-complete, unless we find some issue. So only docs are missing.

Hello @wojtek-t
We are close to the docs placeholder PR deadline i.e less than week left for docs placeholder PR against the dev-1.18 branch. Having a placeholder PR in place will definitely help us in tracking enhancements much better.

Thanks! :)

I opened kubernetes/website#19297 - it's the only remaining thing for Alpha

We seem to be complete for Alpha.

@wojtek-t If you have a cluster with a large count of big unconsumed secrets this won't help the initial list that kubelet does to start it's watches right?

I think I'm not fully following. When Kubelet is observing new pod (or update of existing one) it is doing a get (technically it's a list with field selector for metadata.name which translates it to get) for all not yet watched ones. Each of them is pretty cheap on their own as it returns a single item basically.

Kubelet is NOT listing/watching anything that none of its own pods are mounting.

I didn't read the whole helm/helm#8977 but the initial analysis doesn't seem correct because of the above. You would need to look into what kinds of requests are happening on kube-apiserver to understand better.

Hmm my assumption was that kubelet was doing a list/watch on all secrets at startup so it could update any mounted secret for it's pods. Let me confirm what were seeing in clusters with heavy large secret usage at kubelet startup

Yeah - that's not true. Kubelet is not listing everything - it's getting/watching one-by-one and only those that are used by the pods it's running.

/milestone v1.21

Updated KEP is merged: #2179

Hi @wojtek-t, 1.21 Enhancements Lead here.
I see that you’ve opted in this enhancement into 1.21, but I also see that this is tagged with participation from the SIG app, node, scalability. Is that accurate? If so, is there work that other SIGs must deliver in 1.21 as well?

With kubernetes/kubernetes#97615 we're already code-complete.
The only missing bit is to update the documentation to reflect that the feature will get GA-ed.

cc @xiaobaitusi

kubernetes/website#26477 opened for documentation

kubernetes/website#26477 has merged

This is now both:

• code-complete
• documentation complete

Hi @wojtek-t

With code/doc complete, if you update the kep.yaml to reflect a status of implemented, we can also close out this issue.

Let's wait until code-freeze to ensure nothing will get reverted. And I will do that.

Hi @wojtek-t friendly reminder to update the kep status (#1412 (comment)) so that this issue can be closed out :) thanks!

#2615 out for review