+++ This bug was initially created as a clone of Bug #1946922 +++ Description of problem: On Ingress details page, `TLS certificate` shows 'Not configured' even a secret is referred Version-Release number of selected component (if applicable): 4.8.0-0.nightly-2021-04-05-174735 How reproducible: Always Steps to Reproduce: 1. create an ingress by specifying a Secret that contains a TLS private key and certificate $ cat > tls-example-ingress.yaml << EOF apiVersion: networking.k8s.io/v1 kind: Ingress metadata: name: tls-example-ingress spec: tls: - hosts: - https-example.foo.com secretName: testsecret-tls rules: - host: https-example.foo.com http: paths: - path: / pathType: Prefix backend: service: name: service1 port: number: 80 EOF $ oc create -f tls-example-ingress.yaml $ oc get ingress tls-example-ingress -o json | jq .spec.tls [ { "hosts": [ "https-example.foo.com" ], "secretName": "testsecret-tls" } ] 2. check Ingress details from Networking -> Ingresses -> tls-example-ingress Actual results: 2. on Ingress details page, `TLS certificate` field shows a value 'Not configured' Expected results: 2. we should render a resource icon and link to the referred secret `testsecret-tls` Additional info:
The fix pr test has passed before merge, and the pr has been included in 4.7.0-0.nightly-2021-05-12-004740. So move the bug to Verified.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (OpenShift Container Platform 4.7.11 bug fix update), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2021:1550