Ziming

trying to use postgres-operator:v1.8.0, and spilo-14:2.1-p5 but failed to start pod postgresql-cluster-sample-ns-harborcluster-sample-0  it looks like the spec is changed

spec Patroni.PgHba is overwriting pg_hba.conf which used to be append in file, so connect db denied. use ``` func GetPgHba() []string { return []string{ "local all all trust", "hostssl all...

the secret name is changed from something like `harbor.postgresql-cluster-sample-ns-harborcluster-sample.credentials` to `harbor.postgresql-cluster-sample-ns-harborcluster-sample.credentials.postgresql.acid.zalan.do` this would also break upgrading

need to verify in new version

this is not harbor-operator issue, seems harbor registry s3 driver problem track with https://github.com/goharbor/harbor/issues/14470

need to verify again

1. the selector of service harborcluster-sample-harbor-harbor-core-lb seems not correct 2. there seems only loadbalancer for core api service, no portal service

we still should add a new nginx component in order to route the traffic to core pods and portal pods.

we can't easily fix the problem that harbor install fail when enable minio.redirect and loadbalancer now. So currently we should `revert` loadbalancer support. User can still install with nginx-ingress or...

can't install harbor successful