With Kubernetes 1.16 available for a while and starting to slowly roll out across many managed Kubernetes platforms, you might have heard about API deprecations. While fairly simple to deal with, this change might seriously disrupt your services if left unattended.
As Kubernetes feature set evolves, APIs have to evolve too in order to support this change. There are rules in place that aim to guarantee compatibility and stability, and also it does not happen with every release, but eventually, you will have to use the new API version and format as the old one will not be supported anymore.
You can manually go through all your manifests, but that can be fairly time-consuming, it is easy to miss some and might be highly unpractical if you have multiple teams deploying to the cluster, or simply do not have all the current manifest at one place. And this is where Kube No Trouble aka kubent comes to help.
You can easily configure this tool from AWS.
This product collects company name and email address. This information is sent to and stored by the Matoffo. This information will only be used to contact the buyer in regards to the and do not disclosed to third party organizations.