Popcorn Time!

• Raise your hand in Zoom reactions to share your answer
• After you speak, pick the next raised hand to speak

Q1: Some of you are already using Argo CD. What does your setup and infra look like for Argo CD today? cluster or multi-cluster? self-service or PR-gates? Do you give dev’s access to the Web UI? Do you lock them to read-only?

Next question:

Q2: For everyone: What design decisions do you think you’ll implement? Will you implement self-service or are PR-gates enough?

The Argo CD init problem: Cluster bootstrapping

• Argo CD can be complex to setup manually (TLS certs, admin password, user accounts, GIT_TOKEN, etc)
• The argocd CLI tool makes it easier, but it’s not declarative
• The (eventual) goal is to have a fully-declarative Argo CD setup
• Being able to recreate Argo CD with a simple kubectl apply is powerful! (no backups needed)