This message was deleted.

sparse-intern-71089

04/25/2022, 4:00 PM

This message was deleted.

quiet-wolf-18467

04/25/2022, 4:38 PM

The Operator provides a GitOps approach to CD

quiet-wolf-18467

04/25/2022, 4:39 PM

Which has 2 main values: 1. Continuous reconciliation and draft repair 2. Inverted control loop - you don’t need to ship credentials to other systems to deploy your apps

damp-honey-93158

04/25/2022, 5:46 PM

Thanks - the other related question would be whether or not the operator is missing anything when compared to a CI/CD flow implemented via something like Flux v2

thankful-thailand-33082

04/25/2022, 6:40 PM

Flux Documentation Flux is a tool for keeping Kubernetes clusters in sync with sources of configuration (like Git repositories), and automating updates to configuration when there is new code to deploy. Unless you are using something like Crossplane to deploy your Infrastructure, you cannot really compare flux to pulumi. Flux and ArgoCD are operators that sync CRDs from git repos into a cluster. Pulumi creates the cluster.

quiet-wolf-18467

04/26/2022, 11:59 AM

One can compare Flux to Pulumi because we have the Pulumi Operator

quiet-wolf-18467

04/26/2022, 11:59 AM

The benefits of the Pulumi Operator over Flux are that our CD pipelines can become “environment aware”, something that Flux really struggles with.

👍 1

2 Views

Open in Slack

Previous Next

Pulumi Community

No matter how you like to participate in developer communities, Pulumi wants to meet you there. If you want to meet other Pulumi users to share use-cases and best practices, contribute code or documentation, see us at an event, or just tell a story about something cool you did with Pulumi, you are part of our community.