Guys I have an Ansible for activating a k8s master: -

Question

Guys I have an Ansible for activating a k8s master: -

name: Activate Master node
hosts: all
tasks:
- name: Export2
shell: kubectl version | base64 | tr -d '\n'
register: output
#become: yes
- name: Exec all
shell: kubectl apply -f "https://cloud.weave.works/k8s/net?k8s-version={{ output.stdout }}"
~
I will execute this as root. but the last command will not execute with an error like this:
fatal: [185.255.91.121]: FAILED! => {"changed": true, "cmd": "kubectl apply -f \"https://cloud.weave.works/k8s/net?k8s-version=Q2xpZW50IFZlcnNpb246IHZlcnNpb24uSW5mb3tNYWpvcjoiMSIsIE1pbm9yOiIyMiIsIEdpdFZlcnNpb246InYxLjIyLjAiLCBHaXRDb21taXQ6ImMyYjUyMzdjY2Q5YzBmMWQ2MDBkMzA3MjYzNGNhNjZjZWZkZjI3MmYiLCBHaXRUcmVlU3RhdGU6ImNsZWFuIiwgQnVpbGREYXRlOiIyMDIxLTA4LTA0VDE4OjAzOjIwWiIsIEdvVmVyc2lvbjoiZ28xLjE2LjYiLCBDb21waWxlcjoiZ2MiLCBQbGF0Zm9ybToibGludXgvYW1kNjQifQo=\"", "delta": "0:00:00.077468", "end": "2021-08-08 07:17:20.846559", "msg": "non-zero return code", "rc": 1, "start": "2021-08-08 07:17:20.769091", "stderr": "The connection to the server localhost:8080 was refused - did you specify the right host or port?", "stderr_lines": ["The connection to the server localhost:8080 was refused - did you specify the right host or port?"], "stdout": "", "stdout_lines": []}
But I can execute it manually on the target server. what can be the reason?

0

08.08.2021

17 ответов

31 просмотр

Ehsan Автор вопроса

Raptor Blue Bear
Read the error message

I've read that error message, but the same command will execute manually What should be the reason?

0

08.08.2021

Sharuzzaman Ahmat Raslan

Ehsan
I've read that error message, but the same command...

Using which user when it works?

0

08.08.2021

Ehsan Автор вопроса

Sharuzzaman Ahmat Raslan
Using which user when it works?

root

0

08.08.2021

Ehsan Автор вопроса

Sharuzzaman Ahmat Raslan
Using which user when it works?

and I run playbook using -i root@myserver

0

08.08.2021

Ehsan Автор вопроса

Sharuzzaman Ahmat Raslan
Using which user when it works?

Is there any clue?

0

08.08.2021

Raptor Blue Bear

Ehsan
Is there any clue?

Yes, your kubeconfig is not being picked up. Hence the localhost:8080 (the unconfigured default)

0

08.08.2021

Ehsan Автор вопроса

Raptor Blue Bear
Yes, your kubeconfig is not being picked up. Hence...

So why that command executes on target server manually?

0

08.08.2021

Ehsan Автор вопроса

Raptor Blue Bear
Yes, your kubeconfig is not being picked up. Hence...

0

08.08.2021

Ehsan Автор вопроса

Raptor Blue Bear
Yes, your kubeconfig is not being picked up. Hence...

Same command through Ansible

0

08.08.2021

Sathya Bhat

Ehsan

Check your environment variables. Probably kubeconfig is setup for login shell but not for your ansible

0

08.08.2021

Raptor Blue Bear

Ehsan

Same command through Ansible

Same thing applies. When the command runs as the Ansible user it is not using the kubeconfig. Fix that

0

08.08.2021

Ehsan Автор вопроса

Sathya Bhat
Check your environment variables. Probably kubecon...

Thats it, my playbook can not recognize KUBECONFIG inside .bashrc

0

08.08.2021

Raptor Blue Bear

Ehsan
Thats it, my playbook can not recognize KUBECONFIG...

That's because ansible isn't really doing things through the shell, it's transferring modules and executing scripts that it transfers, not using a login shell.

0

08.08.2021

Ehsan Автор вопроса

Raptor Blue Bear
That's because ansible isn't really doing things t...

What should I do?

0

08.08.2021

Alireza

define KUBECONFIG environment variable in your playbook.

0

08.08.2021

Viking