Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Update deprecated api apiextensions.k8s.io/v1beta1

See original GitHub issue

/kind bug

What steps did you take and what happened: [A clear and concise description of what the bug is.] Update deprecated api group apiextensions.k8s.io/v1beta1 - code.

https://github.com/kubernetes/kubernetes/blob/master/CHANGELOG/CHANGELOG-1.16.md#deprecations-and-removals The apiextensions.k8s.io/v1beta1 version of CustomResourceDefinition is deprecated and will no longer be served in v1.19. Use apiextensions.k8s.io/v1 instead. (#79604, @liggitt)

The CustomResourceDefinition API type is promoted to apiextensions.k8s.io/v1 with the following changes:

Use of the new default feature in validation schemas is limited to v1

spec.scope is no longer defaulted to Namespaced and must be explicitly specified

spec.version is removed; use spec.versions instead

spec.validation is removed; use spec.versions[*].schema instead

spec.subresources is removed; use spec.versions[*].subresources instead

spec.additionalPrinterColumns is removed; use spec.versions[*].additionalPrinterColumns instead

spec.conversion.webhookClientConfig is moved to spec.conversion.webhook.clientConfig

spec.conversion.conversionReviewVersions is moved to spec.conversion.webhook.conversionReviewVersions

spec.versions[*].schema.openAPIV3Schema is now required when creating v1 CustomResourceDefinitions

spec.preserveUnknownFields: true is disallowed when creating v1 CustomResourceDefinitions; it must be specified within schema definitions as x-kubernetes-preserve-unknown-fields: true

In additionalPrinterColumns items, the JSONPath field was renamed to jsonPath (fixes https://github.com/kubernetes/kubernetes/issues/66531) The apiextensions.k8s.io/v1beta1 version of CustomResourceDefinition is deprecated and will no longer be served in v1.19.

What did you expect to happen:

Anything else you would like to add: [Miscellaneous information that will assist in solving the issue.]

Environment:

Kubeflow version (kfctl version):
Minikube version (minikube version):
Kubernetes version: (use kubectl version):
OS (e.g. from /etc/os-release):

Issue Analytics

State:
Created 3 years ago
Comments:8 (5 by maintainers)

Top GitHub Comments

1reaction

issue-label-bot[bot]commented, Oct 1, 2020

Issue-Label Bot is automatically applying the labels:

Label	Probability
area/katib	0.90

Please mark this comment with 👍 or 👎 to give our bot feedback! Links: app homepage, dashboard and code for this bot.

0reactions

gaocegegecommented, Mar 2, 2021

We have some problems with v1

Top Results From Across the Web

Deprecated API Migration Guide - Kubernetes

The apiextensions.k8s.io/v1beta1 API version of CustomResourceDefinition is no longer served as of v1.22. Migrate manifests and API clients ...

Kubernetes 1.22 deprecated APIs - Google Cloud

The Beta API version of CustomResourceDefinition is no longer served as of version 1.22. Migrate manifests and API clients to use the apiextensions.k8s.io/v1 ......

API deprecation in Kubernetes 1.22 that will impact your ...

The fastest check is to grep your codebase and metadata for all usage of “apiextensions.k8s.io/v1beta1” and verify the above APIs aren't ...

Will That Kubernetes v1.22 Upgrade Break My Application?

For example, the networking.k8s.io/v1beta1 API was deprecated in Kubernetes v1.19 and removed in Kubernetes v1.22; Its new stable ...

Update CRDs from v1beta1 - Certified Operator Build Guide

Update CRDs from v1beta1 ... Please refer to this blog post which also covers API deprecation and required ... apiVersion: apiextensions.k8s.io/v1beta1.