Uploaded image for project: 'Knative Serving'
  1. Knative Serving
  2. SRVKS-200

Gateway is reinitialized when one of serving pods re-started

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Minor Minor
    • None
    • None
    • Operator
    • None

      Steps to reproduce

      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 

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

      3. Verify Gateway again

      Actual behavior

      Modified Gateway is initialized.

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

      Expected behavior

      Gateway settings is persist.

       

      Due to this issue, we cannot add TLS certs manually like this docs https://knative.dev/docs/serving/using-a-tls-cert/#manually-adding-a-tls-certificate

              Unassigned Unassigned
              rhn-support-knakayam Kenjiro Nakayama (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: