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

Deploy KMS plugin with readiness probe #113

Open
nilekhc opened this issue Jun 25, 2021 · 0 comments
Open

Deploy KMS plugin with readiness probe #113

nilekhc opened this issue Jun 25, 2021 · 0 comments
Assignees
Labels
bug Something isn't working

Comments

@nilekhc
Copy link
Contributor

nilekhc commented Jun 25, 2021

Describe the bug
While performing upgrade test it is found that create secret test fails with error: failed to create secret Internal error occurred: rpc error: code = DeadlineExceeded desc = latest balancer error: connection error: desc = "transport: Error while dialing dial unix /opt/azurekms.socket: connect: no such file or directory"

One of the reason could be that code is not yet ready to receive traffic. Adding sleep after upgrade help pass the test consistently.

Investigate if we can deploy AKV KMS plugin with readiness probe.

Steps To Reproduce
It's a flake in e2e_upgrade_tests

Expected behavior
e2e_upgrade_tests should always pass.

KMS Plugin for Key Vault version
v0.0.12

Kubernetes version

Additional context

@nilekhc nilekhc added the bug Something isn't working label Jun 25, 2021
@nilekhc nilekhc self-assigned this Jun 25, 2021
@aramase aramase added this to the v0.1.0 milestone Oct 4, 2021
@aramase aramase removed this from the v0.1.0 milestone Mar 29, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants