Monokle
sealed-secrets
Monokle | sealed-secrets | |
---|---|---|
47 | 71 | |
1,552 | 7,178 | |
3.8% | 1.6% | |
9.6 | 9.1 | |
about 1 month ago | 7 days ago | |
TypeScript | Go | |
MIT License | 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.
Monokle
-
Another YAML/Helm-Loving Monokle release
Download from GitHub - https://github.com/kubeshop/monokle
-
Generate Kubernetes resources using AI & explore Helm Charts with Monokle v2.2!
Thank you for your kind words Fluffer Wuffer! We always enjoy feature requests from the community. I’ve added a GitHub issue for NetworkPolicy Builder. Feel free to add more details.
-
What k8s related tool you wish you knew earlier?
Try out Monokle—a Kubernetes configuration tool that provides end-to-end visibility, templating, quick error detection, and simplified troubleshooting. It also has a cluster insights module that allows you to connect to your cluster, and see resources, logs, and terminals, along with other things.
-
[TechStory]: Migrating services and databases from an OpenShift (or K8s) cluster to another
monokle
-
Stupid question? Lens vs OpenLens vs Monokle
Monokle Desktop is an independent project created by Kubeshop, fully open source: https://monokle.io/
-
Monokle 2.1 - We love YAML so you don't have to
Hi! hm... we would have to look into that - please open an issue on our repo with additional details around workflows/problems that we should be solving for in this regard - https://github.com/kubeshop/monokle - thank you!
-
How to scan and control the K8 objects are being created against security threats?
Monokle is another viable option for doing this pre-deployment. It has OPA functionality integrated so you set up and configure additional policies to be checked earlier in your workflow. It also helps with other pre-deployment validation issues. The performance was a bit off for a while but seems they've been working on it as of late.
-
Solving Challenges of Kubernetes YAML Manifest using Monokle
Monokle is an open-source IDE for Kubernetes. You can import existing infrastructure code or start fresh with your configuration. Monokle comes as a standalone desktop app, CLI as well as a cloud offering.
-
How do you start your resource manifests?
I would recommend trying out Monokle because it’s a great tool for creating manifest files for Kubernetes. It offers several features that can help make the process of creating manifests much faster and easier.
-
Kubernetes cluster management with Monokle
We would love to have your input on all these things. We are actively talking to users to discuss use cases and problems that we can help to fix, and we are also establishing partnerships to make Monokle way more useful for your day to day work. You can contact us for a 30’ conversation or join our Discord channel, or you can directly open a new issue in GitHub to let us know what you think.
sealed-secrets
-
Introduction to the Kubernetes ecosystem
External-Secrets Operator : A Kubernetes operator that integrates external secret management systems like AWS Secrets Manager, HashiCorp Vault, Google Secrets Manager, and many more. The operator reads information from external APIs and automatically injects the values into a Kubernetes Secret (Alternatives : Vault, SOPS, Sealed Secrets)
-
Show HN: Open-source alternative to HashiCorp/IBM Vault
I like sealed secrets (https://github.com/bitnami-labs/sealed-secrets) a lot. It's like 1Password, but for apps in kubernetes. You only need to secure a private key, and can throw encrypted secrets in a public github repo or anywhere you want.
It's owned by VMware (Broadcom) now, so you have to decide which company you hate more.
-
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!.
-
Plain text Kubernetes secrets are fine
Yeah documentation is hard and I'm guilty (as a former maintainer of SealedSecrets)
SealedSecrets was designed with "write only" secrets in mind.
Turns out a lot of people need to access the current secrets because they need to update a part of a "composite" secret.
There are two kinds of "composite" secrets, one easy and one harder, but if you don't know how to do it, even the easier is hard:
1. Secret with multiple data "items" (also called keys in K8s Secret jargon but that's confusing when there is encryption involved). I.e. good old "data":{"foo": "....", "bar": "..."}
2. Secrets where data within one item is actually a config file with cleartext and secrets mixed up in one single string (usually some JSON or YAML or TOML)
Case 1 is "easy" to deal with once you realize that sealed secrets files are just text files and you can just manually merge and update encryoted data items. We even created a "merge" and some "raw" encryption APIs to make that process a little less "copy pasta" but it's still hard to have a good UX that works for everyone.
Case 2 is harder. We did implement a data templating feature that allows you to generate a config file via a go-template that keeps the cleartext parts in clear and uses templating directives to inject the secret parts where you want (referencing the encrypted the items)
The main problem with case 2 is that it's undocumented.
The feature landed in 2021:
https://github.com/bitnami-labs/sealed-secrets/pull/580
I noticed that people at my current $dayjob used sealed secrets for years and it took me a while to understand that the reason they hated it was that they didn't know about that fundamental feature.
And how to blame them!? It's still undocumented!
In my defense I spent so much effort before and after I left VMware to lobby so that the project got the necessary staffing so it wouldn't die of bitrot that I didn't have much time left to work on documentation. Which is a bit said and probably just an excuse :-)
That said, I'm happy that the project is alive and the current maintainers are taking care of it against the forces of entropy. Perhaps some doc work would be useful too. Unfortunately I don't have time for now.
- Storing secrets in distributed binaries?
-
Weekly: Questions and advice
This might be OT, and forgive me, but I think one of the best practices for Encrypting and Managing secrets in Kubernetes is to use Sealed Secrets, they allow your secrets to be securely stored in git with the rest of the configuration and yet no one with access to the Git repository will be able to read them. I say this might be OT, because Sealed Secrets are trying to mitigate a different threat, the threat of the secrets at rest somewhere, and not "live in the cluster", where in theory all the ingredients to decrypt the secrets would still live.
-
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
sealed-secrets (sealed)
What are some alternatives?
lens - Lens - The way the world runs Kubernetes
vault-secrets-operator - Create Kubernetes secrets from Vault for a secure GitOps based workflow.
k9s - 🐶 Kubernetes CLI To Manage Your Clusters In Style!
sops - Simple and flexible tool for managing secrets
octant - Highly extensible platform for developers to better understand the complexity of Kubernetes clusters.
Vault - A tool for secrets management, encryption as a service, and privileged access management
OpenLens - OpenLens Binary Build Repository
kubernetes-external-secrets - Integrate external secret management systems with Kubernetes
metalk8s - An opinionated Kubernetes distribution with a focus on long-term on-prem deployments
helm-secrets - A helm plugin that help manage secrets with Git workflow and store them anywhere
kubeapps - A web-based UI for deploying and managing applications in Kubernetes clusters
argocd-vault-plugin - An Argo CD plugin to retrieve secrets from Secret Management tools and inject them into Kubernetes secrets