arkade VS ingress-nginx

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.

ingress-nginx

The second one is a combination of tools: External DNS, cert-manager, and NGINX ingress. Using these as a stack, you can quickly deploy an application, making it available through a DNS with a TLS without much effort via simple annotations. When I first discovered External DNS, I was amazed at its quality.

resource "helm_release" "icrelease" { name = "nginx-ingress" repository = "https://kubernetes.github.io/ingress-nginx" chart = "ingress-nginx" version = "4.9.1" namespace = kubernetes_namespace.icnamespace.metadata[0].name set { name = "controller.ingressClassResource.default" value = "true" } }

helm repo add ingress-nginx https://kubernetes.github.io/ingress-nginx helm repo update helm upgrade --install ingress-nginx ingress-nginx/ingress-nginx --namespace ingress-nginx --create-namespace -f custom/ghost/nginx.yaml

For example, if you chose Nginx Ingress, you will use some of its dozens of annotations that are not portable if you decide to switch to another Ingress implementation like Apache APISIX.

The controller is installed with helm upgrade --install ingress-nginx ingress-nginx --repo https://kubernetes.github.io/ingress-nginx --namespace ingress-nginx --create-namespace

helm repo add jetstack https://charts.jetstack.io helm repo add ingress-nginx https://kubernetes.github.io/ingress-nginx helm repo add rancher-latest https://releases.rancher.com/server-charts/latest helm repo update helm repo list

Everything in the YAML snippets below — except for ingress configuration — relates to configuring the NGINX ingress controller. This includes customizing the default configuration.

Keep Documentation Handy: Always have the official NGINX Ingress documentation accessible.