We're getting the following warnings when installing the helm chart on a Kubernetes cluster running version 1.19.
W0127 00:48:48.240397 59213 warnings.go:70] apiextensions.k8s.io/v1beta1 CustomResourceDefinition is deprecated in v1.16+, unavailable in v1.22+; use apiextensions.k8s.io/v1 CustomResourceDefinition
W0127 00:48:48.310577 59213 warnings.go:70] apiextensions.k8s.io/v1beta1 CustomResourceDefinition is deprecated in v1.16+, unavailable in v1.22+; use apiextensions.k8s.io/v1 CustomResourceDefinition
W0127 00:48:53.273783 59213 warnings.go:70] apiextensions.k8s.io/v1beta1 CustomResourceDefinition is deprecated in v1.16+, unavailable in v1.22+; use apiextensions.k8s.io/v1 CustomResourceDefinition
W0127 00:48:53.373347 59213 warnings.go:70] apiextensions.k8s.io/v1beta1 CustomResourceDefinition is deprecated in v1.16+, unavailable in v1.22+; use apiextensions.k8s.io/v1 CustomResourceDefinition
W0127 00:48:58.263087 59213 warnings.go:70] apiextensions.k8s.io/v1beta1 CustomResourceDefinition is deprecated in v1.16+, unavailable in v1.22+; use apiextensions.k8s.io/v1 CustomResourceDefinition
W0127 00:48:58.307426 59213 warnings.go:70] apiextensions.k8s.io/v1beta1 CustomResourceDefinition is deprecated in v1.16+, unavailable in v1.22+; use apiextensions.k8s.io/v1 CustomResourceDefinition
W0127 00:49:03.241267 59213 warnings.go:70] apiextensions.k8s.io/v1beta1 CustomResourceDefinition is deprecated in v1.16+, unavailable in v1.22+; use apiextensions.k8s.io/v1 CustomResourceDefinition
W0127 00:49:03.312301 59213 warnings.go:70] apiextensions.k8s.io/v1beta1 CustomResourceDefinition is deprecated in v1.16+, unavailable in v1.22+; use apiextensions.k8s.io/v1 CustomResourceDefinition
Running on:
NAME CHART VERSION APP VERSION DESCRIPTION
hashicorp/consul 0.29.0 1.9.2 Official HashiCorp Consul Chart
Config:
controller:
enabled: true
Thanks, we do need to update these but it will take some time because we need to have both versions and update all our code gen. Until then these are just warnings and won't cause any issues.
Yeah, saw @ishustava picked up #790, so just wanted to report this one as well 馃槈
Hi @HofmannZ we have addressed this in https://github.com/hashicorp/consul-helm/pull/883 and this should be resolved with our next Helm release!