<p>As mentioned <a href="https://kubernetes.io/docs/concepts/overview/working-with-objects/names/#uids" rel="nofollow noreferrer">here</a>,</p>
<p><em>A Kubernetes systems-generated string to uniquely identify objects.
Every object created over the whole lifetime of a Kubernetes cluster has a distinct UID. It is intended to distinguish between historical occurrences of similar entities.</em></p>
<hr />
<p>We have multiple k8s clusters in GCP</p>
<p>Each k8s cluster has multiple namespace.</p>
<p>Each namespace has multiple pods</p>
<hr />
<p>Using kubernetes API, We monitor Pod health(<code>Podname, ready, status, restarts, age, Podnamespace</code>) from each namespace of each K8s clusters and store data in MongoDB document.</p>
<p>Goal is to make unique entry of each Pod in a MongoDB document</p>
<hr />
<p>Is Pod UID a unique id across multiple K8s cluster? if no, what is the best primary key to store Pod entry in a MongoDB document?</p>

overexchange
<p>Every object created over the whole lifetime of a Kubernetes cluster has a distinct UID. It is intended to distinguish between historical occurrences of similar entities. But there is no guarantee it would stay unique across clusters.</p>
<p>Can you consider the cluster name and  pod UID combination as the primary key in the database table to identify specific pod in a cluster.</p>
