# EKS + linkerd + vcluster

**URL:** <https://linkerd.buoyant.io/t/eks-linkerd-vcluster/528>\
**Category:** Linkerd General Discussion\
**Tags:** proxy\
**Created:** [July 17, 2024, 6:14pm UTC](https://linkerd.buoyant.io/t/eks-linkerd-vcluster/528 "2024-07-17T18:14:35Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![dverzolla](https://yyz1.discourse-cdn.com/flex029/user_avatar/linkerd.buoyant.io/dverzolla/32/152_2.png) [@dverzolla](https://linkerd.buoyant.io/u/dverzolla)\
**Post date:** [July 17, 2024, 6:14pm UTC](https://linkerd.buoyant.io/t/eks-linkerd-vcluster/528/1 "2024-07-17T18:14:35Z")

</div>

Sharing a challenge I had and how I overcome.

I needed to put vcluster inside a aws eks cluster that had already linkerd installed on it.  
The guest vcluster has linkerd also. As the nature of vcluster, the resources created inside the guest are actually created into the host; and the host linkerd was trying to inject itself into the guest linkerd, kinda `inception`. As linkerd was being injected twice into the guest, it wasn’t working properly.  
To workaround this, I’ve added the matchExpressions below, saying that linkerd will be injected only if `vcluster.loft.sh/name` key `DoesNotExist`.

`linkerd 1.24.10`  
`vcluster 19.5`