kube-no-trouble VS Gravitational Teleport

There are several tools that help us find out the API deprecations in our clusters. One of them is “kube-no-trouble” aka kubent. At the time I write this document, the latest ruleset is for 1.29 in kubent. I run kubent with target version of 1.29 and got the below result. As you can see, kubent shows the deprecated APIs.

We also leverage tools like Kubent, popeye, kdave, and Pluto to help us manage API deprecations (when Kubernetes deprecates features in updates) and ensure the overall health of our infrastructure.

kubent has been my goto for this - you point it at your cluster, tell it the target version you want to use, and it'll let you know if you have any depreciated resources and what you'll need to change. It's simple to use, quick, and just does the job.

You have to constantly run tools like https://github.com/doitintl/kube-no-trouble / https://github.com/FairwindsOps/pluto.

A great tool for checking depreciations is kubent/kube-no-trouble: https://github.com/doitintl/kube-no-trouble

https://github.com/doitintl/kube-no-trouble can be used to check for deprecated/removed APIs - you'll need to fix these in your codebase. You should fix these before upgrading your cluster

Just upgraded a few clusters from 1.21 to 1.24 the past few weeks. Used kubent (Kube No Trouble https://github.com/doitintl/kube-no-trouble) before upgrading and reviewed the output. Pretty painless process all in all.

For the SSH case mentioned in the article, `ssh -R` trick should already resolve some one-time contingencies (assuming SSH connection is not blocked).

But if you find yourself requesting `ssh -R` too often, maybe just ask those datacenter people to setup a proper SSH Bastion for you. There are opensource solutions and enterprise-level ones (Teleport for example: https://github.com/gravitational/teleport), some also allows you to do audit and access control, which maybe important if you work for a enterprise client.

Teleport - Comprehensive control plane tool, but also supports accessing apps behind NATs. Written in Go.

https://github.com/gravitational/teleport/blob/master/rfd/00...

I ordinarily would have said you reinvented Teleport <https://github.com/gravitational/teleport/tree/v14.3.7#readm...> but now that they've gone AGPL with v15 I'm guessing there's a market for MIT licensed stuff, although for sure since Teleport has been around for so long it has encountered more edge cases and undergone more security reviews. I was surprised while digging up the link that Gravatational is still releasing v13 and v14 updates under Apache 2, so maybe even Teleport will continue to have legs for those who cannot deploy AGPL stuff

Teleport is an SSH for Clusters and Teams and aims to be the drop-in replacement for OpenSSH.

Are you looking to set up SSO for your cloud infrastructure? Or maybe establish tunnels to access services behind NATs and firewalls. Then Teleport is for you. It provides connectivity, authentication, access controls and audit for infrastructure. The newest update has a tonne of new features and improvements including enhanced device trust support, SSH connection resumption, MFA for admin actions, improved provisioning for Okta, and heaps. more. Check out all the changes in the Teleport release notes.

In case you didn't see it: https://goteleport.com/blog/teleport-oss-switches-to-agpl-v3... and https://github.com/gravitational/teleport/pull/35259

I readily admit it's not the same amount of :fu: as BuSL or whatever the fuck is going on over at Sentry but still :-( as compared to their much friendlier Apache 2

Link to GitHub -->