In scenarios where agent clusters are isolated from each other, with each cluster responsible for building its own image and pushing it to its respective image registry, there is a potential race condition that can lead to errors during separate run/push steps. Specifically, one of the steps may attempt to pull an image from the wrong image registry due to shared metadata across all clusters.
To mitigate it and ensure that each cluster is building and running images from the correct image registry, I propose introducing a new metadata_key_prefix parameter. This parameter would allow users to specify a unique prefix for the metadata keys used by the plugin, effectively isolating the metadata for each agent cluster.
In scenarios where agent clusters are isolated from each other, with each cluster responsible for building its own image and pushing it to its respective image registry, there is a potential race condition that can lead to errors during separate
run
/push
steps. Specifically, one of the steps may attempt to pull an image from the wrong image registry due to shared metadata across all clusters.To mitigate it and ensure that each cluster is building and running images from the correct image registry, I propose introducing a new
metadata_key_prefix
parameter. This parameter would allow users to specify a unique prefix for the metadata keys used by the plugin, effectively isolating the metadata for each agent cluster.example
docker-compose.yml
pipeline.yml