Kubernetes teams struggle to deploy dependent resources in order
Platform teams and Kubernetes developers need applications, add-ons, charts, and custom resources to be ready before dependent resources are deployed. The signals describe gaps across Argo CD, Helm, and Terraform: retries may not catch prerequisites that silently succeeded too early, and users want more flexible ordering within applications and charts. Today, some work around these gaps by manually syncing deployments or splitting resources and charts, which adds operational effort and makes applications harder to manage together.
For kubernetes platform teams and application developers. Mentioned from Jul 2020 to Apr 2022 on GitHub.
3 different people described this problem in 3 separate discussions.
- Indie fit
- 6.0/10
- Pain
- 6.8/10
- Frequency
- 5.0/10
- Willingness to pay
- 0.0/10
- Momentum
- 5.0/10
- Who pays
- Businesses
- Competition
- High
- Build difficulty
- Medium
What people said
Quoted word for word. Follow a link to read the whole discussion.
I want to sync them all at the same time and don't want to think about clicking sync in some correct order
Yes, what I now realize is that retries don't help because in the problematic scenario (mutating webhooks), nothing actually
See what to build and who will buy it
- 2 product ideas with the smallest useful version and pricing
- 4 places to find your first customers
- 3 more quotes from people who have this problem
- Current workarounds, existing solutions and risks