Skip to content

CRD Issue when migrating from SCB 2.X to 3.X: "spec.preserveUnknownFields: Invalid value" #788

@malexmave

Description

@malexmave

🐞 Bug report

When upgrading from SCB 2.X to 3.X, upgrading the CRDs results in an error:

The CustomResourceDefinition "scans.execution.securecodebox.io" is invalid: spec.preserveUnknownFields: Invalid value: true: must be false in order to use defaults in the schema

This is related to an upgrade in the APIs. To resolve it, you need to add preserveUnknownFields: false under the spec heading of the CRD YAMLs. We could not get this to work automatically, so we're documenting it here since not a lot of people should be taking this upgrade path anyway these days. It should be enough to do it once, all future imports should work as expected.

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions