-
Notifications
You must be signed in to change notification settings - Fork 200
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
Validating webhook times out #1054
Comments
issue in the helm chart then?
|
No scratch that. I spoke too soon. |
My bad - I just took a closer look into the deployment manifests, and it looks like we only changed the target port of the webhook server, and the |
@twuyts Can you provide the steps that you took to perform the upgrade? I can try and see if I can reproduce the issue. edit: I was suspecting you might need to manually update the |
The upgrade is managed through the helm-controller, part of Flux, the solution we use for continuous delivery. |
Seeing a similar errors after upgrading to v0.25.1 We use helm chart:
We have an istio-proxy sidecar in operator pod. Operator logs have entries like:
For us, using PERMISSIVE mode is not acceptable, only STRICT, but that doesn't seem an issue,
So doesn't seem to be an issue like istio/istio#39290 |
the same reconcile error with PERMISSIVE mode
tried also to exclude 9443 port:
no luck |
Description
After upgrading from koperator v0.23.1 to v0.25.1, the validating webhook for kafkaclusters fails:
The same error is thrown when manually updating a kafkacluster resource
Expected Behavior
The error should not occur.
Actual Behavior
A timeout error is thrown.
Affected Version
v0.25.1
Steps to Reproduce
kubectl -n kafka apply -f config/samples/simplekafkacluster.yaml
Error from server (InternalError): error when creating "tmp/cluster.yaml": Internal error occurred: failed calling webhook "kafkaclusters.kafka.banzaicloud.io": failed to call webhook: Post "https://kafka-operator-operator.kafka.svc:443/validate-kafka-banzaicloud-io-v1beta1-kafkacluster?timeout=10s": context deadline exceeded
Checklist
The text was updated successfully, but these errors were encountered: