Krish

> we have unit tests / e2e tests that are green, so kubeadm patches work. That's the reason why this is tagged as `documentation`; I tried a bunch of things...

> It would be helpful if you shared your attempted config in full detail, the approach looks right but we can't see all the details here yet. This is my...

I changed the part ``` - role: control-plane kubeadmConfigPatches: - | kind: JoinConfiguration patches: directory: /etc/kubernetes/manifests/patches ``` to ``` - role: control-plane kubeadmConfigPatches: - | kind: InitConfiguration patches: directory: /etc/kubernetes/manifests/patches...

Happens with 1.9.1 here too.

Well I am testing the latest registry in this way: docker run -d -p 5000:5000 --name dckrregistry --restart=always \ -v `pwd`/data:/var/lib/registry \ -v `pwd`/auth:/auth \ -v `pwd`/certs:/certs \ -e "REGISTRY_AUTH=htpasswd"...

And I think the push fails because of the API changes. If my memory serves right, older one used v1.18 or so, and the new one uses v1.21. You can...

> what seems to be in general causing a problem is lots of secrets with big payloads which overall slow down the apiserver I would disagree with this statement as...

> Yeah, you can create a new issue for supporting optional page list when cache initialize, and it is also related to client-go, which haven not yet provided any external...

@FillZpp @pmalek I have pasted my analysis in https://github.com/Kong/kubernetes-ingress-controller/issues/2382#issuecomment-1158746538 if you would want to take a look.

The following points should also be considered: 1. Timeout for long-running queries. Maybe an async process for this might be useful in the future. Another way may be to constrain...