externalsecret-operator
terraform-k8s
externalsecret-operator | terraform-k8s | |
---|---|---|
1 | 5 | |
184 | 450 | |
- | 0.2% | |
8.2 | 4.9 | |
almost 3 years ago | 5 months 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.
externalsecret-operator
-
Automation assistants: GitOps tools in comparison
If you are using an external KMS in any case, then there are other options, such as the kubernetes-external-secrets operator that was originally started by GoDaddy and the externalsecret-operator from Container Solutions. If you use HashiCorp Vault, you also have the option of using the Vault Secrets operator. This works similarly to the Sealed Secrets Operator, but instead of managing its own key material, it retrieves the secrets from Vault. The CNCF Technology Radar from January 2021 provides an overview of the types of tools that are available for secrets management.
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?
opencspm - Open Cloud Security Posture Management Engine
argocd-operator - A Kubernetes operator for managing Argo CD clusters.
aad-pod-identity - [DEPRECATED] Assign Azure Active Directory Identities to Kubernetes applications.
cluster-api - Home for Cluster API, a subproject of sig-cluster-lifecycle
helm-secrets - A helm plugin that help manage secrets with Git workflow and store them anywhere
argo-rollouts - Progressive Delivery for Kubernetes
DevSecOps - Ultimate DevSecOps library
Flux - Successor: https://github.com/fluxcd/flux2
kubernetes-external-secrets - Integrate external secret management systems with Kubernetes
sops-secrets-operator - Kubernetes SOPS secrets operator
sealed-secrets - A Kubernetes controller and tool for one-way encrypted Secrets
flagger - Progressive delivery Kubernetes operator (Canary, A/B Testing and Blue/Green deployments)