Integration with openstack about kubo-deployment HOT 6 CLOSED

We have created an issue in Pivotal Tracker to manage this:

https://www.pivotaltracker.com/story/show/162150020

The labels on this github issue will be updated when the story is started.

from kubo-deployment.

Without ops file manifests/ops-files/iaas/openstack/cloud-provider.yml the command "kubectl edit node nodename****" does not show any taints fields.

from kubo-deployment.

I see in the worker.

 kubelet/kubelet_ctl.stderr.log:W1122 09:48:12.286929    7966 container_manager_linux.go:792] CPUAccounting not enabled for pid: 7966
kubelet/kubelet_ctl.stderr.log-W1122 09:48:12.286959    7966 container_manager_linux.go:795] MemoryAccounting not enabled for pid: 7966

Maybe it explains why the worker never gets ready to accept pods. I remove the taint from the node and the worker is accepting pods again.
I dont know if this is a bug by openstack installation

from kubo-deployment.

From: https://kubernetes.io/docs/tasks/administer-cluster/running-cloud-controller/#running-cloud-controller-manager
and
https://kubernetes.io/docs/tasks/administer-cluster/developing-cloud-controller-manager/

kubelets specifying --cloud-provider=external will add a taint node.cloudprovider.kubernetes.io/uninitialized with an effect NoSchedule during initialization. This marks the node as needing a second initialization from an external controller before it can be scheduled work. Note that in the event that cloud controller manager is not available, new nodes in the cluster will be left unschedulable. The taint is important since the scheduler may require cloud specific information about nodes such as their region or type (high cpu, gpu, high memory, spot instance, etc).

from kubo-deployment.

We have created an issue in Pivotal Tracker to manage this:

https://www.pivotaltracker.com/story/show/162153418

The labels on this github issue will be updated when the story is started.

from kubo-deployment.

I think I can not really understand the problem. As this is for a test environment we just provisioned a disk with bosh directly and we use local storage class. For our use case is enough.

from kubo-deployment.