Not able to create TLS_DISABLED k8s cluster
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Magnum |
New
|
Undecided
|
Unassigned |
Bug Description
Setup magnum with devstack:-
My env:-
[centos@devstack-1 magnum]$ magnum-api --version
5.0.1.dev15
[centos@devstack-1 magnum]$ magnum --version
2.7.0
Create TLS_DISABLED k8s cluster.
Login to k8s master node:-
kube api server failed to start:-
[fedora@
CONTAINER ID IMAGE COMMAND CREATED STATE BACKEND RUNTIME
kubelet docker.
kube-proxy docker.
kube-apiserv docker.
kube-control docker.
kube-schedul docker.
Following Error is seen in apiserver logs: Sep 04 06:09:54 k8s-cluster-
Sep 04 06:09:54 k8s-cluster-
/var/run/kubernetes is the default cirt-dir for apiserver certs.
It looks like atomic container(k8s apiserver 1.7.4) is trying to create certs even for TLS_DISABLED cluster.
If we mount /var/run/kubernetes does it work? I mean if it can write in /var/run/kubernetes