> Lauri says that harbor-operator should manage it not helm
Harbor Operator seems dead - no commits in past two years.
Also, seems like currently redis(dragonflydb) password has to be hardcoded - https://github.com/goharbor/harbor-helm/issues/1641
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Automatically remove secrets being uploaded to repoLauri says that harbor-operator should manage it not helm
Harbor Operator seems dead - no commits in past two years.
Also, seems like currently redis(dragonflydb) password has to be hardcoded - https://github.com/goharbor/harbor-helm/issues/1641
Maybe remove Harbor, and use Gitea packages [container registry] instead?
Fix harbor issuesto Fix harbor issues OR migrate to Giteahttps://distribution.github.io/distribution/ also an option
https://gist.github.com/mikroskeem/ca353590ac5bdec47270ac810eeef078