Support cloud-config for external CCM

[xmudrii]

Follow-up of #161

When using external CCM, the cluster will not be configured to use cloud-config even if it is provided. Instead we should check if it is provided, and if yes, configure external CCM to use the provided cloud-config.

Acceptance criteria:

• It is possible to use cloud-config with external CCM

[kron4eg]

dependent and blocked by #227 as they share common idea/logic

[xmudrii]

/assign
/lifecycle active

[xmudrii]

Blocked as we're unsure how cloud-config will be handled for out-of-tree CCMs

[xmudrii]

/assign

Check with SIG Cloud Provider about this

[xmudrii]

/unassign

This issue is still relevant.

[kron4eg]

Blocked as we're unsure how cloud-config will be handled for out-of-tree CCMs

As usually, we only need to specify --cloud-config. More info here:
https://github.com/kubernetes/cloud-provider-openstack/blob/master/docs/openstack-kubernetes-integration-options.md#external-openstack-provider

[kron4eg]

blocked by #255

/lifecycle blocked

[xmudrii]

This issue is not blocked by #255 and can be fixed in this milestone. Nothing prevents us from deploying cloud-config if it is provided in the KubeOne manifest.

[kron4eg]

@xmudrii If you mean upload cloud-config to /etc/kubermatic/cloud-config then it's already done unconditionally.

[xmudrii]

Yes, I was talking about that. Was not aware, I thought we don't. Let's see is there anything else we can do and if not we'll close the issue. In that case it's already scope of #255.

[kron4eg]

Since we don't deploy any CCM currently, we have no place to stick that cloud-config 🤷‍♂️, that's why I've closed it initially.

[xmudrii]

/close

[kubermatic-bot]

@xmudrii: Closing this issue.

In response to this:

/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.