Skip to main content
Solved

Kasten Cluster ID and Cluster UID Discrepancy


I noticed a discrepancy between the Kasten Cluster ID and the actual cluster UID retrieved from the namespace.

  • Kasten Cluster ID: f2c3c6f4-dc62-42d9-ac13-7933c4289xxx
  • Cluster UID (via kubectl): 557f2513-0d07-4fbb-ad26-4325ffe12xxx

Is this mismatch intentional?

This discrepancy poses a challenge for automated disaster recovery, as I haven’t found a reliable way to extract the Kasten Cluster ID programmatically.

 

//edit: Sorry, I did not see that there is a dedicated support group.

Best answer by nullsumme

Duh,…

I discovered that the discrepancy was due to using the UID from the kube-system namespace, whereas Kasten uses the UID from the default namespace.

Apologies for the confusion!

View original
Did this topic help you find an answer to your question?

3 comments

Chris.Childerhose
Forum|alt.badge.img+21
  • Veeam Legend, Veeam Vanguard
  • 8449 comments
  • January 13, 2025

@Madi.Cristil ​@safiya - would suggest moving this to the Kasten Support group for better assistance.


  • Author
  • Not a newbie anymore
  • 1 comment
  • Answer
  • January 13, 2025

Duh,…

I discovered that the discrepancy was due to using the UID from the kube-system namespace, whereas Kasten uses the UID from the default namespace.

Apologies for the confusion!


Chris.Childerhose
Forum|alt.badge.img+21
  • Veeam Legend, Veeam Vanguard
  • 8449 comments
  • January 13, 2025

Glad you were able to figure it out.