cloud-conf configmap expects accesskey and accesssecret to be base64 about cloud-provider-alibaba-cloud HOT 2 CLOSED

Alibaba is creating credentials and placing them in the cloud-conf configmap

Do the credentials absolutely have to be in a configmap? This seems like a security risk to me that we should be trying to avoid.

At the moment, Azure has this limitation as well (at least on stack hub) so we take the credentials from a secret, and inject them into the config as the container starts. I think this is probably a preferable approach over what we have today, but ideally I think we should teach the alibaba CCM to read the credentials from environment variables (we are poking for this for azure too) to allow us to keep the credentials in a secret and the rest of the config in a configmap.

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.