https://pulumi.com logo
#kubernetes
Title
# kubernetes
b

big-potato-91793

02/23/2024, 2:52 PM
Copy code
[id=something]
        [urn=urn:pulumi:nonprod9::apollo-client-deployment::something]
      ~ spec: {
          ~ source: "TyfwVfQp.mjs" => "vF9be9rS.mjs"
        }
error: Preview failed: 1 error occurred:
	* the Kubernetes API server reported that "something" 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
: Apply failed with 1 conflict: conflict with "node-fetch" using <http://component.tm1.tktm.io/v1beta1|component.tm1.tktm.io/v1beta1>: .spec.source
error: preview failed
Someone did modify the object with openlens in and now pulumi cannot do anything about it. Any idea what we are doing wrong? That’s kind of normal step for us.
d

dry-keyboard-94795

02/23/2024, 4:38 PM
The link in the error message is a good resource for resolving this. If it's normal for you to make manual modifications, the annotation approach is best
b

big-potato-91793

02/23/2024, 4:38 PM
Awesome 🙂
d

dry-keyboard-94795

02/23/2024, 4:38 PM
If you need manual modifications to persist, and not have pulumi overwrite, then you can use the
ignoreChanges
option too https://www.pulumi.com/docs/concepts/options/ignorechanges/
b

big-potato-91793

02/23/2024, 4:40 PM
Yeah this is manage by the same operator. Just they did the change in the openlens
Will go with the patch force annotation
That was a simple CR object that have 2 field in the spec. So we are not using like the
NamespacePatch
like the example
d

dry-keyboard-94795

02/23/2024, 4:44 PM
It works for standard resources too
b

big-potato-91793

02/23/2024, 4:44 PM
yeah that’s what I’m reading 😛
I guess it’s because we are using the pulumi k8s 4.x.x 🙂
d

dry-keyboard-94795

02/23/2024, 4:49 PM
Yes, SSA become the default for 4.x
3 Views