We plan to have a local container registry in the same cluster where our applications are running. We need this local container registry to support the network disconnections.
I have deployed Harbor in our cluster as local container registry and was able to successfully pull and push images from outside the cluster through nodePort and ingress service types.
However, this is not our use case. We need to pull the images within the cluster for which I am making use of clusterIP. As described in the Harbor Helm Chart description, I have defined the External_URL = http://harbor:80.
Note: Created the secret using following:
un: admin,
pw: Harbor12345
url: [http://harbor:80]
pod.yaml
on deploying the above pod.yaml
Note: In Rancher, I have setup the registries mirror and config to http://harbor:80
Can you please let us know why we are facing 503 DNS fail issue?
Could you please let us if we are missing anything? Is any configuration is missing?
NOTE: When exposed through NodePort or Ingress from cluster, I am successfully pulling the images from Harbor container registry.
imagefrom outside the Cluster.
Hi Harbor Team,
We plan to have a local container registry in the same cluster where our applications are running. We need this local container registry to support the network disconnections.
I have deployed Harbor in our cluster as local container registry and was able to successfully pull and push images from outside the cluster through nodePort and ingress service types. However, this is not our use case. We need to pull the images within the cluster for which I am making use of clusterIP. As described in the Harbor Helm Chart description, I have defined the External_URL = http://harbor:80. Note: Created the secret using following: un: admin, pw: Harbor12345 url: [http://harbor:80]
pod.yaml
on deploying the above pod.yaml
Note: In Rancher, I have setup the registries mirror and config to http://harbor:80 Can you please let us know why we are facing 503 DNS fail issue?
Could you please let us if we are missing anything? Is any configuration is missing?
NOTE: When exposed through NodePort or Ingress from cluster, I am successfully pulling the images from Harbor container registry. imagefrom outside the Cluster.
Our Configuration: Kubernetes version: v1.28.9+rke2r1