--use-service-account-credentials flag does not appear to correctly populate kubeconfig about cloud-provider-alibaba-cloud HOT 6 CLOSED

another option to solving this issue would be to refactor the CCM code to use more of the functionality from the upstream cloud-provider library.

for example, using the NewCloudControllerManagerCommand to initialize the client. you can see how this is done in the AWS CCM.

this would require some refactoring, but would make the alibaba CCM more resilient by using the common library methods for initialization.

from cloud-provider-alibaba-cloud.

The Alibaba CCM check the the service account credentials in https://github.com/kubernetes/cloud-provider-alibaba-cloud/blob/42eac35915d1b030a15727d9fc807f94dbfa3f3f/cmd/cloudprovider/app/ccm.go#L230. However, not all controllers use cloud-controller-manager service account, that resulted in ccm startup errors. We will fix it so that all controllers will use the same service account.

from cloud-provider-alibaba-cloud.

The CCM repo has merged the pr kubernetes#265. Please cherry pick the pr, thanks.

from cloud-provider-alibaba-cloud.

thanks!

cc @kwoodson @JoelSpeed

from cloud-provider-alibaba-cloud.

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

from cloud-provider-alibaba-cloud.

This has been resolved by pulling upstream code.

from cloud-provider-alibaba-cloud.