Unique Id for cluster

[yoavAqua]

Is there a way to find unique id for kubernetes cluster?
We are working with several environments and we couldn't find something to uniquely identify a cluster environment.

Our current workaround is to save all the node's on the cluster and use the node's machine id field to determine on which cluster you are.

[yoavAqua]

/sig api-machinery

[jennybuckley]

/assign @lavalamp

[lavalamp]

There is not, but you're not the only one wanting something like this. Current best practice is to use the kube-system UID.

[lavalamp]

I am pretty sure there was a long email discussion on this on the SIG Architecture mailing list.

[yoavAqua]

@lavalampThanks for the reply :)
I'm sorry but what exactly is the "kube-system UID"?
Also, do you have any thoughts about our workaround? is the machine_id field unique for a single node on all the kubernetes environments (clusters)? couldn't get it from the documentation.

[dims]

@yoavAqua i think it's this thread https://groups.google.com/d/msg/kubernetes-sig-architecture/mVGobfD4TpY/nkdbkX1iBwAJ

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

[fejta-bot]

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten

[fejta-bot]

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close

[k8s-ci-robot]

@fejta-bot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/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.