glasskube VS dashboard

You know you are dealing with a Kubernetes engineer when the “k“ key on their keyboard has seen better days. At the Glasskube office, you will find spare “k“ keys all over the place, just in case 😄

Glasskube has been on a tear lately. 🚀

As an open-source project maintainer, you should be obsessed with Developer Experience. I don’t need to convince you that the README.md needs to be clear and informative. Everybody knows how great documentation can elevate a project. Having a top-notch CONTRIBUTING.md file is the missing piece to retain the open-source contributors you attract.

One more plug: I work at Glasskube, where we are building the missing Kubernetes package manager. If you are interested in our work, make sure to star us: glasskube/glasskube.

The pull request #3735 got accepted just 7 days after the released of our first technical preview of Glasskube.

We created a discussion thread in our GitHub repository explaining the necessary steps:

https://github.com/glasskube/glasskube/discussions/90

tldr: a pull request into our package repository

Glasskube is fully open-source. Support us by leaving a star: ⭐ glasskube/glasskube ⭐

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