kparanoid VS public

I wrote a convoluted tool for this problem which isolates kubectl environments in docker containers: https://github.com/forestgagnon/kparanoid.

This approach allows the convenience of short, context-free commands without compromising safety, because the context info in the shell prompt can be relied on, due to the isolation.

There are some things which don't work well inside a docker container (port-forwarding for example), but it does make it simple to have isolated shell history, specific kubectl versions, etc.

So I put together this "cheat sheet" for us internally and thought I'd share it for anyone interested. Pull requests welcome for updates: https://github.com/wrble/public/blob/main/aws-instance-types.md

Check it out: https://github.com/wrble/public/blob/main/aws-instance-types.md

Every time I'm starting a new service to run internally or reviewing something we have going, I find myself struggling to find the right instance type for the needs.

For instance, there are three families (r, x, z) that optimize RAM in various ways in various combinations and I always forget about the x and z variants.

So I put together this "cheat sheet" for us internally and thought I'd share it for anyone interested.

Pull requests welcome for updates: https://github.com/wrble/public/blob/main/aws-instance-types...

Did I miss anything?