Outdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchWindows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallThis walkthrough takes a sample application from an EKS cluster that has compute and working network access through deployment and verification. It uses AWS’s Linux sample, which creates a three-replica Deployment and an internal-only ClusterIP Service. It does not make the app internet-facing.
Choose how to create the cluster
This demo assumes you are creating a standard Amazon EKS cluster with a managed node group, not using EKS Auto Mode. If you already have a reachable cluster with at least one node, skip to connecting kubectl. AWS describes eksctl as the simpler, faster getting-started route; the AWS Management Console and AWS CLI route makes the individual resources and their relationships more visible. The cited console guide excludes Auto Mode; AWS documents that mode separately.
As an Amazon Associate I earn from qualifying purchases.
- Choose
eksctlwhen you want a more automated setup. - Choose the console and AWS CLI when the demo should show the resources being configured.
The workload steps below are the same either way. Follow the cleanup instructions for the cluster-creation route you chose when the demonstration is finished.
Free tools Windows power users keep installed
One-click scans. No signup required.
Prepare identity, networking, and tools
To create a cluster, you need AWS credentials for an identity authorized to create and manage the required EKS and related resources, a compatible VPC and subnets, and the appropriate command-line tools. AWS’s eksctl example requires at least two subnet IDs. If a cluster already exists, confirm that your AWS identity can access it and that it has at least one node available for the sample workload.
#1 Best Overall
- Install and configure the AWS CLI and AWS credentials.
- Install
kubectland, if using that route,eksctl. - Check AWS’s current cluster and tool version requirements before recording. Supported Kubernetes versions and minimum tool versions change, so do not treat an example version in a guide as a permanent default.
Create or select the EKS cluster
Use the AWS instructions for your chosen route to create the standard cluster and its compute, or identify an existing cluster. An application Deployment needs a reachable Kubernetes control plane and worker capacity; the AWS sample assumes at least one node. Keep the region and cluster name handy because they are needed to configure kubectl if the creation workflow has not already done so.
Configure kubectl and confirm access
If cluster setup did not configure your kubeconfig, run the AWS command below, replacing the placeholders with the actual region and cluster name:
Rank #2
aws eks update-kubeconfig --region REGION --name CLUSTER_NAMEAWS documents this method in its guide to connecting kubectl to an EKS cluster. Then check that the active context can reach the cluster:
kubectl get svcThe command should return the cluster’s Services rather than a connection or authentication error. If it fails, confirm the selected AWS identity, region, cluster name, kubeconfig context, and network access before applying the sample.
Deploy the sample application
Follow AWS’s Linux sample application deployment for the current manifest and commands. The example creates a namespace named eks-sample-app, deploys an image with three replicas, and creates a ClusterIP Service. Apply the sample’s namespace and workload manifests to the connected cluster as instructed there; do not substitute an internet-facing service type if the goal is to reproduce this example.
Verify the Pods and Service
Inspect the resources in the sample namespace and check that the intended Pods become ready. AWS’s sample guide demonstrates listing resources and describing the Service.
Rank #4
kubectl get all -n eks-sample-appThen inspect the Service:
kubectl describe service eks-sample-linux-service -n eks-sample-appUse the Service description to confirm that its selector matches the labels on the deployed Pods and that the endpoints correspond to those Pods. If no endpoints appear, check that the Pods are running and ready and that the Service selector and Pod labels agree. A Service object existing on its own does not prove that the application is reachable.
Understand what is—and is not—reachable
The sample’s ClusterIP Service is accessible only from inside the cluster. It is not a public URL and does not, by itself, expose the application to the internet. To provide external access, configure an appropriate ingress or load-balancing arrangement; AWS points to the AWS Load Balancer Controller as one option. The controller and its routing configuration are additional setup, not part of the sample Service.
- For an internal deployment demo: keep
ClusterIPand verify the workload and Service inside the cluster. - For an external-access demo: add and configure an ingress or load balancer using the relevant AWS guidance, then verify the resulting endpoint separately.
Clean up the demonstration
Remove the workload and cloud resources when you are done so the demo environment is not left running. Use the cleanup procedure for the exact cluster-creation method you selected; resource teardown differs between setup routes, so use the matching AWS instructions rather than assuming that deleting the sample namespace also deletes the EKS cluster or its networking.
AWS describes its example material as intended for learning and testing, not production use. Treat the sample as a deployment demonstration, not a production-ready application blueprint. See Learn Amazon EKS by example.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
