We have an issue with the labels assigned to jenkins slave pods within the jenkins kubernetes plugin. A label in a Kubernetes pod are key/value pairs. Valid label keys have two segments: an optional prefix and name, separated by a slash . The issue we are seeing is that the keys are unique for each pod that is spinned up. Following the guidelines here: https://github.com/jenkinsci/kubernetes-plugin means that we end up with a pod label like: `jenkins/worker-a3346222-237b-4882-a8f9-2d1f125e2a44=true`. so instead of putting the unique id for the worker as the value, it is part of the key. This becomes a problem because we get one index per build in elasticsearch. Has anybody thought about this or know a workaround? It seems unnecessary that we have to write a logstash filter to ignore fields starting with `jenkins/`