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
Hi Folks,
I've been working on deploying Harbor using the goharbor/harbor-helm Helm chart. My goal is to streamline the Harbor deployment by cutting down some of the services, specifically leaving only Core, Registry, Postgres, and Portal services.
However, I've encountered an issue with the Core service. I've disabled Redis connection for the Core service in the configmap.yaml file as follows:
cache:
redis:
enabled: false
Despite this, the Core service pod trying to make connection to redis to start, and I'm seeing the following error:
[FATAL] [/core/main.go:153]: failed to initialize cache: retry timeout: dial tcp: lookup release-name-harbor ││ -redis on 10.43.0.10:53: no such host.
I'm seeking guidance from the community on resolving this issue. Here are some details about my setup:
Kubernetes Platform: RKE2 v1.28.6
OS: Ubuntu 22.04.3 LTS (Jammy Jellyfish)
Additionally, I'm interested in understanding if it's feasible to run Core and Registry services independently. Are there any concerns or requirements I should be aware of when attempting this? My Ultimate goal to make a lightweight helm package by keep only minimal services
Any help, suggestions, or experiences shared would be greatly appreciated! Thanks in advance
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Hi Folks,
I've been working on deploying Harbor using the goharbor/harbor-helm Helm chart. My goal is to streamline the Harbor deployment by cutting down some of the services, specifically leaving only Core, Registry, Postgres, and Portal services.
However, I've encountered an issue with the Core service. I've disabled Redis connection for the Core service in the configmap.yaml file as follows:
cache:
redis:
enabled: false
Despite this, the Core service pod trying to make connection to redis to start, and I'm seeing the following error:
[FATAL] [/core/main.go:153]: failed to initialize cache: retry timeout: dial tcp: lookup release-name-harbor ││ -redis on 10.43.0.10:53: no such host.
I'm seeking guidance from the community on resolving this issue. Here are some details about my setup:
Kubernetes Platform: RKE2 v1.28.6
OS: Ubuntu 22.04.3 LTS (Jammy Jellyfish)
Additionally, I'm interested in understanding if it's feasible to run Core and Registry services independently. Are there any concerns or requirements I should be aware of when attempting this? My Ultimate goal to make a lightweight helm package by keep only minimal services
Any help, suggestions, or experiences shared would be greatly appreciated! Thanks in advance
Attached values and template file
harbor.zip
Beta Was this translation helpful? Give feedback.
All reactions