tofu-controller
bootstrap-repo
tofu-controller | bootstrap-repo | |
---|---|---|
14 | 7 | |
1,154 | 18 | |
3.3% | - | |
9.6 | 8.8 | |
6 days ago | 10 days ago | |
Go | Shell | |
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.
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.
bootstrap-repo
- Running certbot on nginx pod behind ingress nginx - 308 madness
- If you treat your cluster as ephemeral, how do you re-attach PVs and PVCs to your persistent storage?
-
Need help understanding ingress without reverse proxy or metallb.
So why am I telling you all this? Because this is how I point Kubernetes ingresses at apps which live outside the clusters. It's not entirely clear that is what you wanted, but hope this helps. I have more examples, there's a bit more to what I'm doing, since at the bottom line what I wanted was to use my one public IP address to manage more than one service. So that's where Traefik comes in, https://github.com/kingdonb/bootstrap-repo/blob/main/apps/routers/urbit-ships/socryx-topled-ingressroute.yaml
- Practical resources to learn GitOps
-
Does anyone know of a way to "save" and/or "load" cert-manager issued certs to s3 so they aren't constantly re-issued when a cluster is destroyed and rebuilt?
I save them to git, and restore them using GitOps. https://github.com/kingdonb/bootstrap-repo
- kingdonb/bootstrap-repo
-
Question for declarative GitOps managed shops
Using Helm via GitOps, you can pass in ridiculous collections of values that you would never use on the command line, mixing in secrets from secret sources, here is a complicated example (and here is a simpler one that doesn't do any patching.) Hope this helps. Usually when I show people Helm Controller, the reaction I get is "that's exactly what I wanted."
What are some alternatives?
crossplane - The Cloud Native Control Plane
csh-flux
atlantis - Terraform Pull Request Automation
documents - 📑 Lasting documents from the GitOps Working Group which are versioned and released together (including the GitOps Principles and Glossary)
helm-operator - Successor: https://github.com/fluxcd/helm-controller — The Flux Helm Operator, once upon a time a solution for declarative Helming.
tailscale-k8s - Configuration Repo for Tailscale on Kubernetes (on kind-kind)
jsonnet-controller - A fluxcd controller for managing manifests declared in jsonnet
flux2 - Open and extensible continuous delivery solution for Kubernetes. Powered by GitOps Toolkit.
cluster-template - A template for deploying a Kubernetes cluster with k3s or Talos