You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
UPD
Although I have mitigated it 👍 by adding the port tcp:9876 to the GKE VPC firewall, it is still a bug of the rollouts chart and the operator. One cannot assign any rollout.webhook.port other that 9876! 👎
My usual strategy was to change the webhook port of all operators to 1-2 allowed in my firewall. I don't want to keep more that 3-5 ports in firewall rules, it become complicated and easy to mess up. 💯
The text was updated successfully, but these errors were encountered:
denist-huma
changed the title
kruise-rollout-webhook-service is not accesible in GKE
kruise-rollout-webhook-service is not accesible in GKE, and webhook port other that 9876 not working
Aug 16, 2023
denist-huma
changed the title
kruise-rollout-webhook-service is not accesible in GKE, and webhook port other that 9876 not working
kruise-rollout-webhook-service is not accesible in GKE, and any webhook ports other that 9876 aren't working
Aug 17, 2023
I had a problem following the Kubernetes Manifest CD > Canary Rollout documentation.
Debugging this webhook problem, I think that the root case is port blocking in a private GKE cluster I'm on.
Read The Definitive Debugging Guide for the cert-manager Webhook Pod.
Separate console:
Probe deployment's port:
I try to change webhook port not using vela:
Patching deployment and svc ports from 9876 to the recommended 10250 doesn't help:
The probe deployment's port 10250 not working (allowed by default):
Try https://openkruise.io/rollouts/installation way, set port and vela selector:
Install the chart.
The probe deployment's port 8443 not working (allowed in my firewall):
UPD
Although I have mitigated it 👍 by adding the port tcp:9876 to the GKE VPC firewall, it is still a bug of the rollouts chart and the operator. One cannot assign any rollout.webhook.port other that 9876! 👎
My usual strategy was to change the webhook port of all operators to 1-2 allowed in my firewall. I don't want to keep more that 3-5 ports in firewall rules, it become complicated and easy to mess up. 💯
The text was updated successfully, but these errors were encountered: