miner

Hi @chrifey, When you are trying to upgrade Harbor and using an existed `harbor.[version].tar.gz`, files like `install.sh` and `harbor.yml.tmpl` may varied from versions which means you may not using these...

Hi @chrifey , Do you still have a concern on this issue? I am wondering why we need make this image tarball file path configurable? If you need docker load...

Hi @chrifey , Giving the situation above, you'd better to regard the whole offline installer bundle as a unit. It contains all the script, configuration yaml file as well as...

Hi @100mik , Thanks for your contribution! Sorry for the late response and we would like to merge this PR into main branch. Do you have any chance recently to...

@100mik Hi could you pls add a [DCO](https://probot.github.io/apps/dco/) for this pr, then we will merge it. Appreciate!

HI @100mik , NP and thanks for your keep working on this PR. But I didn't see any sign-off on this commit and the DCO CI still not passed. Would...

Hi @orblazer, As it mentioned above, the repository part looks correct but not the scanner part. Would you like to revise this PR? Thanks!

Hi @lengrongfu , Thanks @lengrongfu. But there would be limitations for harbor to use `redis cluster` as you describe above since we need to guarantee all of the components like...

Hi @lengrongfu , First of all, even we discard the 3-rd party for this Redis cluster mode, here's still some limitations on harbor upstream dependency. For example, we depends on...

Since it would open for discussion here https://github.com/goharbor/harbor/discussions/17400, I will close this issue and the related PR https://github.com/goharbor/harbor/pull/17344 for now.