Container Naming Conventions

Just installed cAdvisor, a tool for monitoring container resource usage, which comes with built-in Prometheus metrics support!

It’s working great, except that I can’t make heads-or-tails of the naming convention for the ephemeral containers that run individual pipeline steps.


Two questions:

  1. Does the long string of digits before the _step_XX part have any meaning?
  2. Would you be open to a PR to make these containers have some identifiable information such as the repo name, and job number?


1 Like

We have a new runtime engine that we will introduce in 0.9, which I believe uses a different convention. Lets revisit this when we have 0.9-rc available and then we can see what improvements might be possible.

Sounds like a plan. Looking forward to 0.9!