-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Need to recreate knative-ingress-gateway every couple hours #5393
Comments
Did you deploy knative serving with serving-operator https://github.com/knative/serving-operator ? |
We did use knative eventing and serving operators |
Thank you. Can you confirm if following steps to produce the issue on your env? 1. Modify Gateway
e.g. BEFORE:
AFTER:
2. Restart one of serving podse.g.
3. Verify Gateway againModified Gateway is initialized. If the issue on above step-3 happens, I am sure that you hit a operator's bug. So can you file the bug ticket against https://github.com/knative/serving-operator ? |
Thanks! yes, those steps recreate the problem |
I opened issue knative/serving-operator#160 |
Thank you. I believe that the operator has some(actually many) triggers to initialize the gateway as we saw knative/serving-operator#160 as an example. (As far as I tested today, non-operator env does not have this issue for now.) |
Thanks! |
I edit the following gateway yaml to enable TLS
kubectl edit gateway -n knative-serving knative-ingress-gateway -o yaml
by adding
tls:
mode: SIMPLE
privateKey: /etc/istio/ingressgateway-certs/tls.key
serverCertificate: /etc/istio/ingressgateway-certs/tls.crt
However, every couple hours, my configuration is erased, and back to default. I do NOT have any of following configuration enabled as discussed in issue 5181,
enabled AutoTLS
enabled Gateway reconciliation
The text was updated successfully, but these errors were encountered: