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

[bitnami/harbor] Wrong host string with sentinel enabled #11350

Closed
lwj5 opened this issue Jul 26, 2022 · 8 comments
Closed

[bitnami/harbor] Wrong host string with sentinel enabled #11350

lwj5 opened this issue Jul 26, 2022 · 8 comments
Assignees
Labels
harbor solved stale 15 days without activity tech-issues The user has a technical issue about an application

Comments

@lwj5
Copy link
Contributor

lwj5 commented Jul 26, 2022

Name and Version

bitnami/harbor 15.0.0

What steps will reproduce the bug?

  1. enabled external Redis sentinel
  2. See Redis host reported in the following configmap as redis.redis:26379/mymaster:6379

Files affected:

  • chartmuseum-cm-envvars.yaml
  • registry-cm.yaml

Are you using any custom parameters or values?

externalRedis:
  host: redis.redis
  password: <trunc>
  sentinel:
    enabled: true
    hosts: redis.redis:26379
    masterSet: mymaster

What is the expected behavior?

If service supports sentinel, use Redis host in configmap as redis.redis:26379/mymaster

Since these services do not
chartmuseum helm/chartmuseum#179
resigtry distribution/distribution#2885

We should use Redis host in configmap as redis.redis:6379 or turn off redis for these services altogether

What do you see instead?

Cannot connect to Redis

Additional information

@lwj5 lwj5 added the tech-issues The user has a technical issue about an application label Jul 26, 2022
@agomezmoron agomezmoron added this to Triage in Support Jul 26, 2022
@agomezmoron agomezmoron added the triage Triage is needed label Jul 26, 2022
@RichardSufliarsky
Copy link
Contributor

Try to use

externalRedis:
  host: ""

in your values.yaml.
Check also #11266 and #11354.

@lwj5
Copy link
Contributor Author

lwj5 commented Jul 26, 2022

@RichardSufliarsky do you mean port: ""? it wouldn't work

if you look at the configmaps {{ printf "%s:%s" ( include "harbor.redis.host" . ) ( include "harbor.redis.port" . ) | quote }}
The 2nd colon will always be there anyways.

Unfortunately, I do not have time to fix this chart, so I just edited the values of the affected config maps

@RichardSufliarsky
Copy link
Contributor

@RichardSufliarsky do you mean port: ""? it wouldn't work

if you look at the configmaps {{ printf "%s:%s" ( include "harbor.redis.host" . ) ( include "harbor.redis.port" . ) | quote }} The 2nd colon will always be there anyways.

Unfortunately, I do not have time to fix this chart, so I just edited the values of the affected config maps

No, I mean host: "" in externalRedis, but you are right, it won't help. I looked at goharbor's helm chart and there seems to be different config for Sentinel: https://github.com/goharbor/harbor-helm/blob/9c62943736458b63cb8d8f1bd347e8cdfb34a1f9/templates/registry/registry-cm.yaml#L173
And they handle addr correctly: https://github.com/goharbor/harbor-helm/blob/9c62943736458b63cb8d8f1bd347e8cdfb34a1f9/templates/_helpers.tpl#L155

@rafariossaa rafariossaa moved this from Triage to Pending in Support Jul 27, 2022
@bitnami-bot
Copy link
Contributor

This Issue has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thanks for the feedback.

@bitnami-bot bitnami-bot added the stale 15 days without activity label Aug 26, 2022
@lwj5
Copy link
Contributor Author

lwj5 commented Aug 26, 2022

not stale

@github-actions github-actions bot moved this from Pending to Triage in Support Aug 26, 2022
@github-actions github-actions bot removed the stale 15 days without activity label Aug 26, 2022
@bitnami-bot
Copy link
Contributor

This Issue has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thanks for the feedback.

@bitnami-bot bitnami-bot added the stale 15 days without activity label Sep 11, 2022
@rafariossaa rafariossaa removed the stale 15 days without activity label Sep 13, 2022
@rafariossaa rafariossaa moved this from Triage to In progress in Support Sep 13, 2022
@github-actions github-actions bot added in-progress and removed triage Triage is needed labels Sep 13, 2022
@bitnami-bot bitnami-bot assigned alemorcuq and unassigned rafariossaa Sep 13, 2022
@bitnami-bot
Copy link
Contributor

This Issue has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thanks for the feedback.

@bitnami-bot bitnami-bot added the stale 15 days without activity label Oct 8, 2022
@github-actions github-actions bot moved this from In progress to Pending in Support Oct 8, 2022
@github-actions
Copy link

Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Issue. Do not hesitate to reopen it later if necessary.

@bitnami-bot bitnami-bot moved this from Pending to Solved in Support Oct 13, 2022
@fmulero fmulero removed this from Solved in Support Jan 18, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
harbor solved stale 15 days without activity tech-issues The user has a technical issue about an application
Projects
None yet
Development

No branches or pull requests

6 participants