Skip to content
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

Closed
chunlongliang-ibm opened this issue Sep 4, 2019 · 7 comments
Closed
Labels
kind/question Further information is requested

Comments

@chunlongliang-ibm
Copy link

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

@chunlongliang-ibm chunlongliang-ibm added the kind/question Further information is requested label Sep 4, 2019
@nak3
Copy link
Contributor

nak3 commented Sep 5, 2019

Did you deploy knative serving with serving-operator https://github.com/knative/serving-operator ?
serving-operator has the bug, though I had confirmed it with old version.

@chunlongliang-ibm
Copy link
Author

We did use knative eventing and serving operators

@nak3
Copy link
Contributor

nak3 commented Sep 5, 2019

Thank you. Can you confirm if following steps to produce the issue on your env?

1. Modify Gateway

# oc edit gateway knative-ingress-gateway --namespace knative-serving

e.g.

BEFORE:

  - hosts:
    - '*'
    port:
      name: https

AFTER:

  - hosts:
    - 'test'
    port:
      name: https

2. Restart one of serving pods

e.g.

# oc delete pod -n knative-serving autoscaler-64c549bcf4-vnq6h

3. Verify Gateway again

Modified 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 ?

@chunlongliang-ibm
Copy link
Author

Thanks! yes, those steps recreate the problem

@chunlongliang-ibm
Copy link
Author

I opened issue knative/serving-operator#160

@nak3
Copy link
Contributor

nak3 commented Sep 5, 2019

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.
So, would you mind closing this issue here, and tracking knative/serving-operator#160? I think you can re-open this issue if you have experienced the issue after knative/serving-operator#160 is solved.

(As far as I tested today, non-operator env does not have this issue for now.)

@chunlongliang-ibm
Copy link
Author

Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/question Further information is requested
Projects
None yet
Development

No branches or pull requests

2 participants