Failed To Deploy to Kubernetes Cluster Due to Message: Unauthorized! Token may have expired! Please log-in again. Unauthorized.

[ruigulala]

Description

When I was trying to deploy the following project, I'm having an 401.
https://bitbucket.org/employersappdev/ssldemo.git

Info

Caused by: io.fabric8.kubernetes.client.KubernetesClientException: Failure executing: GET at: https://api.ruig-maven-3446ee10-951b-11e8-9617-02418d964b18.cascade-dev.cascade-domain.com/. Message: Unauthorized! Token may have expired! Please log-in again. Unauthorized.
at io.fabric8.kubernetes.client.dsl.base.OperationSupport.requestFailure (OperationSupport.java:472)
at io.fabric8.kubernetes.client.dsl.base.OperationSupport.assertResponseCode (OperationSupport.java:409)
at io.fabric8.kubernetes.client.dsl.base.OperationSupport.handleResponse (OperationSupport.java:381)
at io.fabric8.kubernetes.client.dsl.base.OperationSupport.handleResponse (OperationSupport.java:344)
at io.fabric8.kubernetes.client.dsl.base.OperationSupport.handleResponse (OperationSupport.java:328)
at io.fabric8.kubernetes.client.dsl.base.BaseOperation.getRootPaths (BaseOperation.java:215)
at io.fabric8.kubernetes.client.BaseClient.rootPaths (BaseClient.java:140)
at io.fabric8.kubernetes.api.KubernetesHelper.isOpenShift (KubernetesHelper.java:2191)
at io.fabric8.maven.plugin.mojo.build.ApplyMojo.executeInternal (ApplyMojo.java:336)
at io.fabric8.maven.plugin.mojo.AbstractFabric8Mojo.execute (AbstractFabric8Mojo.java:74)
at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo (DefaultBuildPluginManager.java:134)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:208)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:154)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:146)
at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:117)
at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:81)
at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build (SingleThreadedBuilder.java:51)
at org.apache.maven.lifecycle.internal.LifecycleStarter.execute (LifecycleStarter.java:128)

However, when I try to reproduce it using curl, I got the correct response.

curl -ik https://api.ruig-maven-3446ee10-951b-11e8-9617-02418d964b18.cascade-dev.cascade-domain.com:443 -H "Authorization: Bearer eyJhbGciOiJSUzI1NiJ9.eyJzdWIiOiJydWblablabla"

The token is stored in .kube/config.

• f-m-p version : 3.5.40
• Maven version (mvn -v) : 3.5.2

• Kubernetes / OpenShift setup and version : 1.10.2
• If it's a bug, how to reproduce :

1. Download source code from https://bitbucket.org/employersappdev/ssldemo.git
2. Make sure the kubernetes cluster is logged in(run kubectl get pods).
3. Run mvn package fabric8:build fabric8:deploy

• If it's a feature request, what is your use case :
• Sample project : [https://bitbucket.org/employersappdev/ssldemo.git]

[rhuss]

Do you also have the right context set ? Can you do a kubectl get pods on the same shell ?

[ruigulala]

Yes, kubectl get pods works as expected.
In the kubectl config, we're using --embed-certs=false. Not sure if this causes the problem.

[stale]

This issue has been automatically marked as stale because it has not had any activity since 90 days. It will be closed if no further activity occurs within 7 days. Thank you for your contributions!

[rhuss]

@ruigulala sorry for the delay. If this is still an issue (is it ?), we should investigste it of course.

[stale]

This issue has been automatically marked as stale because it has not had any activity since 90 days. It will be closed if no further activity occurs within 7 days. Thank you for your contributions!

[egor-ryashin]

Got that exception several times in a row and then it's just gone. I believe it relates more to K8s service not the client.