Amazon EKS clusters require kubectl and kubelet binaries and the aws-cli or aws-iam-authenticator binary to allow IAM authentication for your Kubernetes cluster.
Locally run kubernetes requires to set proper context to access the cluster.
You can easily delete pods running on one Node and start them on another Node using codon feature.
Parse the json output of the kubernetes object and apply wait condition on status.
The kubelet acts as a bridge between the Kubernetes master and the nodes, managing the pods and containers running on a machine. The kubelet translates each pod into its constituent containers and fetches individual container usage statistics from the container runtime through the container runtime interface. The kubelet fetches this information from the integrated cAdvisor for the legacy Docker integration. It then exposes the aggregated pod resource usage statistics through the metrics-server Resource Metrics API.
This article covers setting up of mssql-tools which includes the sqlcmd client utility. These steps are needed for container in which you wish to use the sqlcmd command or other Microsoft-originating utilities on Ubuntu to interact with an MSSQL Server.
Additional user-data can be passed to the host provisioning by setting the additionalUserData field.
You can install a Kubernetes cluster on AWS using a tool called kops. kops provisions fully automated installation of cluster.