ama VS k9s

If you want to stick on one machine, you can always just use a single node Docker Swarm to get the fully automated zero downtime deploys you want with Docker Compose:

https://github.com/BretFisher/ama/discussions/146

Follow Bret here

Check out Bret Fishers courses and content - https://www.bretfisher.com/

This Awesome List is maintained by Bret Fisher (and coming soon, maintainers #3). This is a curated list of working tools and resources for using Swarm. It is not an official list, but a community effort to help people find the best tools and resources for Swarm in 2023 and beyond.

https://www.bretfisher.com/ - awesome guy, awesome discord (https://devops.fan). Awesome Talks

Composer is not meant to run in production. It is only meant for development or building images. Make sure to read Getting started with swarm mode and check this if you want to use run your build image on a proper environment. (recommended)

I don't know if I would call myself an expert, but worrying about security is a big concern of mine and my job. While there are some security benefits to running your app in a container, you're correct in thinking there are some things to keep in mind while writing your Dockerfiles and using Docker. Check out Bret Fisher's write up on security concerns using Docker. This is the second time that I've mentioned him. He's a Docker Captain and recognized by Docker as an expert. His advice is sound.

Only one host for production environment. What to use: docker-compose or single node swarm? · Issue #8 · BretFisher/ama (github.com)

Pierre: The first tool I recommend is K9s. It's not just a time-saver but a productivity booster. With its intuitive interface, you can speed up all the usual kubectl commands, access logs, edit resources and configurations, and more. It's like having a personal assistant for your cluster management tasks.

The last thing you really need is a common set of tools that you want fingertip access to. I really commonly use LazyGit and K9s in my day job so those are the tools I will show off in this article.

K9s is your best friend (get it? 🐶) when exploring your cluster via the terminal. It shares commonality with Vim for its interaction style using shortcuts and starting commands with: but don’t let that discourage you. K9s keeps a vigilant eye on Kubernetes activities, providing real-time information and intuitive commands for resource interaction.

k9s: brew install k9s

I would like to put in a vote for k9s, which is also on the list at Terminal Trove. [0] It's the most convenient tool I've ever found for Kubernetes management. Based on that experience I'll definitely be checking out Harlequin.

[0] https://k9scli.io/

$ wget https://github.com/derailed/k9s/releases/download/v0.29.1/k9s_Darwin_amd64.tar.gz $ tar -xzf k9s_Darwin_amd64.tar.gz $ sudo mv k9s /usr/local/bin/

All in all, run things, do some kubectl apply -f something.yml every day, install k9s, and try to configure a big one cluster at some point.

(K9s is one of my favorite tools for navigating Kubernetes clusters through the CLI).

K9s is an open-source, terminal-based UI for interacting with your Kubernetes clusters, making navigating, observing, and managing your apps easier. If you use Kubectl but wish it was easier and faster to use, K9s might be just what you're looking for!

k9s