# Controller setup on k8s, helm missing configMap
**URL:** https://openziti.discourse.group/t/controller-setup-on-k8s-helm-missing-configmap/3699
**Category:** Support
**Created:** [December 30, 2024, 10:02am UTC](https://openziti.discourse.group/t/controller-setup-on-k8s-helm-missing-configmap/3699 "2024-12-30T10:02:55Z")
**Posts on this page:** 4
**Page:** 1
### Author:  [@checkin247](https://openziti.discourse.group/u/checkin247)
#### Post date: [December 30, 2024, 10:02am UTC](https://openziti.discourse.group/t/controller-setup-on-k8s-helm-missing-configmap/3699/1 "2024-12-30T10:02:55Z")
Hi,
I am trying out ziti and following up on the k8s deployment using the helm chart and got stuck at
Pod start error is:
```bash
configmap "ziti-controller-ctrl-plane-cas" not found
```
I followed the guide here:
> **[Install the Controller in Kubernetes | OpenZiti](https://openziti.io/docs/guides/deployments/kubernetes/kubernetes-controller/)**
>
> open source zero trust
There is a section of optional subcharts of [cert-manager](https://openziti.io/docs/guides/deployments/kubernetes/kubernetes-controller#optional-sub-charts)
I do not really want to install them as I already have it installed.
So I installed the helm chart without the sub charts, but then the init-container hangs at:
```bash
Events:
Type Reason Age From Message
---- ------ ---- ---- -------
Normal Scheduled 35s default-scheduler Successfully assigned openziti/ziti-controller-77fc6949c8-wp6pl to aks-ap3-32698053-vmss000010
Normal SuccessfulAttachVolume 18s attachdetach-controller AttachVolume.Attach succeeded for volume "pvc-36d810a9-9a0b-4471-9bc1-244da0d8cfca"
Warning FailedMount 3s (x7 over 35s) kubelet MountVolume.SetUp failed for volume "ziti-controller-ctrl-plane-cas" : configmap "ziti-controller-ctrl-plane-cas" not found
```
The certificates are created though
```bash
$ k get certificate
NAME READY SECRET AGE
ziti-controller-admin-client-cert True ziti-controller-admin-client-secret 137m
ziti-controller-ctrl-plane-client-identity True ziti-controller-ctrl-plane-client-identity-secret 137m
ziti-controller-ctrl-plane-identity True ziti-controller-ctrl-plane-identity-secret 137m
ziti-controller-ctrl-plane-intermediate-cert True ziti-controller-ctrl-plane-intermediate-secret 137m
ziti-controller-ctrl-plane-root-cert True ziti-controller-ctrl-plane-root-secret 137m
ziti-controller-edge-root-cert True ziti-controller-edge-root-secret 137m
ziti-controller-edge-signer-cert True ziti-controller-edge-signer-secret 137m
ziti-controller-web-client-identity True ziti-controller-web-client-identity-secret 137m
ziti-controller-web-identity-cert True ziti-controller-web-identity-secret 137m
ziti-controller-web-intermediate-cert True ziti-controller-web-intermediate-secret 137m
ziti-controller-web-root-cert True ziti-controller-web-root-secret 137m
```
How to create the configMap (structure) or how to resolve the problem?
The goal is to have ziti controller and router in the k8s cluster and playing along nice with existing deployments.
Thank you for your suggestions.
---
### Author:  [@qrkourier](https://openziti.discourse.group/u/qrkourier)
#### Post date: [December 30, 2024, 6:37pm UTC](https://openziti.discourse.group/t/controller-setup-on-k8s-helm-missing-configmap/3699/2 "2024-12-30T18:37:08Z")
Welcome to the OpenZiti Discourse, @checkin247!
Sounds like a good plan. That symptom points toward trust manager not creating the bundle resource the controller needs to start up.
You can use the existing trust manager instance. Its trust namespace must be the namespace where the Ziti controller is installed.
---
### Author:  [@checkin247](https://openziti.discourse.group/u/checkin247)
#### Post date: [December 31, 2024, 7:50am UTC](https://openziti.discourse.group/t/controller-setup-on-k8s-helm-missing-configmap/3699/3 "2024-12-31T07:50:12Z")
Dear @qrkourier
thank you for your response and pointing me into the right direction.
---
### Author:  [@checkin247](https://openziti.discourse.group/u/checkin247)
#### Post date: [December 31, 2024, 4:24pm UTC](https://openziti.discourse.group/t/controller-setup-on-k8s-helm-missing-configmap/3699/4 "2024-12-31T16:24:55Z")
Got it running, thank you @qrkourier.
conclusion: always work with an own trust-manager per ns if you don't want it to make it overly complicated.