Skip to content

Conversation

@fedepaol
Copy link
Member

Fixes #1644

Revert the change of readiness probe, and change the webhook to start the metrics endpoint only after the webhooks are patched properly and thus able to serve.

@fedepaol fedepaol force-pushed the fix/startmetricsafterwebhooks branch from b599893 to 2aeceba Compare October 14, 2022 15:36
@fedepaol fedepaol changed the title Fix/startmetricsafterwebhooks Start the metrics after the webhook is ready Oct 14, 2022
The metrics serve as readiness probe. Helm wait checks for the pods to
be ready, and by doing this we ensure that the metric endpoint accepts
requests only after the webhook is ready to serve requests.

Signed-off-by: Federico Paolinelli <fpaoline@redhat.com>
This reverts commit 6d208de.

The workaround works and now helm waits is able to wait for the webhook
to be ready, but the controller logs are full of errors like
"unable to process a request with an unknown content type".
@fedepaol fedepaol force-pushed the fix/startmetricsafterwebhooks branch from 2aeceba to 57f8342 Compare October 14, 2022 15:45
This reverts commit 9ea03f0.

Reverting to restore the readiness probe to hit the metrics endpoint.
@fedepaol
Copy link
Member Author

Also, tried manually the steps described in #1610 :

helm install metallb  metallb/metallb  --wait --namespace metallb-system
kubectl apply -f configsamples/bgppeer_simple.yaml

And it didn't fail

Copy link
Contributor

@pperiyasamy pperiyasamy left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@zeeke
Copy link
Contributor

zeeke commented Oct 17, 2022

LGTM

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.

metalLB controller error: unable to process a request with an unknown content type

3 participants