Detecting Kubernetes API Deprecations with pluto

• kubectx

  40 16,894 3.3 Go

  Faster way to switch between clusters and namespaces in kubectl

Then switch Kubernetes context e.g. using kubectx

• pluto

  18 1,960 6.3 Go

  A cli tool to help discover deprecated apiVersions in Kubernetes

  

In large clusters with dozens of resource types and versions, this can become tedious and error-prone. Luckily, there are tools like pluto by FairwindOps which assist us in spotting deprecated and soon-to-be-removed resource API versions.

• InfluxDB

  www.influxdata.com sponsored

  Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.

  

• k3d

  76 5,067 7.3 Go

  Little helper to run CNCF's k3s in Docker

  

To get a clearer picture, let's have a look at the second problem and see how Kubernetes responds if we try to deploy a resource using a removed API version. To do this, we spin up a local Kubernetes cluster with k3d

• binenv

  4 363 6.7 Go

  One binary to rule them all. Manage all those pesky binaries (kubectl, helm, terraform, ...) easily.

  

Pluto is available on multiple platforms and via a variety of package managers. We'll use binenv here.

• helm

  206 26,013 9.0 Go

  The Kubernetes Package Manager

  

If we deploy our resources with Helm, Pluto also provides a detect-helm subcommand that checks our releases for deprecated API versions.

• WorkOS

  workos.com sponsored

  The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.

  

Suggest a related project