# Problems with ELK over EKS Amazon and kubernetes **URL:** \ **Category:** Elasticsearch\ **Created:** [February 7, 2023, 5:08am UTC](https://discuss.elastic.co/t/problems-with-elk-over-eks-amazon-and-kubernetes/324851 "2023-02-07T05:08:08Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![Milton](https://avatars.discourse-cdn.com/v4/letter/m/87869e/32.png) [@Milton](https://discuss.elastic.co/u/Milton)\ **Post date:** [February 7, 2023, 5:08am UTC](https://discuss.elastic.co/t/problems-with-elk-over-eks-amazon-and-kubernetes/324851/1 "2023-02-07T05:08:08Z")
How can I configure an Elasticksearch ELK over EKS for claim persistent volumes, I have disk problems. # kubectl get pods -A NAMESPACE NAME READY STATUS RESTARTS AGE default counter 1/1 Running 0 112m kube-logging is-cluster-0 0/1 Pending 0 133m ---
**Author:** ![Ayush\_Mathur](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ayush_mathur/32/77134_2.png) [@Ayush\_Mathur](https://discuss.elastic.co/u/Ayush_Mathur)\ **Post date:** [February 7, 2023, 7:55am UTC](https://discuss.elastic.co/t/problems-with-elk-over-eks-amazon-and-kubernetes/324851/2 "2023-02-07T07:55:24Z")
Hello @Milton , welcome to the community ! Can you please share the deployment configuration - part where you are defining and mounting PVC and PV ? If its running as a StatefulSet, then perhaps you will need StorageClass, PV and PVC defined explicitly and then use them in your STS yaml. Also would be good to have the events of your kube-logging pod to understand more on the error being thrown. ---
**Author:** ![Milton](https://avatars.discourse-cdn.com/v4/letter/m/87869e/32.png) [@Milton](https://discuss.elastic.co/u/Milton)\ **Post date:** [February 7, 2023, 7:40pm UTC](https://discuss.elastic.co/t/problems-with-elk-over-eks-amazon-and-kubernetes/324851/3 "2023-02-07T19:40:27Z")
Hi Ayush\_Mathur, good afternoon to you. Please can you share the configurations or yaml to configure the PVs and PVCs to run the elasticksearh+kibana+fluend over kubernetes Amazon EKS, I already have a good time trying to configure on local nodes and on an Amazon EKS cluster. I copy my email please and share the configuration link. > **[Cómo configurar una pila de registro de Elasticsearch, Fluentd y Kibana (EFK)...](https://www.digitalocean.com/community/tutorials/how-to-set-up-an-elasticsearch-fluentd-and-kibana-efk-logging-stack-on-kubernetes-es)** > > Cuando se ejecutan múltiples servicios y aplicaciones en un clúster de Kubernetes, una pila de registro centralizada de nivel de clúster puede servirle para … Email: [vargascalisin@gmail.com](mailto:vargascalisin@gmail.com) Cell, Washatt: 995379762 ---
**Author:** ![Milton](https://avatars.discourse-cdn.com/v4/letter/m/87869e/32.png) [@Milton](https://discuss.elastic.co/u/Milton)\ **Post date:** [February 7, 2023, 10:08pm UTC](https://discuss.elastic.co/t/problems-with-elk-over-eks-amazon-and-kubernetes/324851/4 "2023-02-07T22:08:15Z")
I copy the error messages that it shows me ```auto # kubectl get services --namespace=kube-logging NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE elasticsearch ClusterIP None 9200/TCP,9300/TCP 15s ``` When I issue this command, it gives me this output. # kubectl rollout status sts/es-cluster --namespace=kube-logging Waiting for 3 pods to be ready... ```auto # kubectl get pods --namespace=kube-logging NAME READY STATUS RESTARTS AGE es-cluster-0 0/1 Pending 0 4m39s fluentd-fpxx8 1/1 Running 0 96s fluentd-jf7mz 1/1 Running 0 96s fluentd-mgcn7 0/1 Pending 0 96s kibana-84fc546945-pqj4g 1/1 Running 0 2m41s [root@mongodb-server-1b ~]# kubectl -n kube-logging describe po es-cluster-0 Name: es-cluster-0 Namespace: kube-logging Priority: 0 Service Account: default Node: Labels: app=elasticsearch controller-revision-hash=es-cluster-577cc5b6d8 statefulset.kubernetes.io/pod-name=es-cluster-0 Annotations: kubernetes.io/psp: eks.privileged Status: Pending IP: IPs: Controlled By: StatefulSet/es-cluster Init Containers: fix-permissions: Image: busybox Port: Host Port: Command: sh -c chown -R 1000:1000 /usr/share/elasticsearch/data Environment: Mounts: /usr/share/elasticsearch/data from data (rw) /var/run/secrets/kubernetes.io/serviceaccount from kube-api-access-75p96 (ro) increase-vm-max-map: Image: busybox Port: Host Port: Command: sysctl -w vm.max_map_count=262144 Environment: Mounts: /var/run/secrets/kubernetes.io/serviceaccount from kube-api-access-75p96 (ro) increase-fd-ulimit: Image: busybox Port: Host Port: Command: sh -c ulimit -n 65536 Environment: Mounts: /var/run/secrets/kubernetes.io/serviceaccount from kube-api-access-75p96 (ro) Containers: elasticsearch: Image: docker.elastic.co/elasticsearch/elasticsearch:7.2.0 Ports: 9200/TCP, 9300/TCP Host Ports: 0/TCP, 0/TCP Limits: cpu: 1 Requests: cpu: 100m Environment: cluster.name: k8s-logs node.name: es-cluster-0 (v1:metadata.name) discovery.seed_hosts: es-cluster-0.elasticsearch,es-cluster-1.elasticsearch,es-cluster-2.elasticsearch cluster.initial_master_nodes: es-cluster-0,es-cluster-1,es-cluster-2 ES_JAVA_OPTS: -Xms512m -Xmx512m Mounts: /usr/share/elasticsearch/data from data (rw) /var/run/secrets/kubernetes.io/serviceaccount from kube-api-access-75p96 (ro) Conditions: Type Status PodScheduled False Volumes: data: Type: PersistentVolumeClaim (a reference to a PersistentVolumeClaim in the same namespace) ClaimName: data-es-cluster-0 ReadOnly: false kube-api-access-75p96: Type: Projected (a volume that contains injected data from multiple sources) TokenExpirationSeconds: 3607 ConfigMapName: kube-root-ca.crt ConfigMapOptional: DownwardAPI: true QoS Class: Burstable Node-Selectors: Tolerations: node.kubernetes.io/not-ready:NoExecute op=Exists for 300s node.kubernetes.io/unreachable:NoExecute op=Exists for 300s Events: Type Reason Age From Message ---- ------ ---- ---- ------- Warning FailedScheduling 4m49s default-scheduler 0/3 nodes are available: 3 pod has unbound immediate PersistentVolumeClaims. preemption: 0/3 nodes are available: 3 Preemption is not helpful for scheduling. [root@mongodb-server-1b ~]# ``` Those are the error messages that I get, please your support, if you could send me your ymal. to be able to configure with PV and PVC on an Amazon EKS. Thank you so much Cell: 995379762 Email: [vargascalisin@gmail.com](mailto:vargascalisin@gmail.com) ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [March 7, 2023, 10:08pm UTC](https://discuss.elastic.co/t/problems-with-elk-over-eks-amazon-and-kubernetes/324851/5 "2023-03-07T22:08:37Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.