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

feat: use cert ready checker for webhook readiness #721

Merged
merged 1 commit into from
Jan 26, 2023

Conversation

aramase
Copy link
Member

@aramase aramase commented Jan 26, 2023

Signed-off-by: Anish Ramasekar [email protected]

Reason for Change:

Block readiness on the mutating webhook being registered. We can't use mgr.GetWebhookServer().StartedChecker() yet, because that starts the webhook. But we also can't call AddReadyzCheck after Manager.Start. So we need a custom ready check that delegates to the real ready check after the cert has been injected and validator started.

Requirements

  • squashed commits
  • included documentation
  • added unit tests and e2e tests (if applicable).

Issue Fixed:

fixes #709
fixes #719

Please answer the following questions with yes/no:

Does this change contain code from or inspired by another project? If so, did you notify the maintainers and provide attribution?

  • yes
  • no

Notes for Reviewers:

@aramase aramase marked this pull request as ready for review January 26, 2023 09:01
@aramase aramase enabled auto-merge (squash) January 26, 2023 16:30
@aramase aramase merged commit 305d10b into Azure:main Jan 26, 2023
@aramase aramase deleted the readyz-checker branch January 26, 2023 17:15
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

webhook controller pod is ready too soon Webhook pods should not be marked ready until webhook is available
2 participants