Handling expired kubeconfig

XMLWordPrintable

    • Type: Task
    • Resolution: Fixed
    • Priority: Minor
    • Component/s: kubernetes-cd-plugin
    • None
    • Environment:
      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.

            Assignee:
            Azure DevOps
            Reporter:
            Joandy Iglesias
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: