eks

Getting error “An error occurred (AccessDenied) when calling the AssumeRole operation: Access denied” after setting up EKS cluster

拜拜、爱过 提交于 2020-06-25 09:23:16
问题 I have created the EKS cluster using AWS console, while creating a cluster I used my pre-created VPCs and subnets, I have created one role eks-role which has AmazonEKSClusterPolicy and AmazonEKSServicePolicy attached to it. I have added the kubeconfig file using: aws eks update-kubeconfig --name eks-cluster --role-arn "arn:aws:iam::############:role/eks-role" When I use kubectl get svc command I get the error as: An error occurred (AccessDenied) when calling the AssumeRole operation: Access

Can't access EKS api server endpoint within VPC when private access is enabled

非 Y 不嫁゛ 提交于 2020-01-22 14:53:22
问题 I have set up EKS cluser with "private access" enabled and set up one instance in the same VPC to communicate with EKS. The issue is if I enable to the "public access", I can access the api endpoint. But if I disable the public access and enable the private access, I can't access api endpoints. When private access is enabled: kubectl get svc Unable to connect to the server: dial tcp: lookup randomstring.region.eks.amazonaws.com on 127.0.0.53:53: no such host When public access is enabled:

Can't access EKS api server endpoint within VPC when private access is enabled

纵然是瞬间 提交于 2020-01-22 14:53:05
问题 I have set up EKS cluser with "private access" enabled and set up one instance in the same VPC to communicate with EKS. The issue is if I enable to the "public access", I can access the api endpoint. But if I disable the public access and enable the private access, I can't access api endpoints. When private access is enabled: kubectl get svc Unable to connect to the server: dial tcp: lookup randomstring.region.eks.amazonaws.com on 127.0.0.53:53: no such host When public access is enabled:

Kubernetes ingress: Not creating an LB?

我们两清 提交于 2019-12-24 18:23:29
问题 I have an EKS cluster. We want - One LB that will redirect to multiple namespace inside the cluster, - Ingress to avoid the "one load balancer for one service". I want to cut it by namespace. I have been reading a bit of documentation but I can't seem to wrap my head around it. I have this yaml, which I understood would create a LB and the ingress rules. apiVersion: extensions/v1beta1 kind: Ingress metadata: name: simple-fanout-example namespace : default annotations: kubernetes.io/ingress

k8s - IP and DNS for postgres with service

霸气de小男生 提交于 2019-12-11 17:57:50
问题 I have created stateful service which is backed by a postgres deployment with k8s. Setup is 3 public subnet|AZ and 3 private subnet|AZ. postgres deployment is in place to create 1 replica and Service with clusterIP: none But now every time I delete the service and create again IP is changing and I was reading something about DNS resolution. I want to access the DB from java client to be deployed another pod on n/w; here i am unable to get static IP. Can I create a service with clusterIP:

Kubernetes Load balancer without Label Selector

孤者浪人 提交于 2019-12-11 17:26:45
问题 Trying to create a Laod Balancer resource with Kubernetes (for an EKS cluster). It works normally with the Label Selector, but we want to only have one LB per cluster, then let ingress direct services. Here is what I currently have : kind: Service apiVersion: v1 metadata: namespace: default name: name annotations: service.beta.kubernetes.io/aws-load-balancer-internal: 0.0.0.0/0 spec: ports: - port: 80 type: LoadBalancer This creates a LB and gives it an internal DNS, but instances never get

Kubernetes ingress-nginx gives 502 error (Bad Gateway)

坚强是说给别人听的谎言 提交于 2019-12-02 07:01:44
问题 I have an EKS cluster for which I want : - 1 Load Balancer per cluster, - Ingress rules to direct to the right namespace and the right service. I have been following this guide : https://www.digitalocean.com/community/tutorials/how-to-set-up-an-nginx-ingress-with-cert-manager-on-digitalocean-kubernetes My deployments: apiVersion: apps/v1 kind: Deployment metadata: name: hello-world namespace: default spec: replicas: 3 selector: matchLabels: app: hello-world template: metadata: labels: app: