He Weiwei
He Weiwei
I get `error: Maximum call stack size exceeded` when using v1.5.1+, but it's ok with v1.4.3 and v1.5.0.
curl -k https://core.harbor.domain get the following response when using ncp(NSX-T Container Plugin) ingress with internal tls enabled. ``` 400 The plain HTTP request was sent to HTTPS port 400 Bad...
Signed-off-by: He Weiwei
**Actual behavior** A clear and concise description of what the bug is. For the interface with generics ```go type Model[T any] interface { *T TableName() string } ``` ``` go...
All pods' name begins with the name of the harbor cluster excepted redis and postgres. Can we make the pod name of redis and postgres also begins with the name...
Please include the component name for the pod of postgres so that it's easy to know the components used by the harbor. 
We only need two ingresses for the harbor instance, one for the (core, portal), and one for notary. 
Please install postgres, redis and minio operators in the namespace with harbor cluster operator so that it's easy to check the pods of the operators.

## Acceptance Criteria * `scale fn oci-push` exists * Before pushing, Scale transforms the Scale Function and Signature into an OCI * The OCI is pushed to the destination registry...