ReadMeFeed / Community knowledge

#amazon-eks

Real questions. Useful conversations. Find the people who know your stack.

Question1 answer· Accepted0 comments0 followingPosted Mar 160 views0 votes

PersistentVolumeClaim is stuck 'waiting for a volume to be created, either by external provisioner "ebs.csi.aws.com"' on new AWS EKS cluster

We have a EKS setup provisioned where we use a Cloud Native Buildpacks based Tekton Pipeline our PipelineRuns are stuck and pending forever without getting a Pod resource. We created a PersistentVolumeClaim like this: apiVersion: v1 kind: PersistentVolumeClaim metadata: name: buildpacks-source-pvc spec: accessModes: - ReadWriteOnce resources: requests: stora

Amazon Web Services

kubernetes

AWS

Question1 answer· Accepted0 comments0 followingPosted Feb 100 views0 votes

couldn't get current server API group list: the server has asked for the client to provide credentials error: You must be logged in to the server

I created the eks cluster trying to connect it with local cli, for that, I installed the aws-cli and also provide the right 'aws configure' credentials. The user which I am using to connect with the aws have the EKS related policy. Still I am getting the following Error ... E0209 21:09:44.893284 2465691 memcache.go:238] couldn't get current server API group

Amazon Web Services

aws-config

kubernetes amazon-web-services

DevOps & Platform

Question1 answer· Accepted0 comments0 followingPosted May 220 views0 votes

"The connection to the server localhost:8080 was refused - did you specify the right host or port?"

I'm on an ec2 instance trying to get my cluster created. I have kubectl already installed and here are my services and workloads yaml files services.yaml apiVersion: v1 kind: Service metadata: name: stockapi-webapp spec: selector: app: stockapi ports: - name: http port: 80 type: LoadBalancer workloads.yaml apiVersion: v1 kind: Deployment metadata: name: stoc

DevOps & Platform

kubernetes amazon-eks

AWS

Question1 answer· Accepted0 comments0 followingPosted Jan 200 views0 votes

Your current user or role does not have access to Kubernetes objects on this EKS cluster

Don't know if this is an error from AWS or something. I created an IAM user and gave it full admin policies. I then used this user to create an EKS cluster using the eksctl CLI but when I logging to AWS console with the root user I got the below error while trying to access the cluster nodes. Your current user or role does not have access to Kubernetes objec

Amazon Web Services

kubernetes eksctl amazon-iam

DevOps & Platform

Question1 answer· Accepted2 comments0 followingPosted Mar 10 views0 votes

Terraform: Error: Kubernetes cluster unreachable: invalid configuration

After deleting kubernetes cluster with "terraform destroy" I can't create it again anymore. "terraform apply" returns the following error message: Error: Kubernetes cluster unreachable: invalid configuration: no configuration has been provided, try setting KUBERNETES_MASTER environment variable Here is the terraform configuration: terraform { backend "s3" {

DevOps & Platform

terraform

kubernetes terraform-provider-aws

AWS

Question1 answer· Accepted0 comments0 followingPosted Feb 40 views0 votes

EKS ALB is not to able to auto-discover subnets

Background : I have a VPC with 3 public subnets (the subnets have access to an internet gateway) I have an EKS Cluster in this VPC, the EKS cluster is created from the console and not using eksctl I used this tutorial from the official aws documentation, I managed to set my ALB controller and the controller is running perfectly: The cluster contains two node

Amazon Web Services

aws-application-load-balancer amazon-web-services amazon-eks

AWS

Question1 answer· Accepted0 comments0 followingPosted Jan 280 views0 votes

What does "eksctl create iamserviceaccount" do under the hood on an EKS cluster?

AWS supports IAM Roles for Service Accounts (IRSA) that allows cluster operators to map AWS IAM Roles to Kubernetes Service Accounts. To do so, one has to create an iamserviceaccount in an EKS cluster: eksctl create iamserviceaccount \ --name <AUTOSCALER_NAME> \ --namespace kube-system \ --cluster <CLUSTER_NAME> \ --attach-policy-arn <POLICY_A

Amazon Web Services

terraform

kubernetes amazon-iam

DevOps & Platform

Question1 answer· Accepted3 comments0 followingPosted Jan 140 views0 votes

Kubernetes Pods Terminated - Exit Code 137

I need some advise on an issue I am facing with k8s 1.14 and running gitlab pipelines on it. Many jobs are throwing up exit code 137 errors and I found that it means that the container is being terminated abruptly. Cluster information: Kubernetes version: 1.14 Cloud being used: AWS EKS Node: C5.4xLarge After digging in, I found the below logs: **kubelet: I01