[kubernetes] K8s 1.8 changed ReplicaSet naming
See original GitHub issueK8s 1.8 changed the naming scheme for some objects, including ReplicaSets, in this commit, notably the pod template hash is now encoded as a hexadecimal, rather than decimal. This breaks the assumption in kubeutil about the name being all (base 10) digits. This is called for example by get_pod_creator_tags
, which in turn is used by the docker integration. Due to this, docker metrics can’t resolve ReplicaSets to their creating Deployment.
Issue Analytics
- State:
- Created 6 years ago
- Comments:7 (4 by maintainers)
Top Results From Across the Web
ReplicaSet - Kubernetes
You can remove Pods from a ReplicaSet by changing their labels. This technique may be used to remove Pods from service for debugging,...
Read more >Writing a Controller for Pod Labels - Kubernetes
Implementing reconciliation · Use the Pod's name and namespace from the ctrl. · If the Pod has an add-pod-name-label annotation, add a pod-name...
Read more >DaemonSet - Kubernetes
If node labels are changed, the DaemonSet will promptly add Pods to newly matching nodes and delete Pods from newly not-matching nodes. You...
Read more >Using Finalizers to Control Deletion - Kubernetes
Finalizer rules are processed when there are owner references. An owner reference consists of a name and a UID. Owner references link resources ......
Read more >Deployments - Kubernetes
This name will become the basis for the ReplicaSets and Pods which are ... kubectl apply -f https://k8s.io/examples/controllers/nginx-deployment.yaml.
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 tried the backported image and it seems to have fixed the issue! 🎉
https://github.com/DataDog/dd-agent/pull/3586 merged in 5.20 is fixing the issue, closing this one.
@ChipmunkV we infer the deployment name from the replicaset name, not the pod name, see https://github.com/DataDog/dd-agent/blob/80ceba8a0789e20d0b5b1bc740bd26e34ebda019/utils/kubernetes/kubeutil.py#L374