Skip to content

Remove link to non-existent blog post #355

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
ricoberger merged 1 commit into from
Apr 18, 2026
+1 −4
Merged

Remove link to non-existent blog post #355

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 1 addition & 4 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -9,10 +9,7 @@ Create Kubernetes secrets from Vault for a secure GitOps based workflow.

The **Vault Secrets Operator** creates Kubernetes secrets from Vault. The idea
behind the Vault Secrets Operator is to manage secrets in Kubernetes cluster
using a secure GitOps based workflow. For more information about a secure GitOps
based workflow I recommend the article
["Managing Secrets in Kubernetes"](https://www.weave.works/blog/managing-secrets-in-kubernetes)
from [Weaveworks](https://www.weave.works). With the help of the Vault Secrets
using a secure GitOps based workflow. With the help of the Vault Secrets
Operator you can commit your secrets to your git repository using a custom
resource. If you apply these secrets to your Kubernetes cluster the Operator
will lookup the real secret in Vault and creates the corresponding Kubernetes
Expand Down