Currently when using plugin-kubernetesPodCreate task, then it is impossible to assign a custom name to the Pod created in Kubernetes. It is possible to assign a name to the containers within that Pod, but not to the Pod itself.
Documentation under metadata definition includes the possibility of assigning a name (as per k8s spec), but this will be overriden by AbstractConnection.java L95.
Could it be considered, that when a Pod name is passed from the metadata.name configuration, then it is used instead of a generated name?
Use case: we have a standard way of naming Pods in Kubernetes and since the executions are not dropped, we prefer a better naming scheme.
Feature description
Currently when using
plugin-kubernetes
PodCreate
task, then it is impossible to assign a custom name to the Pod created in Kubernetes. It is possible to assign a name to the containers within that Pod, but not to the Pod itself.Documentation under metadata definition includes the possibility of assigning a name (as per k8s spec), but this will be overriden by AbstractConnection.java L95.
Could it be considered, that when a Pod name is passed from the metadata.name configuration, then it is used instead of a generated name?
Use case: we have a standard way of naming Pods in Kubernetes and since the executions are not dropped, we prefer a better naming scheme.