Deployment fails when repository is public but the registry is private
Due to this check, image pull secrets are omitted for any public project, even if the container registry is restricted to project members, causing the deployment to fail.
This could be fixed by either:
- adding more CI/CD variables for the permission level of every component, and patching the check accordingly
- including the pull secret no matter the project's visibility, to also fix deployments failing when a repository transitions from public to private
I'm in favor of the latter option and willing to submit an MR.