Skip to content
This repository has been archived by the owner on Feb 10, 2022. It is now read-only.

use of external cloud provider: deprecated cloud-provider flag in templates #328

Open
obeyler opened this issue Jun 4, 2019 · 1 comment

Comments

@obeyler
Copy link
Contributor

obeyler commented Jun 4, 2019

What happened:

Kubelet job warns that cloud providers are getting externalized through the following log:

I0527 13:20:55.174850 17526 server.go:417] Version: v1.14.1
W0527 13:20:55.175016 17526 plugins.go:118] WARNING: openstack built-in cloud provider is now deprecated. Please use 'external' cloud provider for openstack: https://github.com/kubernetes/cloud-provider-openstack

However when specifying the cloud-provider.type to external then the flag cloud-provider inside kube-api-server and kube-controller-manager is incorrectly set in current templates

<% if_link('cloud-provider') do |cloud_provider| %>
- --cloud-provider=<%= cloud_provider.p('cloud-provider.type') %>
- --cloud-config=/var/vcap/jobs/kube-apiserver/config/cloud-provider.ini
<% end %>

<%- if_link('cloud-provider') do |cloud_provider| -%>
- --cloud-provider=<%= cloud_provider.p('cloud-provider.type') %>
- --cloud-config=/var/vcap/jobs/kube-controller-manager/config/cloud-provider.ini
<%- end -%>

according to documentation at https://kubernetes.io/docs/tasks/administer-cluster/running-cloud-controller/#running-cloud-controller-manager reproduced below.

kube-apiserver and kube-controller-manager MUST NOT specify the --cloud-provider flag. This ensures that it does not run any cloud specific loops that would be run by cloud controller manager. In the future, this flag will be deprecated and removed.

I wonder whether this invalid flag may explain why my configured external openstack cloud provider fails to load

  • Kubernetes version (kubectl version): 1.14.1
  • Cloud provider (e.g. aws, gcp, vsphere): external => openstack
@obeyler obeyler changed the title use of external cloud provider use of external cloud provider: deprecated cloud-provider flag in templates Jun 6, 2019
obeyler pushed a commit to orange-cloudfoundry/kubo-release that referenced this issue Jun 11, 2019
@obeyler
Copy link
Contributor Author

obeyler commented Jun 17, 2019

Please note: that to make openstack cloud provider as external, master nodes must also not be hidden.
(daemonset is collocated on master node by spec it has node selection).
when external is set, every nodes are taint until daemonset pod avialability for cloud manager external.
To make it run, I add kubelet on maste, with arg: register-with-taints: node-role.kubernetes.io/master=true:NoSchedule

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants