...
Error: create: failed to create: the server responded with the status code 413 but did not return more information (post secrets)
helm.go:88: [debug] the server responded with the status code 413 but did not return more information (post secrets)
...
I've not had such problem on Microk8s.
I think the default values of request limits should be set according to the configured limits of etcd and kubeapi of Charmed Kubernetes by default and be configurable.
Just stumbled across this one. I was following the deployment guide of Harbor Operator v.1.3.0 from https:/ /github. com/goharbor/ harbor- operator/ blob/ae23ba2c42 d9d4f89a0c65459 be133ed3a6e8036 /docs/installat ion/by- helm-chart. md and running the full-stack deployment command :
helm upgrade --namespace harbor-operator-ns --install harbor-operator charts/ harbor- operator- v1.3.0. tgz --set-string image.repositor y=ghcr. io/goharbor/ harbor- operator --set-string image.tag=v1.3.0 --set installCRDs=true --set redis-operator. enabled= true --set minio-operator. enabled= true --set postgres- operator. enabled= true
I got error from helm:
...
Error: create: failed to create: the server responded with the status code 413 but did not return more information (post secrets)
helm.go:88: [debug] the server responded with the status code 413 but did not return more information (post secrets)
...
I've not had such problem on Microk8s.
I think the default values of request limits should be set according to the configured limits of etcd and kubeapi of Charmed Kubernetes by default and be configurable.