kubernetes plugin for teamcity

hi i try to connect teamcity kubernetes plugin to my cluster .

Firstly in the log i 've seen

WARN - bric8.kubernetes.client.Config - Error reading service account token from: [/var/run/secrets/kubernetes.io/serviceaccount/token]. Ignoring.

I've rename the directoy on serviceaccount

 :/var/run/secrets/kubernetes.io# ls -l
total 0
drwxr-xr-x 2 root root 60  4 jui 10:30 serceaccount

Connection failed!

 

when i click on Test connection in cloud profiles (i ve chosen Token) to kubernetes i've

[2018-07-12 15:26:31,582] DEBUG [nio-8112-exec-2] - .web.KubeProfileEditController - Error while checking connection to k8s api. Error connecting to https://xxxxx/api/v1: Unexpected response code for CONNECT: 503

 

If i execute curl command on the server everything work

pps/jetbrains/TeamCity_2017.2.4/logs# curl https://xxxxxxxx/api/v1 -k --header "Authorization: Bearer $TOKEN"
{
  "kind": "APIResourceList",
  "groupVersion": "v1",
  "resources": [
    {
      "name": "bindings",

 

Version:
Kubernetes support plugin : snapshot-20180412111013
TeamCity Professional 2018.1 EAP (build 57605)

3 comments
Comment actions Permalink
Official comment

Hello, Olivier

Which authorization scheme have you used in latest example when you got 503 response?

If it is 'service account token' please enable debug-all logging preset, do 'test connection' and share logs with us.

Thank you!

Comment actions Permalink

It was with token .

How can i enable debug-all loging  ?

0
Comment actions Permalink

i've enable the debug.all loging  and restart TC  however when i click on test connection i dont have a full stack of logs .

i explain as well to the developper i think there is a problem with the plugin. The plugin search for a directory  serceaccout but it create serviceaccount  maybe it's not the only one problem.

more information here - >  https://github.com/JetBrains/teamcity-kubernetes-plugin/issues/35

0

Please sign in to leave a comment.