clusterctl: put resources in the kube-system namespace instead of default

[xmudrii]

When creating a new cluster with clusterctl, all resources are deployed in the default namespace, including controllers, but also cluster and machine objects.

This is a bad practice and we should change this ASAP. We should either use the kube-system namespace or create a new namespace for those resources.

[xmudrii]

I've researched little bit about this, and it doesn't seem possible currently.

As of kubernetes-sigs/cluster-api#481 it is possible to put Cluster/Machine resources in other (non-default) namespaces and it is possible to deploy machine and cluster controller is other namespace, but clusterctl will still deploy API server and etcd in the default namespace.

I'll check about this on the upstream Cluster API Implementers' Office Hours.

[xmudrii]

To be fixed by kubernetes-sigs/cluster-api#509.

Action item: Make sure cluster and machine objects have namespace set once cluster-api dependency is updated.

[xmudrii]

Upstream issue is now fixed. A PR will be created soon to update manifests, so all resources are created in appropriate namespace. For now, we're probably going to use the kube-system namespace.