Add support for custom container names to the Kubernetes executor
Proposal
Currently, the service
containers have the names svc-0
, svc-1
, ..., regardless of their purpose.
If services had container names that matched their alias
, or if a new keyword was introduced to control the container name, we could use this name inside patch statements. Right now, that feature doesn't work well with services due to a container's patchMergeKey being "name".
The workaround -- spinning up a dedicated runner per job type so that svc-<N>
always has the same purpose -- is not particularly scalable.
Implementation proposal
- {placeholder}
Edited by Darren Eastman