I`m trying to apply NLB sticky session on a EKS environment. There are 2 worker nodes(EC2) connected to NLB target group, each node has 2 nginx pods. I wanna connect to same pod on my local system for testing. But…
I'm using AWS EKS 1.21 with Fargate (serverless). I'm trying to run Fluentd as a daemonset however the daemonset is not running at all. All the other objects like role, rolebinding, serviceaccount, configmap are already in place in the cluster.…
I have created a Nginx Ingress and Service with the following code: apiVersion: v1 kind: Service metadata: name: myservice spec: type: ClusterIP selector: name: my-app ports: - port: 8000 targetPort: 8000 --- apiVersion: networking.k8s.io/v1 kind: Ingress metadata: name: myingress annotations:…
I have a simple web app that uses volume/persistent volume claim to serve static data from there. Pods got scheduled only on the first worker node where volume resides. How to deal with the shared volume between nodes in case…
I have a kubernetes cluster and i have more than 15 microservices running in it, Each REST API send me a custom header lets say "version":"1.2.0", i need to check this version from each REST api and throw a custom…
I'm using the EKS Construct to create an EKS cluster in CDK. I'm adding the NGINX helm chart to the cluster and I want to export the ingress LoadBalancer URL. The EKS Construct exposes a .getServiceLoadBalancer() method, but it wants…
In my AWS EKS, I have installed nginx-ingress with following command: helm upgrade --install -f controller.yaml --namespace nginx-ingress --create-namespace --version 3.26.0 nginx-ingress ingress-nginx/ingress-nginx Where controller.yaml file looks like this: controller: ingressClass: nginx-internal service: internal: enabled: true annotations: service.beta.kubernetes.io/aws-load-balancer-internal: 0.0.0.0/0 I…
I'm currently trying to deploy NGINX Ingress Controller on my AWS eks Cluster. I have 4 nodes running: NAME STATUS ROLES AGE VERSION ip-10-230-35-48.ec2.internal Ready <none> 7h44m v1.19.6-eks-49a6c0 ip-10-230-39-9.ec2.internal Ready <none> 7h42m v1.19.6-eks-49a6c0 ip-10-230-42-241.ec2.internal Ready <none> 7h49m v1.19.6-eks-49a6c0 ip-10-230-49-228.ec2.internal Ready…
I have followed the below AWS document to create an ALB ingress controller; https://aws.amazon.com/premiumsupport/knowledge-center/eks-alb-ingress-controller-setup/ EKS: version: 1.19 All the services are created successfully, with no errors. But unfortunately, the nodes are not registered in the target groups of the ALB.…
I have deployed a backend API that is connected to the Redis pod and Mongodb pod. The API has successfully established a connection to the mongodb but not Redis, with the following error presented, anyone know how to fix it?…