The Cloud Native Computing Foundation published their Annual Report for 2021 which outlines the past year and what can be expected in the upcoming 6 months. Community leaders and 62,000 contributors on GitHub came together to report on initiatives and updates to create CNCF’s second annual report.
So, here are the important updates from the Kubernetes Annual Report that we think you need to know.
Saying goodbye to dockershim
After the Kubernetes v1.20 release announced the deprecation of dockershim, further updates show the final removal of dockershim from Kubernetes v1.24. This stems from the creation of dockershim implementing Container Runtime Interface (CRI) support for Docker which has led to several maintenance issues. Changes are in favour of runtimes that use CRI designed for Kubernetes rather than Docker to reduce ongoing issues in the Kubernetes community.
For further information on the removal of dockershim, Kubernetes.io has released a FAQ to help guide you through some frequently asked questions. If you are unsure if this change will affect you, visit “Is your cluster ready for v1.24?” for more details.
#ICYMI #Kubernetes is removing #dockershim in the upcoming v1.24 release. Have a look at the blog for the K8s community's commitments and next steps ☁️ https://t.co/Q5nZmfYid7 pic.twitter.com/sbvIuOBghf— Kubernetes (@kubernetesio) January 24, 2022
Tackling storage capacity tracking
Within the v1.24 release, storage capacity tracking has been introduced to increase the chances of scheduling succeeding on the first try. This allows for nodes for a Pod to be accurately selected based on which Pods have volumes that still need provisioning. Storage capacity tacking in the latest update will allow for Pods to be scheduled that might overwise get stuck due to the choice being made blindly.
The latest Kubernetes v1.24 feature blog dives into the newly GA (generally available), "Storage Capacity Tracking" feature. This feature can help streamline scheduling of pods with volume provisioning needs. Check out the blog to learn more! https://t.co/96J8kgF8MW— K8sContributors (@K8sContributors) May 6, 2022
Making quality a priority
Through the changes made in v1.22 and v1.23, it became apparent that the overall quality of Kubernetes needed to be improved to fix bugs and past errors. By clarifying the standards required by reviewers and approvers, this tackles issues that result in lower quality such as regression and faulty automated tests. The CNCF went on to outline how the release schedule will be adjusted to have more time for feedback on builds.
Finding more resources
By signing up to Civo, you can keep up to date with the latest industry news in our monthly newsletter. You can also get started using our Kubernetes platform today with $250 free credit for your first month.