Skip to content
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

Harbor Helm Kubernetes address registry internally #2134

Open
hAislt opened this issue Feb 10, 2025 · 0 comments
Open

Harbor Helm Kubernetes address registry internally #2134

hAislt opened this issue Feb 10, 2025 · 0 comments

Comments

@hAislt
Copy link

hAislt commented Feb 10, 2025

Hello everyone,

I am having issues with my setup and would appreciate assistance.
I deployed harbor with helm on an AKS with Traefik as ingress and an Application Gateway.
There is a separate listener which listens to the domain reserved for harbor e.g. harbor-domain.com.

I can access my harbor instance and pull/push images by accessing the configured domain, this domain is within my cluster not resolvable and I work with a TLS cert defined in ingressroutes.

I tried to spawn pods within the cluster to use the registry but this does not work I get:
dial tcp: lookup harbor-domain.com on 168.63.129.16:53: no such host Warning Failed 13s kubelet Error: ErrImagePull

So this obviously is a DNS issue. I tried using private DNS and pointed it to the service IP of my harbor-registry.
But this does not work as I use externalurl configured to my non-resolvable domain?

How can internal adressing of the registry be achieved?

Helm setup:
expose.type = ingress
expose.tls.enabled = true
expose.tls.secretName = "harbor-tls"

version 1.16.0

Do I need to change the expose type?
Thanks in advance.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant