You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Convert CRDs from v1beta1 to v1 API version, and document the unknown field preservation for Kopf's status storage.
Description
Kubernetes 1.16 introduced new changes to custom and built-in resources with stricter schemas and no possibility for arbitrary field storage by default:
There are workarounds though — via x-kubernetes-preserve-unknown-fields: true.
This PR documents these workarounds and upgrades the framework's CRDs to v1. Legacy CRDs for Kubernetes <= 1.15 are stored nearby (useful when starting in e.g. GKE with default K8s 1.14 and maximum 1.15).
The CRD definition is the only difference. The framework is supposed to work with both versions of CRDs. And the new annotations storage (#331) should solve the root problem "properly" via the code.
What do these changes do?
Convert CRDs from v1beta1 to v1 API version, and document the unknown field preservation for Kopf's status storage.
Description
Kubernetes 1.16 introduced new changes to custom and built-in resources with stricter schemas and no possibility for arbitrary field storage by default:
There are workarounds though — via
x-kubernetes-preserve-unknown-fields: true
.This PR documents these workarounds and upgrades the framework's CRDs to v1. Legacy CRDs for Kubernetes <= 1.15 are stored nearby (useful when starting in e.g. GKE with default K8s 1.14 and maximum 1.15).
The CRD definition is the only difference. The framework is supposed to work with both versions of CRDs. And the new annotations storage (#331) should solve the root problem "properly" via the code.
Issues/PRs
Type of changes
Checklist
The text was updated successfully, but these errors were encountered: