inlets VS dashboard

There's alternative solutions like inlets, which enable you to expose private services to the Internet without going through the router / home IP.

Setting up and interacting with your first cluster can be overwhelming. Just like me, you might have come across the infamous kubernetes/dashboard, followed the installation instructions, and asked yourself: "What did I just do and why exactly does this work the way it works?" And after some tinkering with your cluster, you might have installed even more external tools that help you with some specific aspects of cluster management, providing you with either a CLI or a Web UI.

Loki needs Promtail

Kibana needs Elasticsearch

I'm not sure if this has good enough log viewing https://github.com/kubernetes/dashboard

Created service account (followed this link: https://github.com/kubernetes/dashboard/wiki/Creating-sample-user)

The Kubernetes Dashboard could work for this use case.

yaml GITHUB_URL=https://github.com/kubernetes/dashboard/releases VERSION_KUBE_DASHBOARD=$(curl -w '%{url_effective}' -I -L -s -S ${GITHUB_URL}/latest -o /dev/null | sed -e 's|.*/||') sudo k3s kubectl create -f https://raw.githubusercontent.com/kubernetes/dashboard/${VERSION_KUBE_DASHBOARD}/aio/deploy/recommended.yaml

paste the token created. Have fun! source1 source2

At the end of the guide, two web applications will be deployed: the sample ASP.NET Core app from Microsoft and Kubernetes dashboard. Both served on custom local domains with trusted TLS.

Here's an option developed by the Kubernetes folks, https://github.com/kubernetes/dashboard . There are several more options out there if you search for alternatives to this.

Kubernetes Dashboard GitHub tells:

sorry I misspoke this is the pattern I was thinking of - https://github.com/kubernetes/dashboard/blob/master/modules/web/Dockerfile