Not thoroughly reading the K8s release notes can (and will!) backfire on your containerized workloads.
We all know Kubernetes has a long history of deprecating APIs. For a fast-paced open-source product, it’s somewhat expected. Often, moving forward fast also means losing backward compatibility. The latest Kubernetes v1.22 release is especially significant in that regard because APIs will not only be announced as deprecated but removed from the code:
Imagine what will happen when your favorite managed Kubernetes service (AWS EKS, Google GKE, etc.) upgrades your production cluster to a v1.22 release. Unavoidably, things will break, and your workloads might be significantly impacted.
How do I know if this will impact my cluster?
How do you know if your K8s cluster uses any of the soon-to-be-removed or deprecated APIs? Kubernetes itself doesn’t provide an easy way of listing APIs that are going to be removed soon.
Luckily for you, the DoiT International Cloud Reliability Engineering team has developed kubent (aka, Kube No Trouble)— a tool that many K8s users use to detect just that.
You can read how to install and use kubent directly from Stepan Stipl, the original author in his blog post.