Open itewk opened 3 years ago
Currently there is only two ports hard coded in the Deployment, (https://github.com/sonatype/operator-nxrm3/blob/21c56820c3dc6d938f53e7c2256e333893414d28/helm-charts/sonatype-nexus/templates/deployment-statefulset.yaml#L80) and http and a docker port. The problem is what if I have mutliple docker instances and need multiple docker ports. The most common scneario for this is if using OSS version, you need to push to a different repostiory then you pull form, assuming you set up a group to pull from. This is currently impossible to set up with the operator as it is now.
Deployment
make the ports in the Deployment an array that can be ajusted by the NexusRepo CR. One solution maybe to use the existing service parameter and automatically add any targetport in the service to the Deployment port list.
service
issue
Currently there is only two ports hard coded in the
Deployment, (https://github.com/sonatype/operator-nxrm3/blob/21c56820c3dc6d938f53e7c2256e333893414d28/helm-charts/sonatype-nexus/templates/deployment-statefulset.yaml#L80) and http and a docker port. The problem is what if I have mutliple docker instances and need multiple docker ports. The most common scneario for this is if using OSS version, you need to push to a different repostiory then you pull form, assuming you set up a group to pull from. This is currently impossible to set up with the operator as it is now.request
make the ports in the
Deploymentan array that can be ajusted by the NexusRepo CR. One solution maybe to use the existingserviceparameter and automatically add any targetport in the service to theDeploymentport list.