search

solo-io / gloo-portal-issues

Public tracker for issues related to Gloo Portal
https://docs.solo.io/gloo-portal/latest/
1 stars 3 forks source link

k8s 1.22 - change CRD api version to V1 #160

Closed bcollard closed 2 years ago

bcollard commented 2 years ago

Describe the bug Today, we cannot deploy Gloo Portal on k8s 1.22 We have some references left with CRDs API version apiextensions.k8s.io/v1beta1

Error: INSTALLATION FAILED: failed to install CRD crds/auth_config.yaml: unable to recognize "": no matches for kind "CustomResourceDefinition" in version "apiextensions.k8s.io/v1beta1"

To Reproduce Steps to reproduce the behavior:

  1. kubectl apply '...'
  2. curl '....'
  3. See error

Expected behavior A clear and concise description of what you expected to happen.

Additional context Add any other context about the problem here, e.g.

sam-heilbron commented 2 years ago

Portal depends on the CRDs defined by the rate-limit and ext-auth dependencies. Those have been upgraded to use v1, so this change is a dependency bump to those libraries.

bewebi commented 2 years ago

Resolved by solo-io/dev-portal#2148, to be released in the next 1.2 beta