This message was deleted.

This message was deleted.

Hi All, I'm running into an issue with an apply conflict... I'm using ConfigFile to install knative serving via the yaml they provide. Once it's installed if I do I refresh, pulumi notices on of the resources dfined in the yaml has changed. I can't seem to ignore the change (how do I target a sub resource of ConfigFile?). If I try to use a transform, only the parent ConfigFile resource seems to get passed to the transform, so I still can't target the children. Any thoughts? Here's my error output:

Type                                                                                Name                                                                 Plan       Info
     pulumi:pulumi:Stack                                                                 infra-plane-k8s-dev                                                             1 error
     └─ centml:platform_k8s:knative                                                      dev-k8s-knative
        └─ kubernetes:yaml/v2:ConfigFile                                                 dev-k8s-knative-serving-core
 ~         ├─ kubernetes:<http://admissionregistration.k8s.io/v1:MutatingWebhookConfiguration|admissionregistration.k8s.io/v1:MutatingWebhookConfiguration>    dev-k8s-knative-serving-core:webhook.serving.knative.dev             update     [diff: ~webhooks]; 1 error
 ~         └─ kubernetes:<http://admissionregistration.k8s.io/v1:ValidatingWebhookConfiguration|admissionregistration.k8s.io/v1:ValidatingWebhookConfiguration>  dev-k8s-knative-serving-core:validation.webhook.serving.knative.dev  update     [diff: ~webhooks]; 1 error

Diagnostics:
  kubernetes:<http://admissionregistration.k8s.io/v1:MutatingWebhookConfiguration|admissionregistration.k8s.io/v1:MutatingWebhookConfiguration> (dev-k8s-knative-serving-core:webhook.serving.knative.dev):
    error: Preview failed: 1 error occurred:
    	* the Kubernetes API server reported that "webhook.serving.knative.dev" failed to fully initialize or become live: Server-Side Apply field conflict detected. See <https://www.pulumi.com/registry/packages/kubernetes/how-to-guides/managing-resources-with-server-side-apply/#handle-field-conflicts-on-existing-resources> for troubleshooting help.
    The resource managed by field manager "pulumi-kubernetes-7b887821" had an apply conflict: Apply failed with 1 conflict: conflict with "webhook" using <http://admissionregistration.k8s.io/v1|admissionregistration.k8s.io/v1>: .webhooks[name="webhook.serving.knative.dev"].rules

  pulumi:pulumi:Stack (infra-plane-k8s-dev):
    error: preview failed

  kubernetes:<http://admissionregistration.k8s.io/v1:ValidatingWebhookConfiguration|admissionregistration.k8s.io/v1:ValidatingWebhookConfiguration> (dev-k8s-knative-serving-core:validation.webhook.serving.knative.dev):
    error: Preview failed: 1 error occurred:
    	* the Kubernetes API server reported that "validation.webhook.serving.knative.dev" failed to fully initialize or become live: Server-Side Apply field conflict detected. See <https://www.pulumi.com/registry/packages/kubernetes/how-to-guides/managing-resources-with-server-side-apply/#handle-field-conflicts-on-existing-resources> for troubleshooting help.
    The resource managed by field manager "pulumi-kubernetes-da1dfa41" had an apply conflict: Apply failed with 1 conflict: conflict with "webhook" using <http://admissionregistration.k8s.io/v1|admissionregistration.k8s.io/v1>: .webhooks[name="validation.webhook.serving.knative.dev"].rules

This message was deleted.

This message was deleted.

This message was deleted.

This message was deleted.

Hello, I have a Pulumi project for managing my AWS Organization and SSO (IAM Identity Center). Everything was working perfectly two months ago. Before implementing new changes, I decided to run a

pulumi up

to ensure everything was still in order. However, during the preview, Pulumi is attempting to delete and recreate the Organization, and of course replace all my OUs and update all my Accounts. This behavior seems unusual, and I’m unable to understand why it’s happening. It's unclear why Pulumi wants to delete and recreate my organization. Could you help me troubleshoot this issue? Thank you in advance for your assistance!

Then, we would like to set up cross-account roles/permissions so that the pulumi dev backend state is saved in an S3 bucket in the root account, so that developers in the dev account can't accidentally alter the state. Any tips or resources are appreciated!

This message was deleted.