Currently, pod_name is being used for deployed containers. In k8s context pods are volatile and could be replicated as well. We should use the service name for a given deployment. This would reduce the configuration pod_name boilerplate at several locations.
Also, IMO there is no need to make the name configurable. Is there a reason I do not see?
Task Description
Currently,
pod_name
is being used for deployed containers. In k8s context pods are volatile and could be replicated as well. We should use the service name for a given deployment. This would reduce the configuration pod_name boilerplate at several locations.Also, IMO there is no need to make the name configurable. Is there a reason I do not see?