# Any idea if we can use aws farget as existing cluster install?

**URL:** <https://community.replicated.com/t/any-idea-if-we-can-use-aws-farget-as-existing-cluster-install/1390>\
**Category:** Supporting your customers\
**Tags:** vendor, kots\
**Created:** [March 19, 2024, 4:54pm UTC](https://community.replicated.com/t/any-idea-if-we-can-use-aws-farget-as-existing-cluster-install/1390 "2024-03-19T16:54:20Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![dmuley](https://yyz2.discourse-cdn.com/flex030/user_avatar/community.replicated.com/dmuley/32/572_2.png) [@dmuley](https://community.replicated.com/u/dmuley)\
**Post date:** [March 19, 2024, 4:54pm UTC](https://community.replicated.com/t/any-idea-if-we-can-use-aws-farget-as-existing-cluster-install/1390/1 "2024-03-19T16:54:20Z")

</div>

Hello,

I was trying to install the kotsadm app on eks with farget but its not getting persistent volume assigned to it.  
Is there any restriction of KOTS to have EBS storage only ?

```auto
 Warning FailedScheduling 58m fargate-scheduler Pod not supported on Fargate: volumes not supported: kotsadm-minio not supported because: PVC kotsadm-minio-kotsadm-minio-0 not bound

```

and none of them getting up.

```auto
kubectl get all --all-namespaces
NAMESPACE NAME READY STATUS RESTARTS AGE
icedq pod/kotsadm-minio-0 0/1 Pending 0 121m
icedq pod/kotsadm-rqlite-0 0/1 Pending 0 121m
kube-system pod/coredns-54d6f577c6-44jlz 0/1 Pending 0 167m
kube-system pod/coredns-54d6f577c6-ffg4j 0/1 Pending 0 167m

NAMESPACE NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE
default service/kubernetes ClusterIP 172.20.0.1 <none> 443/TCP 169m
icedq service/kotsadm-minio ClusterIP 172.20.232.83 <none> 9000/TCP 121m
icedq service/kotsadm-rqlite ClusterIP 172.20.187.143 <none> 4001/TCP 121m
icedq service/kotsadm-rqlite-headless ClusterIP None <none> 4001/TCP 121m
kube-system service/kube-dns ClusterIP 172.20.0.10 <none> 53/UDP,53/TCP,9153/TCP 167m

NAMESPACE NAME DESIRED CURRENT READY UP-TO-DATE AVAILABLE NODE SELECTOR AGE
kube-system daemonset.apps/aws-node 0 0 0 0 0 <none> 167m
kube-system daemonset.apps/eks-pod-identity-agent 0 0 0 0 0 <none> 160m
kube-system daemonset.apps/kube-proxy 0 0 0 0 0 <none> 167m

NAMESPACE NAME READY UP-TO-DATE AVAILABLE AGE
kube-system deployment.apps/coredns 0/2 2 0 167m

NAMESPACE NAME DESIRED CURRENT READY AGE
kube-system replicaset.apps/coredns-54d6f577c6 2 2 0 167m

NAMESPACE NAME READY AGE
icedq statefulset.apps/kotsadm-minio 0/1 121m
icedq statefulset.apps/kotsadm-rqlite 0/1 121m

```

I dont see any mentions of farget or ebs in replicated documentation, but i guess kotsadm-minio uses ebs for storage.

---

<div class="post-metadata">

**Author:** ![jdewinne](https://yyz2.discourse-cdn.com/flex030/user_avatar/community.replicated.com/jdewinne/32/152_2.png) [@jdewinne](https://community.replicated.com/u/jdewinne)\
**Post date:** [March 19, 2024, 5:13pm UTC](https://community.replicated.com/t/any-idea-if-we-can-use-aws-farget-as-existing-cluster-install/1390/2 "2024-03-19T17:13:50Z")

</div>

Hi @dmuley I’m not sure if kots will work on Fargate. In the past I’ve seen that typically the storage part is a potential problem. More info on how kots uses storage and options how to for example disable minio: [About Selecting Storage Add-ons | Replicated Docs](https://docs.replicated.com/vendor/packaging-installer-storage#about-persistent-storage-for-kots)

Can you check the creation of the PV’s? I’m assuming that is where we might find the root cause.