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
If you are reporting a problem, please make sure the following information are provided:
Expected behavior and actual behavior:
A clear and concise description of what you expected to happen and what's the actual behavior. If applicable, add screenshots to help explain your problem.
I used harbor-operator to create a harbor instance and used redis_sentinel. What’s amazing is that I entered redis and wanted to manually obtain the relevant index.yaml. I found that there was no relevant data. After checking the configuration of Chartmuseum, I found that harbor-operator has There was a problem with its cache configuration, which resulted in redis not being actually used. Instead, the system cache was used after being downgraded by Chartmuseum.
Steps to reproduce the problem:
Please provide the steps to reproduce this problem.
For multi-copy harbor, refresh the chart list and find that it keeps changing.
I suspected that it was a redis cache problem. I entered redis and switched to db3, and found that there were no logs.
The result of manually parsing the Chartmuseum's configmap is:
It seems that there is a problem with the key configured by redis. We should use ’cache.store: redis_sentinel‘ instead of 'cache: redis_sentinel' . I tried to modify the configmap, and after restarting, there was corresponding data in redis.
Versions:
Please specify the versions of following systems.
harbor operator version: [x.y.z]
harbor version: [x.y.z]
kubernetes version: [x.y.z]
Any additional relevant versions such as CertManager
Additional context:
Harbor dependent services:
Context info of postgreSQL
Context info of Redis
Context info of storage
Log files: Collect logs and attach them here if have.
Kubernetes: How Kubernetes access was provided (what cloud provider, service-account configuration, ...).
The text was updated successfully, but these errors were encountered:
If you are reporting a problem, please make sure the following information are provided:
Expected behavior and actual behavior:
A clear and concise description of what you expected to happen and what's the actual behavior. If applicable, add screenshots to help explain your problem.
I used harbor-operator to create a harbor instance and used redis_sentinel. What’s amazing is that I entered redis and wanted to manually obtain the relevant index.yaml. I found that there was no relevant data. After checking the configuration of Chartmuseum, I found that harbor-operator has There was a problem with its cache configuration, which resulted in redis not being actually used. Instead, the system cache was used after being downgraded by Chartmuseum.
Steps to reproduce the problem:
Please provide the steps to reproduce this problem.
For multi-copy harbor, refresh the chart list and find that it keeps changing.
I suspected that it was a redis cache problem. I entered redis and switched to db3, and found that there were no logs.
Versions:
Please specify the versions of following systems.
Additional context:
The text was updated successfully, but these errors were encountered: