argocd-operator
terraform-k8s
| argocd-operator | terraform-k8s | |
|---|---|---|
| 5 | 5 | |
| 664 | 453 | |
| 2.7% | - | |
| 9.0 | 2.9 | |
| 3 days ago | 20 days ago | |
| Go | Go | |
| Apache License 2.0 | 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.
argocd-operator
- Argo CD in the operator store version 0.2.0? While v2.2.5 is available?
-
ArgoCD install on openshift
The deploy folder is in the releases. So if you're installing 0.0.5, you'd go to https://github.com/argoproj-labs/argocd-operator/tree/v0.0.15/deploy
-
Automation assistants: GitOps tools in comparison
Another installation variant is the additional ArgoCD operator. This allows the actual ArgoCD components to be installed and configured via CRD. It is not documented how you can configure ArgoCD yourself via GitOps. This is conceivable, for example, using the ArgoCD operator. It remains to be determined whether this will work reliably and, above all, whether it supports continued operation via GitOps in the event of an error.
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?
fleet - Deploy workloads from Git to large fleets of Kubernetes clusters
cluster-api - Home for Cluster API, a subproject of sig-cluster-lifecycle
Flux - Successor: https://github.com/fluxcd/flux2
argo-rollouts - Progressive Delivery for Kubernetes
helm-secrets - A helm plugin that help manage secrets with Git workflow and store them anywhere
sops-secrets-operator - Kubernetes SOPS secrets operator
nifikop - The NiFiKop NiFi Kubernetes operator makes it easy to run Apache NiFi on Kubernetes. Apache NiFI is a free, open-source solution that support powerful and scalable directed graphs of data routing, transformation, and system mediation logic.
flagger - Progressive delivery Kubernetes operator (Canary, A/B Testing and Blue/Green deployments)
helmify - Creates Helm chart from Kubernetes yaml
postgres-operator - Postgres operator for Kubernetes
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.