-
Notifications
You must be signed in to change notification settings - Fork 266
azure: re-enable cloud-provider #84
Comments
We have made the azure cloud provider optional for the time being: #83 |
Upstream PR/discussion: kubernetes/kubernetes#42576 |
upstream just recently added some documentation as go comments for the expected yaml structure, see https://github.com/kubernetes/kubernetes/blob/af1389e/pkg/cloudprovider/providers/azure/azure.go#L36-L83 I'll try to make this work. |
Just hit this as well at seattle hackfest. Trying to create a svc. NM Just realized I would need to create config as well. |
I have cloud-config generation working for the kubelet, but the bootkube module also needs this configuration (I think). The apiserver has the What is the recommendation for passing this file through? Should it be done as a host mount of the cloud configuration the kubelet is using or stored as a secret and mounted that way? |
I've got the cloud provider working in all the components now. I decided to add the cloud config to the secret config of apiserver and controller-manager and used the host cloud config during the bootstrap manifest phase. I have an unfortunately rather large PR coming soon for the Azure platform that addresses this issue, #464, #198, ability to use an existing dns zone, #93 (although I removed scale sets because of the limitation), and #39. The reason for the size is I was only recently given the ok from my employer to release the changes. |
I need this fixed too and can help out but first we need to answer @cehoffman's question on where to put this. @cehoffman How did you implement this? Can you extract the changes for the cloud provider config? If not, it would be great if you can share your changes as-is, I'm happy to help extracting the bits. |
@discordianfish @cehoffman Thanks a lot for helping out, this is much appreciated! My vote for this is to provide the cloud-config via a config map. This would make the configuration introspectable and potentially changeable during runtime (/cc @Quentin-M @aaronlevy @alexsomesan for thoughts on this). The canonical location would be in https://github.com/coreos/tectonic-installer/tree/4b8e586/modules/bootkube/resources/manifests and the wiring of the data would be declared in this block tectonic-installer/modules/bootkube/assets.tf Lines 52 to 109 in 4b8e586
|
@s-urbaniak Great, thanks for the pointers. I'll start playing with this now. |
@discordianfish the cloud-config changes are in #690 and isolated to the bootkube module and a new cloud-config module in azure if I remember right |
Ah great, I've just submitted a PR which addresses only the cloud-provider config for now. Still have to test it and probably fix some issues along the way though |
Currently the cloud provider is crashing the kubelet. We need to figure out:
The text was updated successfully, but these errors were encountered: