k9s VS minikube

k9s If you're more comfortable working from the terminal, k9s is a great tool. It provides a real-time, terminal-based UI for Kubernetes, allowing you to view logs, pods, services, and resources interactively. github

More information around k9s can be found here: https://k9scli.io/

wget https://github.com/derailed/k9s/releases/download/v0.32.5/k9s_linux_amd64.deb

K9s is a terminal-based UI to interact with your Kubernetes clusters. This project aims to make it easier to navigate, observe, and manage your deployed applications in the wild. K9s continually watch Kubernetes for changes and offer subsequent commands to interact with your observed resources.

That's it. As far as the installation goes, I had a Kubernetes cluster up and running. I had to install K9s in my local machine to manage the cluster and bind the cluster to the ./kube/config file.

> Pods, logs, shells, YAMLs, all in one integrated interface

Has anyone tried Kubed?

Personally I have very good experience with k9s which seems to do the same, and a bit more.

https://k9scli.io/

wget https://github.com/derailed/k9s/releases/download/v0.24.15/k9s_Linux_x86_64.tar.gz tar -xvf k9s_Linux_x86_64.tar.gz sudo mv k9s /usr/local/bin/

Terminal based UI to interact with your Kubernetes cluster

New-Item -Path 'c:\' -Name 'minikube' -ItemType Directory -Force Invoke-WebRequest -OutFile 'c:\minikube\minikube.exe' -Uri 'https://github.com/kubernetes/minikube/releases/latest/download/minikube-windows-amd64.exe' -UseBasicParsing

Kubernetes cluster: You need a running Kubernetes cluster that supports persistent volumes. You can use a local cluster, like kind or Minikube, or a cloud-based solution, like GKE%20orEKS or EKS. The cluster should expose ports 80 (HTTP) and 443 (HTTPS) for external access. Persistent storage should be configured to retain Keycloak data (e.g., user credentials, sessions) across restarts.

Minikube: Ensure you have Minikube installed and running. If not, download and install it from the official website: https://minikube.sigs.k8s.io/

Visit the Minikube releases page and download the latest release for your operating system.

A Kubernetes cluster - we're using a local Minikube cluster (https://minikube.sigs.k8s.io)

To begin with, I don't have a home lab as such, so I'll run everything through minikube. I may switch things up later to get a more "realistic" k8s install, but minikube will be fine for a start.

With the containerized Node.js/Express API, I could run multiple containers, scaling to handle more traffic. Using a tool called minikube, we can easily spin up a local Kubernetes cluster to horizontally scale Docker containers. It was possible to keep one shared instance of the database, and many APIs were routed with an internal Kubernetes load balancer.

Install Minicube - a tool that allows us to spin up a Kubernetes cluster in a local machine Run minikube start to start your Kubernetes cluster Run minikube dashboard to spin up a web-based user interface that allows you to manage your Kubernetes cluster

If you're just messing around, just use kind (https://kind.sigs.k8s.io) or minikube if you want VMs (https://minikube.sigs.k8s.io). Both work on ARM-based platforms.

You can also use k3s; it's hella easy to get started with and it works great.