arkade VS k3s

If you omit sudo, then you can move the binary yourself.

And of course, there's nothing stopping you visiting the releases page - or installing my tap and getting it from Brew!

https://github.com/alexellis/arkade/releases

I strongly discourage actually using such a tool in a professional setting for a host of reasons but that is exactly what https://github.com/alexellis/arkade appears to be going for.

https://docs.oracle.com/iaas/Content/FreeTier/freetier_topic-Always_Free_Resources.htm https://rancher.com/docs/k3s/latest/en/ https://helm.sh/docs/intro/install/ https://github.com/alexellis/arkade https://cert-manager.io/docs/tutorials/acme/nginx-ingress/ https://docs.openfaas.com/deployment/kubernetes/ https://docs.openfaas.com/cli/install/

If you've not yet heard of or used arkade - check it out on GitHub https://github.com/alexellis/arkade/

For the CNCF landscape of tooling there's Arkade, which would at least cover you on the k9s front. [1]

[1] https://github.com/alexellis/arkade

I built a feature in arkade [1] to pull in binaries for CLIs for infrastructure and developer tooling that I wanted to use - it now has 72 CLIs that you can pull down with a single command and most importantly, as near to instantly as you're going to get.

For instance: arkade get [email protected] yq helm faas-cli

It's not got anywhere near the catalog of brew, and doesn't compile software, or help you find lib-xyz for your Yubikey, but it is really fast and has a growing community behind it.

It works on MacOS, Linux, Windows and arm hosts to determine the correct download URL and pull in a binary.

[1] https://github.com/alexellis/arkade

Contributions are welcome.

For self-hosting I've found https://k3s.io to be really good from the SUSE people. Works on basically any Linux distro and makes self-hosting k8s not miserable.

Yes it’s going to depend on which k8s distribution you’re using. We have work in-progress for k3s to natively support nix-snapshotter: https://github.com/k3s-io/k3s/pull/9319

For other distributions, nix-snapshotter works with official containerd releases so it’s just a matter of toml configuration and a systemd unit for nix-snapshotter.

We run Kubernetes outside of NixOS, but yes the NixOS modules provided by the nix-snapshotter certainly make it simple.

K3S: is a lightweight distribution of Kubernetes that is designed for resource-constrained environments. It is an excellent option for running Kubernetes on a virtual machine or cloud server.

I recently purchased a used Lenovo M900 Think Centre (i7 with 32GB RAM) from eBay to expand my mini-homelab, which was just a single Synology DS218+ plugged into my ISP's router (yuck!). Since I've been spending a big chunk of time at work playing around with Kubernetes, I figured that I'd put my skills to the test and run a k3s node on the new server. While I was familiar with k3s before starting this project, I'd never actually run it before, opting for tools like kind (and minikube before that) to run small test clusters for my local development work.

Kubernetes - k3s distribution

I’ve created a local cluster with K3S and installing Windmill could not be simpler with just one chart to configure, which already has sane defaults to get started. For this demo we will also configure workers to passthrough environment variables to our scripts so that they have access to the Kubernetes API server for later.

You should be familiar with Kubernetes and have set up a Kubernetes cluster. I recommend k3s.

K3s' go.mod[0] is insane.

[0] https://github.com/k3s-io/k3s/blob/master/go.mod