amazon-eks

问题 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

问题 I am exploring the istio service mesh on my k8s cluster hosted on EKS(Amazon). I tried deploying istio-1.2.2 on a new k8s cluster with the demo.yml file used for bookapp demonstration and most of the use cases I understand properly. Then, I deployed istio using helm default profile(recommended for production) on my existing dev cluster with 100s of microservices running and what I noticed is my services can can call http endpoints but not able to call external secure endpoints(https://www

问题 Trying to mount config files from a hostPath to a kubernetes container. This works using minikube and VirtualBox shared folder, but I am unable to make this work on Linux. I making use of AWS EKS and the following architecture https://aws.amazon.com/quickstart/architecture/amazon-eks/. I think my problem is that the files need to live on each of the EKS Node instances. Here is the architecture diagram: Below is the Deployment file. apiVersion: apps/v1 kind: Deployment metadata: name: openhim

问题 I've followed the instructions to create an EKS cluster in AWS using Terraform. https://www.terraform.io/docs/providers/aws/guides/eks-getting-started.html I've also copied the output for connecting to the cluster to ~/.kube/config-eks. I've verified this successfully works as I've been able to connect to the cluster and manually deploy containers. However, now i'm trying to use the Terraform Kubernetes provider to connect to the cluster but cannot seem to be able to configure the provider

问题 I deploy traefik ingress controller pod and then two services, one of them a LoadBalancer type for reverse-proxy and the other a ClusterIP for dashboard. Also I create ingress for redirect all <elb-address>/dashboard to my traefik dashboard. but for some reason I get 404 error code when I trying to request my dashboard at aws-ip/dashboard That is the manifest yamls that I use to set up traefik --- apiVersion: v1 kind: ServiceAccount metadata: name: traefik-ingress-controller namespace: kube

问题 I am working on migrating my applications to Kubernetes. I am using EKS. I want to distribute my pods to different nodes, to avoid having a single point of failure. I read about pod-affinity and anti-affinity and required and preferred mode. This answer gives a very nice way to accomplish this. But my doubt is, let's say if I have 3 nodes, of which 2 are already full(resource-wise). If I use requiredDuringSchedulingIgnoredDuringExecution , k8s will spin-up new nodes and will distribute the

问题 I am running EKS in private subnet and thus unable to create an internet facing load balancer but was able to create Internal LoadBalancer. Is there any way I can create Loadbalancer(probably Manually) in public subnet and point to the pods running in EKS in the private subnet. I was thinking of creating the chain of load balancer in which External load balancer will point to internal load balancer but that too is not possible as the IP address of the internal load balancer is reserved IP.

问题 When using Amazon's K8s offering, the EKS service, at some point you need to connect the Kubernetes API and configuration to the infrastructure established within AWS. Especially we need a kubeconfig with proper credentials and URLs to connect to the k8s control plane provided by EKS. The Amazon commandline tool aws provides a routine for this task aws eks update-kubeconfig --kubeconfig /path/to/kubecfg.yaml --name <EKS-cluster-name> Question: do the same through Python/boto3 When looking at

问题 I have an EKS cluster setup in a VPC. The worker nodes are launched in private subnets. I can successfully deploy pods and services. However, I'm not able to perform DNS resolution from within the pods. (It works fine on the worker nodes, outside the container.) Troubleshooting using https://kubernetes.io/docs/tasks/administer-cluster/dns-debugging-resolution/ results in the following from nslookup (timeout after a minute or so): Server: 172.20.0.10 Address 1: 172.20.0.10 nslookup: can't

问题 Let me describe my scenario: TL;DR When I create a deployment on Kubernetes with 1 attached volume, everything works perfectly. When I create the same deployment, but with a second volume attached (total: 2 volumes), the pod gets stuck on "Pending" with errors: pod has unbound PersistentVolumeClaims (repeated 2 times) 0/2 nodes are available: 2 node(s) had no available volume zone. Already checked that the volumes are created in the correct availability zones. Detailed description I have a