Lens is a desktop application that provides a rich graphical interface for Kubernetes cluster management. Note that the open-source OpenLens project is no longer actively maintained; the current Lens product is developed and maintained by Mirantis. - Source: dev.to / 4 months ago

Lens Lens is an incredibly popular IDE for Kubernetes, offering a powerful graphical interface to interact with clusters. It simplifies the complexity of managing multiple clusters and provides tools for monitoring, logging, and troubleshooting. Site. - Source: dev.to / over 1 year ago

Thankfully, for whoever likes that approach, there are friendlier GUIs to help manage yours clusters and deployments. Rancher, developed by the same folks from K3s, is one of them, but honestly I've found too complicated to set up. In my previous job I came across an alternative that I consider much more practical: Lens. - Source: dev.to / almost 2 years ago

Lens is another Kubernetes management tool with a powerful visual interface. It's a desktop app that aims to offer an IDE-like Kubernetes experience. Lens's features include support for Helm charts, app templates, metrics monitoring across several engines, and seamless multi-cluster connectivity. You can also use Lens to control Kubernetes RBAC configs and invite team members to your clusters. - Source: dev.to / about 2 years ago

Generally I felt as if I was diving in the deepest of waters without the correct equipement and that was horrifying. Unfortunately to me, I had to dive even deeper before getting equiped with tools like ArgoCD, and k8slens. I had to start working with... HELM. - Source: dev.to / over 2 years ago

At StackGres [1] we find Timescale to be one of the most used extensions. Timescale is quite a successful project! StackGres is actually the first solution recommended by Timescale for self-hosting with Kubernetes operators [2]. So if you are into Kubernetes (or if not, consider it, using something like K3s [3] is quite straightforward and lightweight on resources), this is probably a great option to self-host... - Source: Hacker News / 19 days ago

* Latency. Yes, yes, yes, they add "microseconds" vs "milliseconds for queries", and that's true, but just part of the story. There's an extra hop. There's two extra sets of TCP layers being traversed. If the hop is local (say a sidecar, as we do in StackGres) it adds complexity in its deployment and management (something we solved by automation, but was an extra problem to solve) and consumes resources. If it's a... - Source: Hacker News / 5 months ago

This is conceptually similar to what we did for Postgres extensions at the StackGres [1] project. I gave a talk at a Kubecon about it [2]. However, this scheme is not perfect. Some Kubernetes security solutions enforce immutable containers, and once the agent pulls any additional file into the container, it will be flagged. It's also harder to reason about the security of the image (think CVEs, etc), given that... - Source: Hacker News / 11 months ago

I applaud the decision to use AGPL-3.0. For me, it's a license that provides forward guarantees to the Community: no proprietary forks can happen, so any fork will be an OSS fork from which the upstream project may benefit too, which benefits all users. That's the reason we chose this license for StackGres [1], another project in the Postgres space. [1]: https://stackgres.io. - Source: Hacker News / about 2 years ago

This is good and interesting recipe to get Keycloak and Postgres on Kubernetes. There is an important improvement, though: the Postgres deployed here is not production ready (high availability, backups, monitoring, etc). We run Keycloak on StackGres [1] which gives us production-ready Postgres setup (disclaimer: it's dogfooding). Happy to share the YAML manifests used to deploy Keycloak with StackGres. Maybe we... - Source: Hacker News / about 3 years ago