Differences Between EKS and Traditional Kubernetes Clusters

 

1. Managed Control Plane:

• EKS: AWS manages the Kubernetes control plane (including the API server and etcd).

• Traditional Kubernetes: You are responsible for setting up and managing the control plane.

2. Scalability:

• EKS: Easily scales across multiple AWS Availability Zones for high availability.

• Traditional Kubernetes: Scaling and managing the high availability setup is your responsibility.

3. Security:

• EKS: Integrates with AWS IAM for fine-grained permissions and integrates with other AWS security services.

• Traditional Kubernetes: Requires manual setup and management of security configurations.

4. Maintenance:

• EKS: AWS handles the maintenance of the control plane, including updates and patching.

• Traditional Kubernetes: You are responsible for maintaining and updating the entire Kubernetes infrastructure.

Comments

Post a Comment

Popular posts from this blog

Q48 & 49

Question 48. What Is A Placement Group In Ec2 ? Answer : AWS provides an option of creating a Placement Group in EC2 to logically group the instances within as single Availability Zone. We get the benefits of low network latency and high network throughput by using a Placement Group. Placement Group is a free option as of now. When we stop an instance, it will run in same Placement Group in restart at a later point of time. The biggest limitation of Placement Group is that we cannot add Instances from multiple availability zones to one Placement Group. Question 49. What Types Of Issues Do You Face While Connecting To An Ec2 Instance ? Answer : Some of the possible connection issues with EC2 instance are: Connection time out Permission denied due to host key not found Unprotected private key file Permission denied due to user key not recognized by server No supported authentication method available Server refused the key AWS Video Training
Read more

Q28

Question 28. How To Create Your Own Amazon Machine Image (ami) ? Answer : You can customize a instance that is launched from a public AMI and then save that configuration as a custom AMI for your own use. Instances that you launch from your AMI use all the customizations that you’ve made.
Read more

Q24

Question 24. How To Migrate An Instance To Another Availability Zone ? Answer : You can migrate your EC2 instance from one Availability Zone to another. Following are the steps to migrate an Instance to another Availability Zone: Create an AMI from the running instance Launch an instance from the AMI that you just created, specify the new Availability Zone You can use the same instance type as the original instance, or select a new instance type If the original instance has an associated Elastic IP address, then associate it with the new instance If the original instance is a Reserved Instance, change the Availability Zone for your reservation
Read more