CI CasC integration with Secrets Manager (PRT071)
summary
Live demo shows CloudBees CI controllers on Amazon EKS pulling credentials from AWS Secrets Manager at runtime using Secrets Store CSI Driver and IAM roles for service accounts. Helm deploys CloudBees and the AWS CSI provider, GitHub App triggers a CasC bundle to create a new controller, and an IAM policy with KMS decrypt permission allows Secrets Manager secrets to mount into the JCasC volume. The dynamic provisioning completes and the secrets are verifiably present on the new controller.
AI-written summary · about
chapters (8)
- 0:00Introduction to CloudBees CI
- 1:25What is Configuration as Code
- 4:18Demo setup and architecture overview
- 6:31IAM and Secrets Manager integration
- 8:39GitHub app and dynamic provisioning
- 10:04JCasC bundle and secrets management
- 12:34Verifying secrets in new controller
- 13:40Operation Center and summary
related talks
30mLook Ma, No secrets in my Kubernetes Cluster! - Vijay Dharap
55mHandling secrets in cloud-based applications
36mSecrets Store CSI Driver-Bring Your Own Enterprise Secrets Store to K8s
20mApplication Secret Management with AWS KMS
24mSecrets Store CSI Driver: Keeping Secrets Secret
41mSIG AWS Update - Justin Santa Barbara
24mCan You Keep a Secret? On Secret Management in Kubernetes
39mControlled Mayhem With Cloud Native Security Pipelines
