Use clouds.yaml

[jschoone]

Hi,
thanks for the webhook, it really helps us.
The only thing I missed (or didn't find out how to use) is the ability of providing a clouds.yaml, which I added in this PR.
I was not 100% sure about the naming in the Helm chart, so I chose the useClouds because it is also used in OpenStack Cloud Controller Manager and the identityRef from ClusterAPI Provider OpenStack.

A problem is that this still uses the old gophercloud. It might make sense to update the components to v2, but this probably requires a bit more work which can better be done in a different PR.

[maboehm]

A problem is that this still uses the old gophercloud. It might make sense to update the components to v2, but this probably requires a bit more work which can better be done in a different PR.

Can you please elaborate why that is a problem? Yes, we should probably update to v2, but AFAIK clouds.yaml should work in principal in v1: gophercloud/gophercloud#2899

Would you be willing to contribute this? It take some time until I can give this repo some more love and finish updating all dependencies since we forked.

[jschoone]

A problem is that this still uses the old gophercloud. It might make sense to update the components to v2, but this probably requires a bit more work which can better be done in a different PR.

Can you please elaborate why that is a problem? Yes, we should probably update to v2, but AFAIK clouds.yaml should work in principal in v1: gophercloud/gophercloud#2899

Oh, didn't know it works also like that. I successfully tested the code I committed, but I didn't know whether it's a good idea to continue using the old version. As the utils was the "problem" by importing those old versions, this can probably avoided then. I'll try later, thanks!

Would you be willing to contribute this? It take some time until I can give this repo some more love and finish updating all dependencies since we forked.

I will try :)