Uploaded image for project: 'Red Hat Cluster Management Cloud Services'
  1. Red Hat Cluster Management Cloud Services
  2. CMCS-102

kubeconfig and password secret should be made from the infraID instead of hd.Name

XMLWordPrintable

      As the end-user only knows the infra-ID (which is how the imported cluster are displayed on the UI), it will make more sense to have kubeconfig/password secret build from the infraID rather than the hd.Name.

      For example:

      oc get secret -n itdove-hyp1-spoke

itdove-hyp1-spoke-itdove-hyp1-spoke-hd-admin-kubeconfig                     Opaque                                1      3d2h
itdove-hyp1-spoke-itdove-hyp1-spoke-hd-kubeadmin-password                   Opaque                                1      3d2h

      should be

      itdove-hyp1-spoke-itdove-hyp1-spoke-hd-xxxx-admin-kubeconfig                     Opaque                                1      3d2h
itdove-hyp1-spoke-itdove-hyp1-spoke-hd-xxxx-kubeadmin-password                   Opaque                                1      3d2h

      So from

      {hostingNs}-{hd.Name}-kubeadmin-password to{hostingNs}

      -

      {hd.InfraID}

      -kubeadmin-password

              phwu@redhat.com Philip Wu
              itdove Dominique Vernier
              Juliana Hsu Juliana Hsu (Inactive)
              Roke Jung Roke Jung
              Joshua Packer Joshua Packer
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: