You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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:
What are the unique features or configurations that distinguish an OpenShift cluster from a vanilla Kubernetes cluster?
Are there any Non-deletable resources available in openshift cluster?
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.
The text was updated successfully, but these errors were encountered:
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.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
Exclude this issue from closing by commenting /lifecycle frozen.
If this issue is safe to close now please do so with /close.
/lifecycle rotten
/remove-lifecycle stale
openshift-cibot
added
lifecycle/rotten
Denotes an issue or PR that has aged beyond stale and will be auto-closed.
and removed
lifecycle/stale
Denotes an issue or PR has remained open with no activity and has become stale.
labels
May 24, 2024
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:
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.
The text was updated successfully, but these errors were encountered: