# Updating to 1.12.0 Fails To Reconcile in Flux

**URL:** <https://forums.percona.com/t/updating-to-1-12-0-fails-to-reconcile-in-flux/15598>\
**Category:** Percona Operator for MongoDB\
**Created:** [May 9, 2022, 12:55am UTC](https://forums.percona.com/t/updating-to-1-12-0-fails-to-reconcile-in-flux/15598 "2022-05-09T00:55:05Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Mike\_Krieger](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/mike_krieger/32/6517_2.png) [@Mike\_Krieger](https://forums.percona.com/u/Mike_Krieger)\
**Post date:** [May 9, 2022, 12:55am UTC](https://forums.percona.com/t/updating-to-1-12-0-fails-to-reconcile-in-flux/15598/1 "2022-05-09T00:55:05Z")

</div>

Hi,

We use flux to apply our K8s configs to our cluster. We’re unable to upgrade from 1.11 to 1.12, however, since it fails with the following error:

```auto
CustomResourceDefinition/perconaservermongodbs.psmdb.percona.com dry-run failed, reason: Invalid, error: CustomResourceDefinition.apiextensions.k8s.io "perconaservermongodbs.psmdb.percona.com" is invalid: spec.preserveUnknownFields: Invalid value: true: must be false in order to use defaults in the schema

```

Has anyone else hit this? 1.11 works just fine so it must be something in the new `crd.yaml` definitions that we applied, but unfortunately the error doesn’t tell us which fields are missing.

---

<div class="post-metadata">

**Author:** ![Sergey\_Pronin](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/sergey_pronin/32/14887_2.png) [@Sergey\_Pronin](https://forums.percona.com/u/Sergey_Pronin)\
**Post date:** [May 9, 2022, 9:14am UTC](https://forums.percona.com/t/updating-to-1-12-0-fails-to-reconcile-in-flux/15598/2 "2022-05-09T09:14:05Z")

</div>

Hey Mike,

which k8s version and flavor are you using?

For example starting with k8s 1.22 there are some changes in APIs. Like CustomResourceDefinition is no longer `v1beta1`, but just `v1`.

And in some k8s flavors I see the note:

```auto
spec.preserveUnknownFields: true is disallowed when creating v1 CustomResourceDe.finition objects; it must be specified within schema definitions as x-kubernetespreserve-unknown-fields: true.

```

Could you please try to set all occurrences of `x-kubernetes-preserve-unknown-fields:` to `false` in `crd.yaml`?

Also we migrated to OpenAPI schema starting with 1.12, so it might be related. Please let me know how it goes.