postgres-operator
tofu-controller
postgres-operator | tofu-controller | |
---|---|---|
6 | 14 | |
145 | 1,154 | |
2.1% | 3.3% | |
7.4 | 9.6 | |
about 2 months ago | 6 days ago | |
Go | Go | |
MIT License | 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.
postgres-operator
-
Jolt v0.5.2 is available!
I found a couple of those Postgres operators, like the movetokube/postgres-operator but I honestly can't tell which of them are any good. Do you have any experience with them? I also would need something for MinIO, since I'm able to use Terraform to create databases, buckets and then spin up the app. It's a really comfortable process albeit I do prefer GitOps.
-
My recently deployed media apps in ArgoCD, migrating from Terraform.
Not everything carries over from Terraform to GitOps but with that said check out this operator that lets you provision an existing postgres database.
-
Database for homelab - in or out of cluster?
On my list is the external postgres operator to provision databases on the external postgres instance, similar to using democratic-csi for providing volumes on the TrueNAS host. https://github.com/movetokube/postgres-operator
-
Is there an operator/controller for Kubernetes that allows me to create Postgres roles and databases with CRDs?
Others have mentioned some great operators for managing in-cluster postgres databases, but if you're looking to manage external or previously existing databases: https://github.com/movetokube/postgres-operator
-
If I set up a home K3s setup.. how often am I going to have to...
That is my plan, too. I have the External Postgres Server Operator on my list of thing to try out. Does anyone have experience with it already?
-
Operator to Replicate Kubernetes ImagePullSecrets to all namespaces
Here is an example of an operator that creates databases: https://github.com/movetokube/postgres-operator
tofu-controller
-
Self-service infrastructure as code
We stumbled upon a project for maintaining Terraform with CRDs that we could deploy with Helm. That project is now called Tofu-Controller - another WeaveWorks project, so it integrated great with our existing Flux setup.
-
Weaveworks Seems to Be Disintegrating
https://github.com/weaveworks/tf-controller/issues/1166#issu...
-
Disaster Recovery for AWS EKS Infra
Weave's TF-Controller, which also has fewer bugs, much better adoption, and it looks like it's actually being developed by someone. But requires a weird argocd <-> flux interop boilerplate. It's a "controller for flux" and not a Kubernetes controller, and I don't really get such ambiguous targeting , but meh...
-
Migrate from terragrunt to terraform
Wrt tools, I wanted to integrate terraform with Flux thanks to their tf-controller. Conciling the core gitops features with terraform would be great imho.
-
My recently deployed media apps in ArgoCD, migrating from Terraform.
I'm using Flux instead of Argo which has support for running terraform from a given Git Repo or OCI artifact so essentially I still fall back on Terraform when needed and it's applied via GitOps.
- Looking for teammate to join project (not a job posting)
-
MySQL operators without the cluster
tf-controller which is integrated with Flux GitOps and reconciles Terraform files in a control loop
-
Automate your Terraform using GitOps with Flux
While searching for alternatives for running Terraform using Kubernetes, I found several controllers and operators, but none that I felt had as much potential as the tf-controller from Weaveworks. We are already using Flux as our GitOps tool, and the tf-controller works by utilizing some of the core functionality from Flux, and has a custom resource for Terraform deployments. The source controller takes care of fetching our modules, the kustomize controllers apply the Terraform resources, and then the controller spin up static pods (called runners) that runs your Terraform commands.
-
2022 was a great year for GitOps
For us, GitOps is a vital part of how we operate, and it is the magic sauce that fuels our platform offering. Not only do we use it for application deployments, but by utilizing the Weaveworks tf-controller, we can create services using Terraform to automate our infrastructure deployments.
-
Terraform to deploy and KEDA to scale - will it work?
Some further research brought me to Weaveworks' TF-Controller which appears to be able to do what I want at least for the initial deployment step. Flux CD (also by Weaveworks) integrates with KEDA now, so it would be great if it could also integrate with KEDA to manage terraform-deployed Azure resources.
What are some alternatives?
argocd-operator - A Kubernetes operator for managing Argo CD clusters.
crossplane - The Cloud Native Control Plane
pull-secret-operator - Copy pull secrets from one namespace into one or more other namespaces
atlantis - Terraform Pull Request Automation
postgres-operator - Production PostgreSQL for Kubernetes, from high availability Postgres clusters to full-scale database-as-a-service.
helm-operator - Successor: https://github.com/fluxcd/helm-controller — The Flux Helm Operator, once upon a time a solution for declarative Helming.
sandbox-cluster - Manifests and documentation for Code for Philly's live civic cloud cluster
jsonnet-controller - A fluxcd controller for managing manifests declared in jsonnet
postgres-operator - Postgres operator creates and manages PostgreSQL clusters running in Kubernetes
documents - 📑 Lasting documents from the GitOps Working Group which are versioned and released together (including the GitOps Principles and Glossary)
wireguard-operator - Painless deployment of wireguard on kubernetes
flux2 - Open and extensible continuous delivery solution for Kubernetes. Powered by GitOps Toolkit.