I was following up the Wiki guidance, https://github.com/01org/cc-oci-runtime/wiki/Clear-Containers-and-Kubernetes, to setup Clear Container 2.1.4 with Kubernetes 1.6.3, and stuck to the step of bringing up Kubernetes master. When executing `#sudo ~/k8s-bring-up.sh`, it stops at "waiting for the control panel to become ready".
What might be the cause of the issue?
Full log is as below,
horaceli@horaceli-workstation:~$ sudo ~/k8s-bring-up.sh
[kubeadm] WARNING: kubeadm is in beta, please do not use it for production clusters.
[init] Using Kubernetes version: v1.6.3
[init] Using Authorization mode: RBAC
[preflight] Running pre-flight checks
[preflight] Starting the kubelet service
[certificates] Generated CA certificate and key.
[certificates] Generated API server certificate and key.
[certificates] API Server serving cert is signed for DNS names [horaceli-workstation kubernetes kubernetes.default kubernetes.default.svc kubernetes.default.svc.cluster.local] and IPs [10.96.0.1 10.239.159.165]
[certificates] Generated API server kubelet client certificate and key.
[certificates] Generated service account token signing key and public key.
[certificates] Generated front-proxy CA certificate and key.
[certificates] Generated front-proxy client certificate and key.
[certificates] Valid certificates and keys now exist in "/etc/kubernetes/pki"
[kubeconfig] Wrote KubeConfig file to disk: "/etc/kubernetes/admin.conf"
[kubeconfig] Wrote KubeConfig file to disk: "/etc/kubernetes/kubelet.conf"
[kubeconfig] Wrote KubeConfig file to disk: "/etc/kubernetes/controller-manager.conf"
[kubeconfig] Wrote KubeConfig file to disk: "/etc/kubernetes/scheduler.conf"
[apiclient] Created API client, waiting for the control plane to become ready
Does anyone have any guide for cc 2.1 + OVS, not ovs-dpdk? If yes, it will be appreciated, thanks. When i am trying to play with cc 2.1 + OVS, i find that the network is not available for 2 cc dockers.
Zhi Yong Wu
I sent a few PRs for making the new OWNERS based maintenance model a
little more formal. As described in the CONTRIBUTING file, the
maintainership for each of our 3.0 repos is split between reviewers and
approvers. The latter group is a subset of the former and have the final last
word for merging a PR. A PR must be LGTM'ed by one member of each group
before being merged.
On the technical leadership front, Damien Lespiau (@dlespiau) will be the
project technical lead, at least until we reach our first 3.0.0 release .
Please let us know if you have any questions/concerns.
Intel Corporation SAS (French simplified joint stock company)
Registered headquarters: "Les Montalets"- 2, rue de Paris,
92196 Meudon Cedex, France
Registration Number: 302 456 199 R.C.S. NANTERRE
Capital: 4,572,000 Euros
This e-mail and any attachments may contain confidential material for
the sole use of the intended recipient(s). Any review or distribution
by others is strictly prohibited. If you are not the intended
recipient, please contact the sender and delete all copies.