Uploaded image for project: 'National Data Service'
  1. National Data Service
  2. NDS-222

Restarting Kubernetes using kube-up.sh causes tokens/certificates to be out of sync

XMLWordPrintableJSON

    • Icon: Bug Bug
    • Resolution: Won't Fix
    • Icon: Minor Minor
    • None
    • None
    • Development, Infrastructure
    • None

      When you start a local/developer Kubernetes instance using our kube-up.sh script, certificates are generated that are used for token authentication. If you subsequently run kube-down.sh and then kube-up.sh, the certificates and tokens can be out of sync between previously run pods.

      This task encompasses work to resolve this problem. This will likely entail modifications to kube-up.sh and kube-down.sh to resolve.

              Unassigned Unassigned
              willis8 Craig Willis
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: