Hi all. Question up top - can anyone help me under...
# kubernetes
a
Hi all. Question up top - can anyone help me understand why, when I run the
Up
method on a stack object (using the automation API), the Kubernetes provider (4.18.3) sends a PATCH request with no changes to the Kubernetes API? This has come up because: • We use Gatekeeper to enforce labels on resources • We've updated that constraint, so we're expecting different label values • Teams are trying to use the Pulumi automation API to deploy their resources with corrected labels • The resources are being rejected for including the old values that are currently deployed I've grabbed the admission review object as Gatekeeper receives it, and what I've found is that the first thing it receives is this patch request that just contains the current state of the resource, with no changes. The only option I'm passing to
Up
currently is
optup.ProgressStreams
, in case that's relevant. Just hoping someone can point me in the right direction before I go digging.