# Helm install with linkerd-cni plugin get error on init container linkerd-network-validator PodInitializing

**URL:** <https://linkerd.buoyant.io/t/helm-install-with-linkerd-cni-plugin-get-error-on-init-container-linkerd-network-validator-podinitializing/475>\
**Category:** Linkerd General Discussion\
**Tags:** configuration\
**Created:** [May 28, 2024, 2:41pm UTC](https://linkerd.buoyant.io/t/helm-install-with-linkerd-cni-plugin-get-error-on-init-container-linkerd-network-validator-podinitializing/475 "2024-05-28T14:41:57Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![yaronkalatian](https://avatars.discourse-cdn.com/v4/letter/y/77aa72/32.png) [@yaronkalatian](https://linkerd.buoyant.io/u/yaronkalatian)\
**Post date:** [May 28, 2024, 2:41pm UTC](https://linkerd.buoyant.io/t/helm-install-with-linkerd-cni-plugin-get-error-on-init-container-linkerd-network-validator-podinitializing/475/1 "2024-05-28T14:41:57Z")

</div>

we are running on OCI cluster  
the OS of the nodes are:  
Shape: VM.Standard.E4.Flex  
Red Hat Enterprise Linux release 8.9 (Ootpa)

helm install get error adding pod linkerd\_linkerd-proxy-injector-58cc9dc565-k69px to CNI network “oci”: plugin type=“oci-ipvlan” failed (add): unable to allocate IP address

I install the linkerd-cni with helm using flux

> **[linkerd2-cni 2024.5.4 · buoyant/linkerd2-edge](https://artifacthub.io/packages/helm/linkerd2-edge/linkerd2-cni)**
>
> Linkerd is a \*service mesh\*, designed to give platform-wide observability, reliability, and security without requiring configuration or code changes. The Linkerd \[CNI plugin\](https://linkerd.io/2/features/cni/) takes care of setting up your pod's...

but the control-plane init container which I used the helm release (we are using flux) is not initializing:

> **[linkerd-control-plane 2024.4.5 · buoyant/linkerd2-edge](https://artifacthub.io/packages/helm/linkerd2-edge/linkerd-control-plane/2024.4.5)**
>
> Linkerd gives you observability, reliability, and security for your microservices — with no code change required.

I set the repairController to true and the linkerd-cni pods are running with 2 containers .

I tried the iptablesMode: “nft” but with no success  
I tried to comment the: proxyUID: 2102 but still with no success

Defaulted container “linkerd-proxy” out of: linkerd-proxy, proxy-injector, linkerd-network-validator (init)  
Error from server (BadRequest): container “linkerd-proxy” in pod “linkerd-proxy-injector-854f664bc5-vk42q” is waiting to start: PodInitializing

---

<div class="post-metadata">

**Author:** ![Alex](https://yyz1.discourse-cdn.com/flex029/user_avatar/linkerd.buoyant.io/alex/32/63_2.png) [@Alex](https://linkerd.buoyant.io/u/Alex)\
**Post date:** [June 5, 2024, 11:00pm UTC](https://linkerd.buoyant.io/t/helm-install-with-linkerd-cni-plugin-get-error-on-init-container-linkerd-network-validator-podinitializing/475/2 "2024-06-05T23:00:55Z")

</div>

Hi @yaronkalatian

I’ve never seen this particular error before, but based on the message in the error, it does seem like it might be an issue with the oci-ipvlan plugin, not the linkerd-cni plugin.