Is your feature request related to a problem? Please describe.
We should switch the runner sandbox namespace to be ignored by the Zarf agent to allow more flexibility in the choice of images that are run within the namespace. We should also look for ways to still minimized the amount of configuration a developer needs to manage (i.e. credentials) for common tasks / jobs.
Describe the solution you'd like
In doing this there are a few *ilities that we will need to consider:
While this will be a BREAKING new default there should be a configuration to disable it.
We should setup the namespace to be able to be configured to pull from private registries (such as the GitLab container registry since this will be the most likely location for runner images) - this will require something like the following:
To the above we will likely want to have commonly-managed images and project-managed ones - for common images they should be usable with minimal configuration from a developer whereas project images (i.e. those built by a team within the env) would simply rely on something like statically defined images.
Describe alternatives you've considered
We could require all images to be in Zarf but this requires that images are included in the production deployment process and doesn't allow any flexibility for developers to build / use their own images if they desired.
Additional context
This will be something we run into as we build out images for the pipeline components we will build.
Is your feature request related to a problem? Please describe.
We should switch the runner sandbox namespace to be ignored by the Zarf agent to allow more flexibility in the choice of images that are run within the namespace. We should also look for ways to still minimized the amount of configuration a developer needs to manage (i.e. credentials) for common tasks / jobs.
Describe the solution you'd like
In doing this there are a few *ilities that we will need to consider:
Describe alternatives you've considered
We could require all images to be in Zarf but this requires that images are included in the production deployment process and doesn't allow any flexibility for developers to build / use their own images if they desired.
Additional context
This will be something we run into as we build out images for the pipeline components we will build.