Feature: Add optional 'leases' etcd shard#18054
Feature: Add optional 'leases' etcd shard#18054apeabody wants to merge 4 commits intokubernetes:masterfrom
Conversation
|
Hi @apeabody. Thanks for your PR. I'm waiting for a kubernetes member to verify that this patch is reasonable to test. If it is, they should reply with Tip We noticed you've done this a few times! Consider joining the org to skip this step and gain Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. DetailsInstructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
- Allows 'leases' API validation - Maps well-known port assignments - Configures API Server overrides and nodeup DNS mapping - Updates Etcd Manager and TLS Configurations - Implements Node diagnostics, E2E integrations, and log overrides - Introduces mock test fixtures in cluster.go
|
/ok-to-test |
|
@apeabody Could you add some info in the description on why this is useful and who should use it? |
Add documentation about the optional leases etcd shard for megaclusters, including an example configuration.
Adds support for configuring an optional
leasesetcd shard. This shard is specifically designed for megaclusters to isolate the massive volume of high-frequency write traffic generated by node heartbeats. By redirecting this traffic to a dedicatedleasesshard, it prevents the primary etcd database from being overwhelmed, ensuring overall control plane stability.