In kubernetes series article, we will explore Kubernetes’ essential features, its role in managing containerized workloads, and its extensibility options, empowering developers to harness its full potential.

Troubleshooting Amazon EKS When faced with issues in your Amazon Elastic Kubernetes Service (Amazon EKS) workloads, there are various kubectl commands at your disposal

kubectl logs: Easily view the logs of a container within a Pod.

kubectl port-forward: Establish connections between ports on your local host and those on a container.

kubectl exec: Execute commands inside a container for further investigation.

Additional Resources:

Following are some troubleshooting for references:

error: exec plugin: invalid apiVersion “”

If invalid apiVersion happened:

error: exec plugin: invalid apiVersion ""

Update the kubectl and run commands

aws eks update-kubeconfig --name $EKS_CLUSTER_NAME --region $AWS_REGION
kubectl version

error: exec plugin: invalid apiVersion “”

If meets the error error: exec plugin: invalid apiVersion ""

Please make sure your AWS CLI is lastest version, and re execute update-kubeconfig.

aws --profile backyard eks update-kubeconfig --region $AWS_REGION --name $EKS_CLUSTER_NAME

or change the to

no nodes available to schedule pods

If get no nodes available to schedule pods, it mean your cluster have no enough node.

You can confirm your node status

kubectl get nodes

If you get No resources found


Amazon EKS

For more detailed information about Amazon Elastic Kubernetes Service (Amazon EKS), see the AWS re:Invent 2021 Deep Dive on Amazon EKS.

Upgrading your Amazon EKS cluster

For more information about how the upgrade process works for Amazon EKS, see Updating a cluster.

EKS Best Practices Guide

For more information about best practices for working with Amazon EKS, see the EKS Best Practices Guide.

Kubernetes objects

In the demonstration, we showed how to apply a few different types of objects to a Kubernetes cluster. For more information about Kubernetes objects, see Understanding Kubernetes Objects in the Kubernetes documentation.

Pod networking

Amazon EKS supports native VPC networking with the Amazon VPC Container Network Interface (CNI) plugin for Kubernetes. This plugin assigns a private IPv4 or IPv6 address from your virtual private cloud (VPC) to each Pod. We saw these Pods run on the EKS cluster after it was created. For more information about Pod networking with Amazon EKS, see Pod networking using the Amazon VPC Container network interface (CNI) plugin.


For more general information about logging with Kubernetes, see Logging Architecture.

For more information about Amazon EKS control plane logging, see Amazon EKS control plane logging.

EKS Workshop

For more information about examples and tutorials, see EKS Workshop.