-
Notifications
You must be signed in to change notification settings - Fork 39.3k
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
ping kmsplugin gentely when in good state #85828
Conversation
@ShiHan9: Adding the "do-not-merge/release-note-label-needed" label because no release-note block was detected, please follow our release note process to remove it. 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. |
Hi @ShiHan9. 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 Once the patch is verified, the new status will be reflected by the 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. |
/cc @immutableT |
@@ -48,6 +48,7 @@ const ( | |||
kmsTransformerPrefixV1 = "k8s:enc:kms:v1:" | |||
kmsPluginConnectionTimeout = 3 * time.Second | |||
kmsPluginHealthzTTL = 3 * time.Second |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Let's rename this to kmsPluginHealthzNegativeTTL.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Done
/ok-to-test |
/retest |
/release-note-none |
/assign @lavalamp |
/approve |
@@ -261,6 +275,31 @@ func TestKMSPluginHealthz(t *testing.T) { | |||
} | |||
} | |||
|
|||
func TestKMSPluginHealthzTTL(t *testing.T) { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
convert this to table-driven test.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
done
/test pull-kubernetes-e2e-gce-device-plugin-gpu |
@@ -48,7 +48,8 @@ const ( | |||
aesGCMTransformerPrefixV1 = "k8s:enc:aesgcm:v1:" | |||
secretboxTransformerPrefixV1 = "k8s:enc:secretbox:v1:" | |||
kmsTransformerPrefixV1 = "k8s:enc:kms:v1:" | |||
kmsPluginHealthzTTL = 3 * time.Second | |||
kmsPluginHealthzNegativeTTL = 3 * time.Second | |||
kmsPluginHealthzPositiveTTL = 90 * time.Second | |||
) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think this is still too much for the integration test to pass.
I believe this would need to be under 30 seconds, so I suggest 20.
We can follow up with a PR to expose cache TTL so that the integration test could run in reasonable amount of time.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
done
Change-Id: I50ce249d7996e5c51dcbb00e53d67300aa72a87f
/lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: immutableT, lavalamp, shihan9 The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
What type of PR is this?
/kind feature
What this PR does / why we need it:
too many calls to kms when kms provider in good state