Bug 1946922 - Ingress details page doesn't show referenced secret name and link
Summary: Ingress details page doesn't show referenced secret name and link
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Management Console
Version: 4.8
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
: 4.8.0
Assignee: Joe Caiani
QA Contact: Yadan Pei
URL:
Whiteboard:
Depends On:
Blocks: 1948958
TreeView+ depends on / blocked
 
Reported: 2021-04-07 09:03 UTC by Yadan Pei
Modified: 2021-07-27 22:58 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-07-27 22:57:54 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github openshift console pull 8623 0 None open Bug 1946922: Fix ingress details page to show referenced secret name 2021-04-12 16:47:27 UTC
Github openshift console pull 8645 0 None open Bug 1946922: update render of multiple secrets with resource icon/text pairs 2021-04-13 20:56:40 UTC
Red Hat Product Errata RHSA-2021:2438 0 None None None 2021-07-27 22:58:17 UTC

Description Yadan Pei 2021-04-07 09:03:47 UTC
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:

Comment 3 Samuel Padgett 2021-04-16 13:55:11 UTC
Moving back to ON_QA. The intent of the existing code was to show the secret name as plain text, and it wasn't showing up due to a bug. We can open a separate issue to make it a link, which is a more involved fix.

Comment 4 Yadan Pei 2021-04-19 01:54:59 UTC
based on discussion https://github.com/openshift/console/pull/8645#issuecomment-821192481, this bug is only used to track the plain text is shown which is already fix. Multiple secrets should be rendered with link is tracked in another bug


Verified on 4.8.0-0.nightly-2021-04-18-101412

Comment 7 errata-xmlrpc 2021-07-27 22:57:54 UTC
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 (Moderate: OpenShift Container Platform 4.8.2 bug fix and security 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/RHSA-2021:2438


Note You need to log in before you can comment on or make changes to this bug.