The bitnami chart that we're using for metrics-server expects the underlying daemon to be listening on port 8443. When we made this change, we inadvertently caused metrics-server to start listening on the default port of 443. This means that liveness probes are failing, causing metrics-server deploys to fail.
Safety checklist
[x] This change is backwards compatible and safe to apply by existing users
[x] This change will NOT lead to data loss
[x] This change will NOT lead to downtime who already has an env/service setup
How has this change been tested, beside unit tests?
I have not tested this change, but reading through the code I'm confident this should fix it.
Description
The bitnami chart that we're using for
metrics-serverexpects the underlying daemon to be listening on port 8443. When we made this change, we inadvertently causedmetrics-serverto start listening on the default port of443. This means that liveness probes are failing, causingmetrics-serverdeploys to fail.Safety checklist
How has this change been tested, beside unit tests?
I have not tested this change, but reading through the code I'm confident this should fix it.