Request for Guidance: Definite Criteria for Identifying OpenShift Kubernetes Cluster

[KiranBodipi]

Hello OpenShift Community,

I hope this message finds you well. I am currently working on a project that involves programmatically identifying Kubernetes clusters, specifically those running OpenShift. I would appreciate your insights and guidance regarding the criteria or characteristics that can be used to definitively identify an OpenShift Kubernetes cluster.

Here are some specific details I'm interested in:

1. What are the unique features or configurations that distinguish an OpenShift cluster from a vanilla Kubernetes cluster?
2. Are there any Non-deletable resources available in openshift cluster?
3. Are there any environment variables or configuration files that reliably identify an OpenShift cluster?
   I've found many projects are depending on namespaces and annotations or labels in resources which can be mutable or deleted, which is not always reliable.
   I believe presence of routes in cluster can be helpful here but am not sure, whether this can also lead to above issue.
   I've reviewed the official documentation, couldn't find anything around how openshift identify's it's kubernetes cluster? I'm seeking practical insights and experiences from the community. Your expertise will be invaluable in ensuring accurate identification of OpenShift clusters in my application.

Thank you in advance for your time and assistance. Any pointers, code snippets, or documentation references would be greatly appreciated.

[openshift-bot]

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

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

/lifecycle stale