reachlin/k8s0

Another minimal kubernetes with ansible

k8s0's Issues

api server is not able to start

please see below issue, how to resolve ?

TASK [apiserver : Wait for api server] *****************************************
task path: /home/famous/k8s0/roles/apiserver/tasks/main.yml:22
Using module file /usr/lib/python2.7/dist-packages/ansible/modules/utilities/logic/wait_for.py
ESTABLISH LOCAL CONNECTION FOR USER: root
EXEC /bin/sh -c 'echo ~root && sleep 0'
EXEC /bin/sh -c '( umask 77 && mkdir -p "echo /root/.ansible/tmp/ansible-tmp-1527946683.01-256363484286943" && echo ansible-tmp-1527946683.01-256363484286943="echo /root/.ansible/tmp/ansible-tmp-1527946683.01-256363484286943" ) && sleep 0'
PUT /root/.ansible/tmp/ansible-local-109103K6WW9/tmpItdCGH TO /root/.ansible/tmp/ansible-tmp-1527946683.01-256363484286943/wait_for.py
EXEC /bin/sh -c 'chmod u+x /root/.ansible/tmp/ansible-tmp-1527946683.01-256363484286943/ /root/.ansible/tmp/ansible-tmp-1527946683.01-256363484286943/wait_for.py && sleep 0'
EXEC /bin/sh -c '/usr/bin/python /root/.ansible/tmp/ansible-tmp-1527946683.01-256363484286943/wait_for.py && sleep 0'
EXEC /bin/sh -c 'rm -f -r /root/.ansible/tmp/ansible-tmp-1527946683.01-256363484286943/ > /dev/null 2>&1 && sleep 0'
The full traceback is:
File "/tmp/ansible_VVKTLA/ansible_module_wait_for.py", line 542, in main
s = _create_connection(host, port, min(connect_timeout, alt_connect_timeout))
File "/tmp/ansible_VVKTLA/ansible_module_wait_for.py", line 407, in _create_connection
connect_socket = socket.create_connection((host, port), connect_timeout)
File "/usr/lib/python2.7/socket.py", line 571, in create_connection
raise err

fatal: [node0]: FAILED! => {
"changed": false,
"elapsed": 300,
"invocation": {
"module_args": {
"active_connection_states": [
"ESTABLISHED",
"FIN_WAIT1",
"FIN_WAIT2",
"SYN_RECV",
"SYN_SENT",
"TIME_WAIT"
],
"connect_timeout": 5,
"delay": 9,
"exclude_hosts": null,
"host": "127.0.0.1",
"msg": null,
"path": null,
"port": 8443,
"search_regex": null,
"sleep": 1,
"state": "started",
"timeout": 300
}
},
"msg": "Timeout when waiting for 127.0.0.1:8443"
}
to retry, use: --limit @/home/famous/k8s0/site.retry

PLAY RECAP *********************************************************************
node0 : ok=26 changed=21 unreachable=0 failed=1

kubelet can't start without "shared" volume on Travis

this is about more investigation on this issue

without the "shared" flag on this line, the calico can't start properly. the "shared" works fine on local box, but not on travis.

upgrade k8s version

the current version is too old,
especially,

Dear Sir,

I try to use:

#kubectl apply -f https://raw.githubusercontent.com/kubernetes/dashboard/master/src/deploy/recommended/kubernetes-dashboard.yaml

secret "kubernetes-dashboard-certs" created
serviceaccount "kubernetes-dashboard" created
service "kubernetes-dashboard" created
Error from server (BadRequest): error when creating "https://raw.githubusercontent.com/kubernetes/dashboard/master/src/deploy/recommended/kubernetes-dashboard.yaml": Role in version "v1" cannot be handled as a Role: no kind "Role" is registered for version "rbac.authorization.k8s.io/v1"
Error from server (BadRequest): error when creating "https://raw.githubusercontent.com/kubernetes/dashboard/master/src/deploy/recommended/kubernetes-dashboard.yaml": RoleBinding in version "v1" cannot be handled as a RoleBinding: no kind "RoleBinding" is registered for version "rbac.authorization.k8s.io/v1"
Error from server (BadRequest): error when creating "https://raw.githubusercontent.com/kubernetes/dashboard/master/src/deploy/recommended/kubernetes-dashboard.yaml": Deployment in version "v1beta2" cannot be handled as a Deployment: no kind "Deployment" is registered for version "apps/v1beta2"

Any Idea?


also when I use "vagrant halt" and "vagrant up" it reinstall kubernate and delete all my pods,
Is there possible to keep or save all my pods?

Best Regards