Increase quota-bytes for etcd in v3 mode

[wojtek-t]

Ref #20504

---

This change is

[wojtek-t]

Fixed verify - reapplying label.

[k8s-ci-robot]

Jenkins verification failed for commit fc1a3c0cc674654c3ba14f53ec45e4dfeac3e0b1. Full PR test history.

The magic incantation to run this job again is @k8s-bot verify test this. Please help us cut down flakes by linking to an open flake issue when you hit one in your PR.

[xiang90]

4GB is really the dangerous line for etcd (see Chubby's or PaxosDB's limit? I know ZK or Consul wont handle this well). I hope people who run large clusters have good networking + disk... I might optimize this eventually, but do not expect that we can make this number 40GB. Just a reminder.

[k8s-ci-robot]

Jenkins GCI GKE smoke e2e failed for commit ca99cbc. Full PR test history.

The magic incantation to run this job again is @k8s-bot gci gke e2e test this. Please help us cut down flakes by linking to an open flake issue when you hit one in your PR.

[k8s-ci-robot]

Jenkins GKE smoke e2e failed for commit ca99cbc. Full PR test history.

The magic incantation to run this job again is @k8s-bot cvm gke e2e test this. Please help us cut down flakes by linking to an open flake issue when you hit one in your PR.

[wojtek-t]

but do not expect that we can make this number 40GB. Just a reminder.

@xiang90 - yes sure; That's completely fine.

[wojtek-t]

Also - I would like to reduce this value in the future, but I've seen it happening in large clusters, to increasing it for now. I'm planning to understand this and decrease it in future releases.

[xiang90]

Also - I would like to reduce this value in the future, but I've seen it happening in large clusters, to increasing it for now. I'm planning to understand this and decrease it in future releases.

Awesome. I would love to help.

[k8s-github-robot]

@k8s-bot test this [submit-queue is verifying that this PR is safe to merge]

[k8s-github-robot]

Automatic merge from submit-queue