Basically helm deployment doesn't work

[victor-sys-admin]

it's not deploying the half of the volumes

Only 1 volume is deploy

[qrkourier]

Hello @victor-sys-admin 👋

The controller needs one volume to store the bbolt database as a file. Here's the Helm template for that PersistentVolumeClaim: https://github.com/openziti/helm-charts/blob/ziti-controller-1.0.14/charts/ziti-controller/templates/pvc.yaml

The PVC will try to provision with the default storage class, unless you specify a class.

It sounds like the cluster can't satisfy the PVC for some reason. It could be that a PVC with the same name was recently released and hasn't finished cleaning up, or the cloud provider is unable to provision a volume with the specified (or default) storage class for some other reason.

Are you overriding the default storage class? Are there other PVCs in the cluster using the same storage class as the one selected for this Helm release?

[victor-sys-admin]

I just exec the helm controller (changing clientApi.advertisedHost="my.domain" and clientApi.type to ingress)
default storage class work like a charm with my others hundred pods and I run this on bare metal so no issues with cloud providers ...

[qrkourier]

Now I see you meant the secrets, etc. from the pod events, not a pvc. The pod is waiting for those to become available.

Are cert-manager and trust-manager ready?

Is the trust namespace set to the namespace where the ziti controller is deployed?

[qrkourier]

Here where the trust namespace is set: https://github.com/openziti/helm-charts/blob/ziti-controller-1.0.14/charts/ziti-controller/values.yaml#L397

[victor-sys-admin]

OK, when I deploy cert-manager and trust-manager I haven't done any customization, I just follow your documentation.
https://openziti.io/docs/guides/deployments/kubernetes/kubernetes-controller

Do you have a documentation for all required customization ?