-
Notifications
You must be signed in to change notification settings - Fork 89
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: Add K8s API communication check on startup #387
feat: Add K8s API communication check on startup #387
Conversation
8bb10f5
to
d3c64e9
Compare
Codecov Report
@@ Coverage Diff @@
## master #387 +/- ##
=======================================
Coverage 49.80% 49.80%
=======================================
Files 54 54
Lines 4883 4905 +22
=======================================
+ Hits 2432 2443 +11
- Misses 2202 2212 +10
- Partials 249 250 +1
Flags with carried forward coverage won't be shown. Click here to find out more.
Continue to review full report at Codecov.
|
d3c64e9
to
738b865
Compare
Signed-off-by: Mike Smith <10135646+mjsmith1028@users.noreply.github.com>
d74d0ea
to
f6205b8
Compare
Signed-off-by: Mike Smith <10135646+mjsmith1028@users.noreply.github.com>
🎉 This PR is included in version 2.1.0 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
The purpose of this PR is to avoid container restarts on startup when metacontroller is in a service mesh (istio, kuma, etc). If the service mesh sidecar takes longer to come up than metacontroller, then metacontroller will have container restarts. The K8s API healthcheck lets us know that the sidecar is properly communicating and the API server is healthy.