Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[3.5] backport backoff/retry config #17363

Merged
merged 1 commit into from
Feb 5, 2024

Conversation

dusk125
Copy link
Contributor

@dusk125 dusk125 commented Feb 2, 2024

Backporting #17307 to 3.5 to allow kubernetes to consume these new options as they are on etcd release-3.5.

Addresses #17272.

Signed-off-by: Allen Ray <alray@redhat.com>
@k8s-ci-robot
Copy link

Hi @dusk125. Thanks for your PR.

I'm waiting for a etcd-io member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Instructions 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/test-infra repository.

Copy link
Member

@ahrtr ahrtr left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm

cc @serathius

Please also add a changelog item for 3.5 if merged.

@tjungblu
Copy link
Contributor

tjungblu commented Feb 5, 2024

/lgtm (non-binding)

@ahrtr ahrtr merged commit 3c8e389 into etcd-io:release-3.5 Feb 5, 2024
15 checks passed
@dusk125 dusk125 deleted the 3.5-backport-retry-config branch February 5, 2024 15:40
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

Successfully merging this pull request may close these issues.

5 participants