Eron Wright

Also, ArgoCD has various "diff" strategies, including "server-side dry-run": https://argo-cd.readthedocs.io/en/stable/user-guide/diff-strategies/

I believe that this feature would depend on running the deployment in a separate pod: https://github.com/pulumi/pulumi-kubernetes-operator/issues/78

Good news everyone, we just release a preview of Pulumi Kubernetes Operator v2. This new release has a whole-new architecture that uses pods as the execution environment, and each stack...

Related: https://github.com/kubernetes-sigs/kubebuilder/issues/1231

I was thinking that we would avoid duplication of their core parsing logic by having our tools consume the "code model" that is produced by autorest - the intermediate data...

Why exactly should the aliases be removed? Is a jump directly from 1.x to 3.x not supported? Thanks.

Thanks @shashiranjan84 for the repro instructions, we've added this to our backlog.

Regarding (2), a new option to consider is the "DefaultAzureCredential" mode, which is a uniform way to configure the provider across those environments.

I wonder how replacement would combine with skipAwait on delete and with SSA. Would the Apply call performed by the replacement be racing against finalization of the original?

Good news everyone, we just release a preview of Pulumi Kubernetes Operator v2. This new release has a new design for the logic of when to "re-sync" the stack (that...