k9s VS Nomad

Have you seen/tried k9s? https://k9scli.io/

Debug - logging into remote: While devspace, telepresence, and skaffold are nice for remote dev, sometimes the easiest thing to do is to login to the remote container for debugging. You definitely want to use a Kubernetes dashboard - k8s lens, or k9s cli. Along with this, you can use kubectl exec to open up a shell in the container or use ephemeral containers to attach to a running pod introduced in k8s v1.23. The latter is the preferred method in dev environments. Neither of these should be done in prod environments.

6. K9s

Here is the output of the previous command (from the K9s console):

I just ran across K9s, a terminal client for Kubernetes, and figured others may find it useful. I just started my journey into Kubernetes/K3s and happened to stumble across this. Wish I had of found this earlier. Using kubectl is great to list pods and describe them but gets tedious.

K9s — Kubernetes CLI To Manage Your Clusters In Style

Fwiw, having the tools to help you understand what's going on in a running cluster can be quite helpful, imo. For example, Lens or k9s can help with this. Otherwise, you're faced with having the kubectl docs handy at all times. And I know that just by naming these, I'm practically inviting others to point out alternatives. And brace yourself for Helm, which is super-useful and murky when you first start tinkering with it.

The most important thing for me about Kubernetes is that it makes things fun again. (YMMV) The Kubernetes Slack is super friendly and helpful! (also YMMV ;) )

The article is factually accurate and the mental model is consistent with other K8s docs, but I'm not sure I've seen it put so concisely from an outside perspective before.

The ¹ footnote should have been in-line, because "front-loading" complexity is a great explanation: distributed systems are hard, and require a whole bunch of decisions. It's intimidating to be faced will all of those decisions up front, but at least they're all visible, and it forces you to be very clear on what you want, or you get nothing. I'd rather be surprised and confused (which is to say, have to think) now rather than in 6 months when I realize I had not accounted for some something.

Finally ... I would be lost without k9s: https://k9scli.io/

In a previous hackathon, data analyst Chris Migirdic built an IDE where you present your own time series data/problem, and a layer could be provided over it to make time-series predictions. This iteration was quickly dubbed “BYOSQL,” or Bring Your Own SQL, by participants as he explained one could write any SQL query against Lob’s data warehouse, and you'd be able to fit a time series model over that. The most obvious application for Lob is evaluating mailpiece data. Another improvement over the previous version was performance; much of this was attributed to a shift to deployment in Nomad. Finally, another benefit of the program is to pick up what kinds of queries people are running and get an idea of what prediction problems our developers are trying to solve.

That being said, it hasn't kept similar offerings from continuing to pop up as a "less complex" solution. Take Nomad for instance.

HashiCorp Nomad | Full time | Remote

https://www.nomadproject.io

Want to work on an alternative to Kubernetes made by the creators of Terraform, Consul, Vagrant, and Vault? Come work on Nomad at HashiCorp! Our team builds and maintains a highly-scalable, flexible distributed cluster orchestrator. Nomad helps teams run varied workloads including containers, VMs, and raw binaries. Cloudflare, PagerDuty, Roblox, Pandora, and many other large organizations run Nomad in production today.

We are currently looking for both backend and frontend engineers interested in solving hard problems in the DevOps space, tackling interesting distributed systems challenges, and/or working on open source software.

Our stack: Golang & Ember (experience in either is nice to have, but not a hard requirement)

Here’s a link to a full job posting: https://www.hashicorp.com/job/3990643

Also, feel free to reach out to me, a PM on the team, at mnomitch (at) hashicorp (dot) com

In this post, I want to show how you can implement your own tool using the HCL format. The HCL configuration format is used by all the amazing HasiCorp tools like Terraform, Vault, and Nomad.

Nomad Client (www.nomadproject.io - Container Orchestration)

Shoulda been more clear, sorry; I don't use docker or docker swarm. I'm using nomad as my orchestration system (and the cluster I have running at home is exclusively podman nodes, so no docker even). I need to rewrite the docker-compose in nomad's HCL format, which usually this only takes a few minutes but appwrite's docker-compose is pretty dense. I might write a script to do it, tbh.

I think it's often better to "pick your poison" in terms of cloud providers and commit to it, with a rough migration plan that you can execute if you have to. There'll be common patterns in your systems that can be repeated if a large-scale lift-and-shift has to happen for some reason. But it's never easy, and I've found different clouds to have their own idiosyncrasies that make migration difficult - larger migrations will inevitably take time, effort, and lots of planning.

If you're looking for alternatives, or something lighter weight than Kubernetes, I've used Nomad (plus Terraform and Ansible) and some shell scripts to get repeatable clusters deployed and migrated between cloud providers: https://www.nomadproject.io/

Nomad can also work. It's relatively popular and advertised as less complicated than K8's https://www.nomadproject.io/

Hashicorp Nomad provides container and service orchestration across all the RaspberryPis and the Mac Mini