terraform-controller
webui
| terraform-controller | webui | |
|---|---|---|
| 1 | 3 | |
| 291 | 137 | |
| 0.0% | - | |
| 0.0 | 3.0 | |
| about 3 years ago | almost 2 years ago | |
| Go | TypeScript | |
| 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.
terraform-controller
-
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.
webui
-
GitOps using Flux and Flagger
There is no UI for Flux. It does have an experimental UI that is not in an active development state at the time of writing this.
-
Automation assistants: GitOps tools in comparison
This allows the developer to analyze their deployments and correct errors all without having to access the cluster. For authentication , there are interfaces for common protocols, such as LDAP and OIDC. Via configurable roles and groups, users can granted access the projects and applications for which they are responsible. The developers of Flux v2 are currently working on a web interface. However, it is still in an experimental state.
-
Deploying to different namespaces via Jenkins in k8s (and secrets mgmt)
That's what I said: "I'm a Flux guy." I agree that Flux v2 is much better than Flux v1. But setting up ArgoCD is a drag. With Flux, you just run the CLI command and everything is committed to the repo and deployed in the cluster. Flux is only missing the UI but I think that this will change soon (https://github.com/fluxcd/webui).
What are some alternatives?
argo-cd - Declarative Continuous Deployment for Kubernetes
Flux - Successor: https://github.com/fluxcd/flux2
sealed-secrets - A Kubernetes controller and tool for one-way encrypted Secrets
werf - A solution for implementing efficient and consistent software delivery to Kubernetes facilitating best practices.
kubernetes-external-secrets - Integrate external secret management systems with Kubernetes
cluster-api - Home for Cluster API, a subproject of sig-cluster-lifecycle
flagger - Progressive delivery Kubernetes operator (Canary, A/B Testing and Blue/Green deployments)
awx - AWX provides a web-based user interface, REST API, and task engine built on top of Ansible. It is one of the upstream projects for Red Hat Ansible Automation Platform.
flux2 - Open and extensible continuous delivery solution for Kubernetes. Powered by GitOps Toolkit.
kamus - An open source, git-ops, zero-trust secret encryption and decryption solution for Kubernetes applications