When installing cloud-provider-azure using helm chart provided with cloudControllerManager.cloudConfigSecretName set it behaves incorrectly (still tries to use /etc/kubernetes/azure.json).
What you expected to happen:
According to the docs in section Dynamically reloading cloud controller manager when using the --cloud-config-secret-name user should:
Set --enable-dynamic-reloading to true
Remove the --cloud-config-key option
This is not the case with the current chart, since it sets both options and don't pass the --enable-dynamic-reloading option, thus the cloudControllerManager.cloudConfigSecretName value doesn't work.
How to reproduce it (as minimally and precisely as possible):
Install cloud-provider-azure using helm with --set cloudControllerManager.cloudConfigSecretName="azure-cloud-provider".
What happened:
When installing
cloud-provider-azureusing helm chart provided withcloudControllerManager.cloudConfigSecretNameset it behaves incorrectly (still tries to use/etc/kubernetes/azure.json).What you expected to happen:
According to the docs in section Dynamically reloading cloud controller manager when using the
--cloud-config-secret-nameuser should:--enable-dynamic-reloadingtotrue--cloud-config-keyoptionThis is not the case with the current chart, since it sets both options and don't pass the
--enable-dynamic-reloadingoption, thus thecloudControllerManager.cloudConfigSecretNamevalue doesn't work.How to reproduce it (as minimally and precisely as possible):
Install
cloud-provider-azureusing helm with--set cloudControllerManager.cloudConfigSecretName="azure-cloud-provider".