Introduction of New Amazon EKS Console | Amazon Web Services Blog

This article is translated by Introducing The New Amazon EKS Console.

Since Amazon Elastic Kubernetes Service (EKS) has been provided at Re: Invent 2017, it has evolved rapidly to satisfy the needs of users using Kubernetes in the production environment.Customers such as Intel, Snap, Intuit, Goddy, and Autodesk are running the most confidential mission -critical applications on Amazon EKS because of security, reliability, and scalability.

Amazon EKS had no simple way to easily visualize the Kubernetes application or API resource settings.To identify the problem and investigate, it was necessary to manually track Kubernetes and the entire AWS.All of these tasks needed a lot of time to start and execute Amazon EKS, especially for new users.

On December 1, 2020, we are happy to be able to announce a new Amazon EKS console.At Amazon EKS, you can check the status of Kubernetes, applications, and related cloud drills in a single location.By using a new console, you can quickly get information about her Kubernetes environment, understand all the dependencies of various components in the application, and confirm that it is properly deployed.Is easy.

See Kubernetes cluster in detail

Since the EKS console is hosted by AWS, no additional setup or settings are required.Just open the console and select a cluster.

You will first notice that the cluster's worker node list is displayed on the Overview tab. From the Kubernetes control plane, these nodes are computing resources that run the Kubernetes application. Click on the node to see all the information that the Kubernetes API server knows about this node. You can quickly explore a variety of nodes and find a link to the related EKS managed node group and the EC2 instance represented by that node. The console can quickly come and go from Kubernetes to AWS, which helps to troubleshoot the problem and quickly understand what is happening in a cluster. Interestingly, using Fargate, each executed pod is displayed as a node in the cluster. This is because Fargate runs a unique Kubernetes node agent for 1 pod.

Next is the Workloads tab.Workload is an application running in Kubernetes.The application running in the cluster is displayed on this tab.By default, all workloads are displayed, but it can be narrowed down by namespace or workload type.You can quickly find the workload you are looking for.

Note that RBAC only displays access authority workloads and namespace.Use a drop -down collector to quickly filter the workload with namespace and narrow down the cluster workload.

In Kubernetes, each workload defines one or more pods executed in the cluster.POD can define one or more containers and execute multiple containers together.Click on one of the workloads (here, My-DePloyment) to see the details of this Deployment resource and the actually executed pod.

From here, let's make a little deeper.You can check the definition and status by clicking individual pods.You can check the containers of the pod and display the container images, volume mounts, and other settings you are using.This is useful when checking for trouble shooting in the event of a disability or a change in the manifest.

Here are some nice features.This is a deep link to the node where this pod is running.Using this, you can check where the pod is located, and better understand if a specific node problem is causing an application.Providing such a context is an important goal of this new console, providing a more unified experience that integrates Kubernetes and AWS.

Pod containing multiple containers can easily find out all containers contained in the pod.POD containers can be deployed and can quickly display the status and settings of each container.This section describes the Amazon Elastic Block Store (EBS) CSI Driver.This driver is useful for his EBS volume provisioning management in a cluster.

All cluster management controls are here and are hidden under the Configuration tab.You can check all configuration information, computing and logging control here.The newly added Add-ons tab displays the status and setting information of EKS Add-ons.

Built -in security

Powerful security control is an important factor in running Kubernetes, and the new EKS console is no exception.His access to his Kubernetes API using the console can control the tag -based and are also testimony to AWS CloudTrail.You can use RBAC in a Kubernetes cluster to allow users to access their specific namespace and other resources.Based on her RBAC mapping in her IAM roll in the cluster's authentic configmap, each user has the authority to display the cluster resource.And the same is true when using a console.This extends existing best practices related to cluster access, allowing intuitive operation as expected.

As the center of Kubernetes on AWS

The new EKS console helps to connect Kubernetes and AWS more closely.Next year, we will add support to display detailed configuration information for each Kubernetes resource on the cluster, the cross link between Kubernetes and AWS will be even easier, and related metrics and tools are directly directly to the context of resources and applications.You can get insight from the entire application and the entire cluster.

We will also be able to visualize any Kubernetes cluster, regardless of where the Kubernetes cluster is running.Currently, the EKS console supports her EKS cluster in the cloud.As a part of EKS Anywhere, the on -premises cluster can be easily connected to the EKS, and it will be possible to obtain consistent on -demand insights related to applications and infrastructure.

Available now

The new EKS console can be used in all new and existing EKS clusters from today.To start, go to the EKS console and create or click any cluster.See EKS documentation for details and procedures.

-Nate & Jesse

The translation was handled by the Solution Architect.