Sealed secrets for Kubernetes - enabling GitOps for secrets

Sealed Secrets provides declarative Kubernetes Secret Management in a secure way. Since the Sealed Secrets are encrypted, they can be safely stored in a code repository. This enables an easy to implement GitOps flow that is very popular among the OSS community.
In this video I discuss
- Introduction to sealed secrets
- Installation
- Demo with simple sealed secret creation
- Using sealed secrets in GitOps workflow using ArgoCD
Thanks to Org members
Cisco, Komodor, Sysdig and slim.ai
Want to become org member or video collaborations ? Email me [e-mail] or DM on Twitter works fine too.
►►►Connect with me ►►►
► Kubesimplify: kubesimplify.com/newsletter
► Newsletter: saiyampathak.com/newsletter
► Discord: saiyampathak.com/discord
► Twitch: saiyampathak.com/twitch
► KZbin: saiyampathak.com/youtube.com
► GitHub: github.com/saiyam1814
► LinkedIn: / saiyampathak
► Website: / saiyampathak
► Instagram: / saiyampathak
► / saiyampathak

[@tamilselvan8343]

Excellent

[@UtkarshMishra-it4oc]

What if I am provisioning a cluster and I want a secret in that cluster? Since the cluster itself is created by me I cannot use kubeseal in that cluster to create the sealed secrets manifest. How do I automate this flow?

[@rohanrustagi7857]

Thank you 😊

[@rdr6858]

👍

[@saloninarang1040]

👍🏻