Closed timebertt closed 2 years ago
I propose to generate the example CRDs from the API types using controller-gen
on make generate
similar to make generate-extensions-crds
in g/g: https://github.com/gardener/gardener/blob/00859f107d55ca009f9f889f2c10993245f5411c/Makefile#L222-L225
Once we vendor a new g/g version including https://github.com/gardener/gardener/pull/4854, this repo can simply auto-generate all CRDs under example
, except the VPA CRD.
I'm not sure if that one is actually needed or could simply be removed.
/unassign for now, as @BeckerMax plans to revendor g/g in this extension. With that, https://github.com/gardener/gardener/pull/4854 can be reused to fix this issue.
How to categorize this issue?
/area dev-productivity /kind enhancement /platform aws
What would you like to be added:
Update CRDs under
example
toapiextensions.k8s.io/v1
, e.g. https://github.com/gardener/gardener-extension-provider-aws/blob/51d2a020b218c16d4dbc1f0a197c9a83bae9f48e/example/20-crd-backupbucket.yaml#L2-L3Why is this needed:
With k8s v1.22,
apiextensions.k8s.io/v1beta1
is no longer served: https://kubernetes.io/docs/reference/using-api/deprecation-guide/#customresourcedefinition-v122 We should update the example CRDs to allow developers to easily test against a v1.22 cluster.E.g. I hit the following when testing a PR: