Eureka
sealed-secrets
Our great sponsors
Eureka | sealed-secrets | |
---|---|---|
8 | 69 | |
12,183 | 7,045 | |
0.5% | 2.5% | |
6.2 | 9.2 | |
about 1 month ago | 8 days ago | |
Java | Go | |
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.
Eureka
- How Netflix Uses Java
-
Why using Eureka?
I was setting up microservices based on Netflix Eureka and experimenting on top of spring-cloud and after weeks of research and development the question rose!
-
[Feedback request] Fuddle service registry
The closest thing I've found is Netflix's Eureka, though its very Java oriented and I found hard to use.
-
Kubernetes Microservices on Azure with Cosmos DB
There's an open issue documenting this problem on Spring Cloud Netflix and Netflix Eureka.
-
Programming Microservices Communication With Istio
Service discovery — Traditionally provided by platforms like Netflix Eureka or Consul.
- Ask HN: What are the best the publicly available FAMANG code repos?
-
What Is a Service Mesh, and Why Is It Essential for Your Kubernetes Deployments?
With multiple services running, it’s hard to discover where they’re located. The dependencies between multiple services are not always easily found, and new services may be deployed with a new dependency on an older service. Those services can be deployed anywhere in the infrastructure, so what you need is a Service Discovery service. There are plenty available, such as Netflix Eureka or HashiCorp Consul.
sealed-secrets
-
Deploy Secure Spring Boot Microservices on Amazon EKS Using Terraform and Kubernetes
If you have noticed, you are setting secrets in plain text on the application-configmap.yml file, which is not ideal and is not a best practice for security. The best way to do this securely would be to use AWS Secrets Manager, an external service like HashiCorp Vault, or Sealed Secrets. To learn more about these methods see the blog post Shhhh... Kubernetes Secrets Are Not Really Secret!.
- Storing secrets in distributed binaries?
-
Want advice on planned evolution: k3os/Longhorn --> Talos/Ceph, plus Consul and Vault
The addition of Consul and Vault gives me a few things. For one, right now I'm handling secrets with a mixture of SOPS and Sealed Secrets. I use Vault in my professional life, and have used both Vault and Consul at my last job. Vault is a beast, so I may as well get better at it; plus its options for secret injection are better.
- Homebrew 4.0.0 release
-
How to Deploy and Scale Strapi on a Kubernetes Cluster 1/2
Use Sealed Secrets Operator.
-
Secret Management in Kubernetes: Approaches, Tools, and Best Practices
Considering the major limitations of using Kubernetes Secrets, there are many new approaches being developed by the Kubernetes community. Kubernetes SIGs like the Secrets Store CSI Driver and solutions like the external secrets operator that works with third-party secret managers, and options to seal secrets through tools like bitnami’s sealed-secrets. To skip the tools and move directly to best practices, click here.
sealed-secrets (sealed)
-
How do other securely manage their secrets?
We use sealed secrets controller - https://github.com/bitnami-labs/sealed-secrets
-
GitOps and Kubernetes – Secure Handling of Secrets
An option that easily works with GitOps is the Operator Sealed Secrets from Bitnami. Secrets encrypted with it can only be decrypted by operators running inside the cluster, not even by the original author. For encryption, there is a CLI (and a third-party web UI) that requires a connection to the cluster. The disadvantage of this is that the key material is stored in the cluster, the secrets are bound to the cluster and one has to take care of backups and operation.
What are some alternatives?
vault-secrets-operator - Create Kubernetes secrets from Vault for a secure GitOps based workflow.
sops - Simple and flexible tool for managing secrets
service-mesh-istio - A microservice project leveraging Service Mesh with advanced features from Istio
Vault - A tool for secrets management, encryption as a service, and privileged access management
kubernetes-external-secrets - Integrate external secret management systems with Kubernetes
consul - Consul is a distributed, highly available, and data center aware solution to connect and configure applications across dynamic, distributed infrastructure.
helm-secrets - A helm plugin that help manage secrets with Git workflow and store them anywhere
argocd-vault-plugin - An Argo CD plugin to retrieve secrets from Secret Management tools and inject them into Kubernetes secrets
kamus - An open source, git-ops, zero-trust secret encryption and decryption solution for Kubernetes applications
Apollo - Java libraries for writing composable microservices
kustomize-sops - KSOPS - A Flexible Kustomize Plugin for SOPS Encrypted Resources
external-secrets - External Secrets Operator reads information from a third-party service like AWS Secrets Manager and automatically injects the values as Kubernetes Secrets.