[JIRA] (JENKINS-52593) Support EKS authentication, or specifying a kubeconfig directly

[tallisk...@gmail.com (JIRA)]

Title: Message Title

Tallis Vanek commented on JENKINS-52593   Re: Support EKS authentication, or specifying a kubeconfig directly Thanks for the summary Konrad, I was able to follow along with my setup. My Jenkins master is trying to authenticate with the entire kube config tucked away in a secret. Also, I can see that my jenkins user on the master is able to run the token 'aws eks get-token' successfully. I am however running into the "Message: Unauthorized! Token may have expired! " issue, even with my Jenkins master configured to use the correct java opt /etc/alternatives/java -Dcom.sun.akuma.Daemon=daemonized -Dorg.csanchez.jenkins.plugins.kubernetes.clients.cacheExpiration=60 -DJENKINS_HOME=/var/lib/jenkins -jar /usr/lib/jenkins/jenkins.war ... I'm wondering what else can be involved, and how I can verify that the cache is actually the issue. Do you have any ideas? Some info: openjdk version "1.8.0_222" ami linux: 4.14.152-127.182.amzn2.x86_64 jenkins kube plugin: org.csanchez.jenkins.plugins:kubernetes:1.22.0 Jenkins: 2.208  kubectl: v1.17.0 / v1.14.8-eks-b8860f aws-cli/1.16.303 Python/2.7.16 Linux/4.14.152-127.182.amzn2.x86_64 botocore/1.13.39 Thanks in advance. Add Comment   This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.192436.1531774635000.7349.1576273020311%40Atlassian.JIRA.