You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Feb 27, 2024. It is now read-only.
For the recently added subdomain feature of Sonatype's docker repos, it is likely necessary to add additional hosts entries to ingress that correspond to the subdomains.
For example -
Create a Kubernetes cluster with Sonatype in it.
Go to Sonatype config and create a docker proxy registry. Give it a subdomain name of docker-proxy.
Add DNS records using the method provided by your hosting provider. (For example, use external-dns and list docker-proxy.your.domain.com in the list of hostnames.)
Try to use this docker-proxy URL. You might get 404 no service mapping, because while your.domain.com maps to the sonatype-nexus-repository-manager service, the subdomain docker-proxy.your.domain.com does not map to it. In my case on GCP, this will result in the subdomain getting routed to the default no service mapping backend.
There is a nexus.docker.registries that would work in this case, except, it is tied up with other logic associated with connector ports. In particular, trying to add the same sonatype-nexus-repository-manager to multiple hostnames this way will error with this service name -- notice the insertion of docker:
no Service with the name "sonatype-nexus-repository-manager-docker-8081" found
It seems the Helm chart ingress template needs to be modified to support the scenario.
The text was updated successfully, but these errors were encountered:
I added the capability in https://github.com/jimsnab/nxrm3-helm-repository only to find unstable support in GCP for the load balancer with a host per subdomain. It only works if I create the LB without subdomain hosts, let it come online, and then add the subdomains as additional hosts. Two pass install is not how Helm works. And I think this is a loophole in GCP and they're trying to block the use case but forgot about the ingress update possibility. So I am giving up on the subdomains feature.
However, someone might use nginx or another cloud provider that doesn't have GCP's unstable behavior. And if so maybe adopt some form of the solution sitting in my fork ^.
jimsnab
changed the title
Need a way to specify additional hosts in Ingress
Subdomains: Need a way to specify additional hosts in Ingress
Feb 20, 2023
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
For the recently added subdomain feature of Sonatype's docker repos, it is likely necessary to add additional hosts entries to ingress that correspond to the subdomains.
For example -
docker-proxy
.external-dns
and listdocker-proxy.your.domain.com
in the list of hostnames.)docker-proxy
URL. You might get 404 no service mapping, because whileyour.domain.com
maps to thesonatype-nexus-repository-manager
service, the subdomaindocker-proxy.your.domain.com
does not map to it. In my case on GCP, this will result in the subdomain getting routed to the default no service mapping backend.There is a
nexus.docker.registries
that would work in this case, except, it is tied up with other logic associated with connector ports. In particular, trying to add the samesonatype-nexus-repository-manager
to multiple hostnames this way will error with this service name -- notice the insertion ofdocker
:It seems the Helm chart ingress template needs to be modified to support the scenario.
The text was updated successfully, but these errors were encountered: