db-operator
egressip-ipam-operator
Our great sponsors
| db-operator | egressip-ipam-operator | |
|---|---|---|
| 3 | 1 | |
| 154 | 33 | |
| 0.6% | - | |
| 0.7 | 3.8 | |
| 2 months ago | 14 days ago | |
| Go | Go | |
| Apache License 2.0 | Apache License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
db-operator
-
Database for homelab - in or out of cluster?
For homelab, I'm using in-cluster databases. And I'm doing full volumes backups instead of database dumps. I have funkwhale and gitea that both require postgres. And I'm using postgres that is provided as chart dependency. But my plan is to setup one postgres database in the separate ns, and then use https://github.com/kloeckner-i/db-operator for managing it.
-
MySQL operators without the cluster
Look at https://github.com/kloeckner-i/db-operator , byt external secret is missing
- Operators for out-of-cluster databases
egressip-ipam-operator
-
Timeouts when default router pod is on the same node as a pod that is calling another route in OpenShift cluster - behind Azure load balancer
HOWEVER, when we use EgressIPs (https://github.com/redhat-cop/egressip-ipam-operator) for our customers running on it, the pods have very different behavior. The pods can no longer hit the ingress VIP (LB) and just time out, but they can hit the API (LB) and some things allowed by the NSG. I've confirmed the pods using EgressIPs do leave the node that has the EgressIP assigned and can hit the nodes running the routers just fine (targeting port and spoofing DNS as seen in access logs).
What are some alternatives?
nifikop - The NiFiKop NiFi Kubernetes operator makes it easy to run Apache NiFi on Kubernetes. Apache NiFI is a free, open-source solution that support powerful and scalable directed graphs of data routing, transformation, and system mediation logic.
keepalived-operator - An operator to manage VIPs backed by keepalived
varnish-operator - Run and manage Varnish clusters on Kubernetes
patch-operator - An operator to apply patches to Kubernetes objects in a declarative way.
tor-controller - Tor toolkit for Kubernetes (Tor instances, onion services and more)
github-actions-runner-operator - K8S operator for scheduling github actions runner pods
cloud-on-k8s - Elastic Cloud on Kubernetes
mysql-operator - Kubernetes operator to manage mysql databases and users
postgres-operator - Production PostgreSQL for Kubernetes, from high availability Postgres clusters to full-scale database-as-a-service.
chart-operator - Deploys Helm charts in Kubernetes workload clusters
argocd-operator - A Kubernetes operator for managing Argo CD clusters.