« Back to projectatomic.io
Ask Your Question

I there a kubernetes dependency with cloud-init?!

asked 2015-03-02 11:06:35 +0000

pwFoo gravatar image

I used a init.iso to set a initial password. After basic configuration is done I moved the fedora atomic vm to a live server and removed the init.iso.

1) With cloud init active boot up needs some minutes

2) Cloud init disabled kube-controller-manager won't work

Mar 02 10:59:32 atomic01 kube-controller-manager[3925]: I0302 10:59:32.103392    3925 plugins.go:70] No cloud provider specified.
Mar 02 10:59:32 atomic01 kube-controller-manager[3925]: I0302 10:59:32.133511    3925 restclient.go:146] Waiting for completion of operation 6
Mar 02 10:59:34 atomic01 kube-controller-manager[3925]: I0302 10:59:34.135311    3925 restclient.go:146] Waiting for completion of operation 6
edit retag flag offensive close merge delete

1 answer

Sort by ยป oldest newest most voted

answered 2015-03-02 13:56:29 +0000

Kubernetes doesn't have a cloud-init dependency, that error is an internal Kubernetes concept of cloud provider from the plugin architecture.

Fedora Atomic does have a boot "dependency" on cloud-init, meaning that having no datasource for configuration might cause longer boot times as the services run on boot.

Is the apiserver running correctly from your other question? When you moved the VM, are you setting the same IP address via DHCP in the new environment as the config files expect? How did you go about moving the VM?

edit flag offensive delete link more


So I have to mount the cloud init iso also after Fedora Atomic is configured and go live? I only need cloud init to set a password or pubkey, because there is no other way to log in... After initial config (password / pubkey, WAN network config with a static ip and default route) the atomic host was moved to production environment.

pwFoo ( 2015-03-12 10:13:50 +0000 )edit

Once the host is configured there's no need for a cloud-init source, but you may see longer boot times as cloud-init still runs. The "waiting" error from kubernetes is unfortunately generic and points to something blocking before whatever kube-controller is trying to do. It could be connectivity?

nzwulfin ( 2015-03-16 13:36:11 +0000 )edit

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account.

Add Answer

[hide preview]

Question Tools

1 follower


Asked: 2015-03-02 11:06:35 +0000

Seen: 1,387 times

Last updated: Mar 02 '15