OCI Target Configuration Project Should Be Optional
name: OCI Target Configuration Project Should Be Optional
Current configuration for the OCI Target Configuration has Project as a required field. This forces a deployment model into all of the images/helm charts, etc to be pushed into a common root repository for the registry. This is not a good fit for all scenarios. Proposal that allows the field to be options so that it can be utilized when/where it's appropriate.
Current Example (the i-dont-care-but-this-is-required
is REQUIRED)
Source Image | Destination Image |
---|---|
harbor.company.com/myProject/image:latest | airgapped.org/i-dont-care-but-this-is-required/myProject/image:latest |
harbor.company.com/docker.io/nginx:latest | airgapped.org/i-dont-care-but-this-is-required/docker.io/nginx:latest |
Proposed Example with Project Blank
Source Image | Destination Image |
---|---|
harbor.company.com/myProject/image:latest | airgapped.org/myProject/image:latest |
harbor.company.com/docker.io/nginx:latest | airgapped.org/docker.io/nginx:latest |
This allows for my applications in the air-gapped environment to only need to be concerned with my the image repository's URL and not require changing all of the projects as well.
Is your feature request related to a problem? Please describe
See above... The current solution forces me into a deployment pattern/paradigm that doesn't fit my desired state and should be easily accommodated by making this an optional property.
Describe the solution you'd like
See above... Make the project field of the OCI Target Configuration optional
Describe alternatives you've considered
I can make this work, but the air-gapped and connected environments are different configurations and not always meeting my particular needs.