override fields with SSA

I’m using SSA and I need to change a CR that had been created by GKE add-on manager.

Here is what I’m doing:

       let configConnectorConfigGroup: kube.yaml.ConfigGroup;

       configConnectorServiceAccount.email.apply(servicesAccountEmail => {
               const configConnector = {
                       apiVersion: "core.cnrm.cloud.google.com/v1beta1",
                       kind: "ConfigConnector",
                       metadata: { name: "configconnector.core.cnrm.cloud.google.com" },
                       spec: {
                           mode: "cluster", // GKE defaults to "namespaced" mode, which we need to override
                           googleServiceAccount: servicesAccountEmail,
                       },
               };

               configConnectorConfigGroup = new kube.yaml.ConfigGroup("configconnector", { yaml: yaml.stringify(configConnector), skipAwait: true }, kubeOpts);

       })

I am getting this error:

  kubernetes:core.cnrm.cloud.google.com/v1beta1:ConfigConnector (configconnector.core.cnrm.cloud.google.com):
    error: resource configconnector.core.cnrm.cloud.google.com was not successfully created by the Kubernetes API server : Apply failed with 1 conflict: conflict with "gke_addon_poststart" using core.cnrm.cloud.google.com/v1beta1: .spec.mode

I had a look at the code, but couldn’t find anything with regards to how one can override fields that are not managed by Pulumi, which is what I’d like to be able to do.

[errordeveloper]

@squaremo pulumi.com/patchForce: true worked, thanks a lot for your help!

[squaremo]

OK, that field is set explicitly by gke_addon_poststart – maybe putting the annotation pulumi.com/patchForce: true on the patch object will be enough to resolve that conflict.