-
Notifications
You must be signed in to change notification settings - Fork 60
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Kubernetes Cluster Name not getting logged #204
Comments
@dewanymca Could you please clarify what is the cluster name you are looking for to record? Could you please describe how are you getting it? For example, what kind of kubectl cmd or what UI. A screenshot of where you get it manually will be really helpful for us to understand what is the data point you are trying to record. Thanks. |
When we run command kubectl config get-contexts we recieve clustername as output in one of the column, we are looking to get smae in Applicaiton insight |
@dewanymca For now, apparently, there's no way to get the cluster name from within the cluster.
There's a draft for standardize the cluster name: Is it possible:
|
+1 Some time when you need to manage cloud resources from within the cluster, you need the cluster id to look for the |
@raelga Thanks for the info. Is this tag on the pods? If so, it is already recorded in the labels property. @dewanymca Last time, we synced offline, talking about adding labels on to the node for the cluster name, did it work for you? |
yes it did work for me
…On Fri, May 29, 2020 at 10:11 PM Saar Shen ***@***.***> wrote:
@raelga <https://github.com/raelga> Thanks for the info. Is this tag on
the pods? If so, it is already recorded in the labels property.
@dewanymca <https://github.com/dewanymca> Last time, we synced offline,
talking about adding labels on to the node for the cluster name, did it
work for you?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#204 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ADVAIFTG4SNR7I46SWM2ATLRT7QUDANCNFSM4MQIFIMA>
.
|
We are running active-active configuration for Kubernetes cluster for different environment. We are unable to see clustername getting logged as part of telemetry. This will help us in identitfying which cluster has processed the request and how load balancing is happening. Is there anything we are missing here? How to enable ClusterName.
The text was updated successfully, but these errors were encountered: