GitOps, a methodology that uses Git as the single source of truth for all aspects of a system including application code and configurations, presents challenges for managing secrets. Although storing secrets in Git might seem counterintuitive to GitOps' principles, solutions exist to manage them securely. One approach involves using the Bitnami Sealed Secrets controller, which encrypts Kubernetes secrets for Git storage and decrypts them for application use without requiring code changes. This controller handles secrets by converting them into a format safe for Git, allowing their inclusion alongside other application configurations. It employs a tool called kubeseal to encrypt secrets using a cluster-specific public key, ensuring that secrets remain secure and specific to their intended environment. While incorporating sealed secrets into a GitOps workflow offers a way to manage secrets efficiently, it requires careful consideration of secret rotation and key handling, especially in production environments.