Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-51886

Handling expired kubeconfig

XMLWordPrintable

    • Icon: Task Task
    • Resolution: Fixed
    • Icon: Minor Minor
    • kubernetes-cd-plugin
    • None
    • Plugin version: 0.2.3
      Jenkins version: 2.46.3

      I have properly configured the plugin and I was able to publish to a kubernetes cluster. However, the specified kubeconfig contains an expiration date. How does the plugin handles expired/expiring kubeconfig? Am I supposed to auth a different way so my session doesn't expire? Thanks in advance.

          [JENKINS-51886] Handling expired kubeconfig

          Joandy Iglesias added a comment - - edited

          I figured it out. First, I was creating my kubeconfig as if it was going to be used by kubectl which explains my expiration problem. While reading these plugin docs I found this howto kubeconfig doc. Even after creating it that way I was still unable to access the cluster via the plugin. Finally, this bug report helped me realize I was missing the token from the kubeconfig.

          Joandy Iglesias added a comment - - edited I figured it out. First, I was creating my kubeconfig as if it was going to be used by kubectl which explains my expiration problem. While reading  these plugin docs I found  this howto kubeconfig doc. Even after creating it that way I was still unable to access the cluster via the plugin. Finally, this bug report helped me realize I was missing the token from the kubeconfig.

            azure_devops Azure DevOps
            jiglesias Joandy Iglesias
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: