-
Notifications
You must be signed in to change notification settings - Fork 814
Support multiple hosts for core #2214
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
Signed-off-by: Jamess11 <[email protected]>
Signed-off-by: Jamess11 <[email protected]>
9e3e8ae
to
0d69d48
Compare
this won't work as harbor only supports one domain defined in external_url, everything else is redirected to to external_url |
It works in our company, we cloned the ingress that was created by the helm chart to expose docker.io, ghcr.io and gcr.io, while the external url is set to harbor.io. |
Signed-off-by: Jamess11 <[email protected]>
I wasn't precise in my statement: it won't work across different networks. Where for example the external_url is in the public internet and the second domain is on the intranet. the clients on the intranet don't have access to the internet. I guess this isn't the case for you. |
I don't understand why Harbor can host images in I'm afraid this change is too specific to your environment and not generic enough to justify merging it. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the contribution.
I believe this might create the impression of full multi-host support in Harbor, which could be misleading.
{{- if $ingress.hosts.core }} | ||
hosts: | ||
- {{ $ingress.hosts.core }} | ||
{{- range $host := $ingress.hosts.core }} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Harbor doesn't truly support multi-host setups, as noted in goharbor/harbor#8243. Allowing multiple hostnames in the Helm chart adds confusion. it only enables redirection to the externalURL
.
In practice, all traffic is handled by the primary host, making the other hostnames effectively cosmetic.
For true multi-host support, each hostname should be capable of directly handling requests, not redirecting to a single primary. Hope this make sense.
This PR is being marked stale due to a period of inactivty. If this PR is still relevant, please comment or remove the stale label. Otherwise, this PR will close in 30 days. |
Added support for multiple core hosts at the ingress level.
In an air-gapped environment, we needed to add another ingress manually in order to make global docker registries such as docker.io and ghcr.io urls accessible via the habror we deloyed. With this change, it would be much more easy to manage.