[release/0.7] add featureGate IgnoreLeaseSync to stop sync leases.coordination.k8s.io #621
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
27149chen
changed the title
|
Hi @27149chen, DetailsInstructions for interacting with me using comments are available here. |
Signed-off-by: lou <alex1988@outlook.com> (cherry picked from commit b6eeea8) Signed-off-by: lou <alex1988@outlook.com>
27149chen
force-pushed
the
cherry-pick-615
branch
from
aae898c
to
9140eb7
Compare
Iceber
approved these changes
Dec 20, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What type of PR is this?
/kind feature
What this PR does / why we need it:
cherry-pick #615
This pr adds a featureGate
IgnoreLeaseSyncto stop synchronizing internal resources that the majority of users do not care about. Currently onlyleases.coordination.k8s.iois added since it updates too frequently.Which issue(s) this PR fixes:
Fixes #
Special notes for your reviewer:
Does this PR introduce a user-facing change?: