help understanding pod names
See original GitHub issueIn an attempt to control costs, am trying to figure out which users in my pangeo google cloud cluster have been creating dask kubernetes pods. All I have to work with are the kubernetes API calls logged by google cloud into bigquery.
The challenge is that it is hard to parse the names of the dask workers, which look something like this: dask-jovyan-3569756c-e2j5ht
. I have concluded that the first random looking string is associated with the cluster, and the second is associated with the individual worker. Is there any hope of tracing this back to individual users?
Issue Analytics
- State:
- Created 4 years ago
- Comments:8 (6 by maintainers)
Top Results From Across the Web
Object Names and IDs | Kubernetes
Each object in your cluster has a Name that is unique for that type of resource. Every Kubernetes object also has a UID...
Read more >Names - Unofficial Kubernetes - Read the Docs
Names are used to refer to an object in a resource URL, such as /api/v1/pods/some-name . By convention, the names of Kubernetes resources...
Read more >Kubernetes pod naming convention - Stack Overflow
I'm wondering if there is a proper naming convention for generated pod names in Kubernetes. By generated pod names I mean the name...
Read more >Names | Kubernetes
Names are used to refer to an object in a resource URL, such as /api/v1/pods/some-name . By convention, the names of Kubernetes resources...
Read more >Pods and Services - Core Concepts - OpenShift Documentation
Pods must have a unique name within their namespace. A pod definition may specify the basis of a name with the generateName attribute,...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I think that a broader solution would be to push on this upstream in JupyterHub.
Ideally when users arrive in their session in JupyterHub their username reflects their login.
Ideally if you login to ocean.pangeo.io, you could do something like this
Instead of the behavior today
If this change was made, then everything else would follow naturally
@yuvipanda
Going to close this as solutions seems to have been found.