operator
tofu-controller
operator | tofu-controller | |
---|---|---|
5 | 14 | |
1,096 | 1,154 | |
1.7% | 3.3% | |
9.4 | 9.6 | |
4 days ago | 6 days ago | |
Go | Go | |
GNU Affero General Public License v3.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.
operator
-
My recently deployed media apps in ArgoCD, migrating from Terraform.
minio has a k8 operator as well which I use at work: https://github.com/minio/operator
- Using Minio operator in AKS cluster. Minio tenants stuck in "Waiting for pod get ready" even though the pods are ready. What to do? Solution on git issues not helping :(
-
Need help adding TLS certificates to a tenant in a k3s cluster
So far I have seen some minio documentation (1, 2, ) about how to add the certificates correctly but I haven't been able to set it up correctly :-(
-
I'm slightly struggling to understand MinIO concepts
Yesterday, I tried to install MinIO, as I'm looking for a distributed object storage solution for Spark jobs on Kubernetes. I read the docs, went to the Github repo and followed the steps to install it using Helm. Here's what I did :
-
Monitor Minio with Prometheus on Kubernetes
Thank you! I assume you refer to this operator here, am I right? I will have a look at this, and also at the annotations possibility. Another question: is it deliberate that no Helm install is available?
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?
longhorn - Cloud-Native distributed storage built on and for Kubernetes
crossplane - The Cloud Native Control Plane
postgres-operator - PostgreSQL operator for Kubernetes
atlantis - Terraform Pull Request Automation
certgen - A dead simple tool to generate self signed certificates for MinIO TLS deployments
helm-operator - Successor: https://github.com/fluxcd/helm-controller — The Flux Helm Operator, once upon a time a solution for declarative Helming.
metallb - A network load-balancer implementation for Kubernetes using standard routing protocols
jsonnet-controller - A fluxcd controller for managing manifests declared in jsonnet
home-ops - Wife approved HomeOps driven by Kubernetes and GitOps using Flux
documents - 📑 Lasting documents from the GitOps Working Group which are versioned and released together (including the GitOps Principles and Glossary)
cluster-template - A template for deploying a Kubernetes cluster with k3s or Talos
flux2 - Open and extensible continuous delivery solution for Kubernetes. Powered by GitOps Toolkit.