Skip to content
This repository has been archived by the owner on Apr 25, 2023. It is now read-only.

Transition from apiextensions.k8s.io/v1beta1 to apiextensions.k8s.io/v1 #1296

Closed
makkes opened this issue Oct 12, 2020 · 0 comments · Fixed by #1297
Closed

Transition from apiextensions.k8s.io/v1beta1 to apiextensions.k8s.io/v1 #1296

makkes opened this issue Oct 12, 2020 · 0 comments · Fixed by #1297
Labels
kind/bug Categorizes issue or PR as related to a bug.

Comments

@makkes
Copy link
Contributor

makkes commented Oct 12, 2020

What happened:
When installing the Kubefed CRDs into a cluster, the API server will issue a warning:

Warning: apiextensions.k8s.io/v1beta1 CustomResourceDefinition is deprecated in v1.16+, unavailable in v1.22+; use apiextensions.k8s.io/v1 CustomResourceDefinition

What you expected to happen:
No warnings

How to reproduce it (as minimally and precisely as possible):

kubectl create -f charts/kubefed/crds/crds.yaml

Anything else we need to know?:

Environment:

  • Kubernetes version (use kubectl version): 1.19.1
  • KubeFed version: master
  • Scope of installation (namespaced or cluster)
  • Others

/kind bug
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
kind/bug Categorizes issue or PR as related to a bug.
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Transition CRDs from v1beta1 to v1 makkes/kubefed
2 participants
@makkes @k8s-ci-robot