K0s ClusterID added to annotations

[makhov]

Fixes #683

[apedriza]

How about adding it as a controlplane annotation and not as part of the controlplane status? In general I think that a clusterID is not part of the controlplane state as such, WDYT?

Following annotations definition:

You can use Kubernetes annotations to attach arbitrary non-identifying metadata to objects. Clients such as tools and libraries can retrieve this metadata.

[makhov]

Yeah, good point.

@eromanova is it ok, if we add clusterID as annotation to K0smotronControlPlane and K0sControlPlane objects?

@apedriza or should we add the annotation to the Cluster object itself?

[eromanova]

@makhov Yes, it’s fine if the clusterID is stored in the annotation. What matters is that we can retrieve it from the public API objects, regardless of where the field is located.

[apedriza]

@apedriza or should we add the annotation to the Cluster object itself?

Yes, good idea 👍