-
Notifications
You must be signed in to change notification settings - Fork 32
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
✨ adding additional waits to prevent e2e cert-manager failures #441
Conversation
Signed-off-by: Jordan Keister <[email protected]>
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #441 +/- ##
=======================================
Coverage 37.83% 37.83%
=======================================
Files 15 15
Lines 1208 1208
=======================================
Hits 457 457
Misses 701 701
Partials 50 50 ☔ View full report in Codecov by Sentry. |
|
||
kubectl_wait "cert-manager" "deployment/cert-manager" "60s" | ||
kubectl wait mutatingwebhookconfigurations/cert-manager-webhook --for=jsonpath='{.webhooks[0].clientConfig.caBundle}' --timeout=60s | ||
kubectl wait validatingwebhookconfigurations/cert-manager-webhook --for=jsonpath='{.webhooks[0].clientConfig.caBundle}' --timeout=60s | ||
kubectl apply -f "${catalogd_manifest}" |
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.
Nit, loss of a blank line here...
upgrade-e2e script cannot pass until #440 merges. |
Signed-off-by: Jordan Keister <[email protected]>
d8dc9e7
We've encountered cert-manager failures in e2e, installing from release, and running the demo updates. This introduces some additional waits on cert-manager resources to attempt to reduce these.