Kind — recommended. Creates a cluster using kind. Requires the containerd image store. Locally built images must be explicitly loaded into the cluster with kind load docker-image before Kubernetes can use them. - Source: dev.to / 26 days ago

What we need is a way to bootstrap a Kubernetes Cluster itself. Being in a docker-like environment the best option is a Kubernetes in Docker solution, Such as KinD or K3s. Both are available in Daggerverse and can be installed as external module to be reused. - Source: dev.to / about 2 months ago

# .github/workflows/test.yml Name: Testes de integração On: [push, pull_request] Jobs: test: runs-on: ubuntu-latest steps: - uses: actions/checkout@v4 - name: Instalar kind e kubectl run: | curl -Lo ./kind https://kind.sigs.k8s.io/dl/v0.23.0/kind-linux-amd64 chmod +x ./kind && sudo mv ./kind /usr/local/bin/kind curl -LO... - Source: dev.to / 3 months ago

Before landing on the base image approach, my first assumption was that the Kubernetes cluster setup was the bottleneck - we use kind to run dependencies like PostgreSQL and NATS. I replaced kind with k3s. It saved 1–2 minutes, but nothing significant on its own. - Source: dev.to / 3 months ago

> kind create cluster Creating cluster "kind" ... ✓ Ensuring node image (kindest/node:v1.35.0) 🖼 ✓ Preparing nodes 📦 ✓ Writing configuration 📜 ✓ Starting control-plane 🕹️ ✓ Installing CNI 🔌 ✓ Installing StorageClass 💾 Set kubectl context to "kind-kind" You can now use your cluster with: Kubectl cluster-info --context kind-kind Not sure what to do next? 😅 Check out... - Source: dev.to / 5 months 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