gitops-playground
terraform-k8s
Our great sponsors
gitops-playground | terraform-k8s | |
---|---|---|
1 | 5 | |
165 | 450 | |
4.8% | 1.1% | |
9.4 | 4.9 | |
3 days ago | 5 months ago | |
Groovy | Go | |
GNU General Public License v3.0 or later | Mozilla Public 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.
gitops-playground
-
Automation assistants: GitOps tools in comparison
Flux has certain little features that ArgoCD doesn't have, such as support for SOPS and automatic updates for new image versions. However, the latter is the reasons that Flux v2 has not yet appeared in a stable version. It could be difficult to opt for a product with a version number 0.x when it is the central component in the supply chain. However, we do expect the release of a stable version here soon. One possibility to see ArgoCD and Flux v2 in action and compare their features is the GitOps Playground project that was started by the authors.
terraform-k8s
-
Terraform Cloud Operator in Production - Secrets
Is anyone here using the Terraform Cloud Operator in production? If so, how are you managing workspace secrets?
-
Terraform Cloud Operator giving not found error
So I’m using the terraform cloud operator for kubernetes (https://github.com/hashicorp/terraform-k8s) to create workspaces from an EKS cluster. I’ve had to use a forked helm chart. However, the issue I have right now is that when I create a workspace via the CRD, it creates on Terraform cloud and then is just stuck. Doesn’t try to apply the module, plan, apply etc. The logs of the operator pod talks about not being able to find the workspace.
-
GitOps using the Terraform Cloud Operator for Kubernetes
Did anyone try https://github.com/hashicorp/terraform-k8s for applying GitOps principles to IaC?
-
Automation assistants: GitOps tools in comparison
In addition to creating Kubernetes clusters, there is also an increasing number of opportunities to use various Infrastructure-as-Code (IaC) tools, such as Terraform, with GitOps. As was already mentioned, PipeCD offers support for Terraform. Terraform's vendor, HashiCorp, now also offers an official Terraform Kubernetes operator. However, it needs access to HashiCorp's Terraform Cloud. Alternatively, there are also third-party operators that can function without Terraform Cloud, such as the one developed by Rancher. However, it is still in alpha stage.
-
Etok: execute terraform on kubernetes
Pretty neat. I really want to test it out, and see how it compares to https://github.com/hashicorp/terraform-k8s and https://github.com/rancher/terraform-controller
What are some alternatives?
truecharts - Community App Catalog for TrueNAS SCALE [Moved to: https://github.com/truecharts/charts]
argocd-operator - A Kubernetes operator for managing Argo CD clusters.
cluster-api - Home for Cluster API, a subproject of sig-cluster-lifecycle
terraform-controller - Use K8s to Run Terraform
argo-rollouts - Progressive Delivery for Kubernetes
argo-cd - Declarative Continuous Deployment for Kubernetes
Flux - Successor: https://github.com/fluxcd/flux2
flux2-kustomize-helm-example - A GitOps workflow example for multi-env deployments with Flux, Kustomize and Helm.
sops-secrets-operator - Kubernetes SOPS secrets operator
atlantis - Terraform Pull Request Automation
flagger - Progressive delivery Kubernetes operator (Canary, A/B Testing and Blue/Green deployments)