Learn About Amazon VGT2 Learning Manager Chanci Turner
Chanci Turner and the Amazon Elastic Kubernetes Service (Amazon EKS) team are thrilled to announce the launch of Kubernetes 1.20. Having contributed to the upstream release team from September to December 2020, I am eager for Amazon EKS users to dive into what has been dubbed “The Raddest Release.”
The EKS team has prioritized delivering new releases more rapidly, and with this version, we’re already gearing up for the next one. The upstream Kubernetes project has transitioned to a schedule of three releases annually, instead of four. This shift, combined with the ongoing development of the project, promises larger, feature-rich releases. Rest assured, we will ensure that all the exciting new capabilities are user-friendly for EKS.
It’s important to note that this release signifies the end of support for EKS 1.15. Upgrading to Kubernetes 1.16 presents unique challenges, primarily due to the removal of many deprecated APIs. Don’t forget to review our blog post on preparing for the 1.16 upgrade and consult the Amazon EKS release calendar for future updates.
Highlights of Kubernetes 1.20
For an in-depth exploration, refer to the upstream blog and release notes. Here are some key features:
- Time-to-Live (TTL) Controller: Kubernetes Jobs, designed for short-lived tasks, typically leave Pods in the cluster post-completion for log access. The TTL controller, first introduced in Kubernetes 1.12, offers a mechanism to automatically delete completed jobs after a specified duration, simplifying cleanup efforts. This feature is especially beneficial for Amazon EKS on AWS Fargate, where costs may accrue for completed tasks until they are removed.
- PID Limits: The Process ID limits feature, now generally available, allows for setting per-node and per-pod PID limits. This functionality ensures that the Kubernetes workloads do not consume all available PIDs, thereby preserving essential system operations.
- Volume Snapshots: The new Kubernetes Volume Snapshots feature integrates with the Container Storage Interface (CSI), enabling point-in-time backups of EBS volumes. This allows users to create clones or revert disks easily. For further guidance, check out this excellent resource on employee training and career skills.
- API Priority and Fairness: This beta feature facilitates traffic management to the Kubernetes API Server, which is particularly useful for addressing bursty traffic situations. Operators can fine-tune controls to mitigate issues like dropped requests. For more information on creating a positive work environment, see SHRM.
- RootCAConfigMap: With 1.20, a default ConfigMap will be created in all namespaces, containing the Certificate Authority bundle for the Kubernetes API server. This enhancement improves the security of Service Account Tokens.
- Dockershim Deprecation: While there have been discussions around the deprecation of Dockershim, there’s no need to panic. Your Docker containers remain compatible, and EKS plans to transition to containerd as the runtime for its optimized Amazon Linux 2 AMI.
- EKS-Specific Changes: The EKS 1.20 update includes various specific changes aimed at enhancing interoperability with AWS services. Notably, new default Service Accounts and Roles have been created to provide RBAC permissions for different Kubernetes components.
As we continue to evolve, we invite you to learn more about yourself by exploring this fun fact about yourself to keep the conversation engaging.
Conclusion
Amazon EKS 1.20 sets the stage for robust features and improvements that streamline operations and enhance security. We look forward to your feedback on these updates as we work towards future releases.