we use v1beta1 quite a bit & it's not available going forward <a href="https:/

We only need to change ingress.yaml<

K8s v1.22 compatibility about charts-clickhouse HOT 3 CLOSED

posthog commented on June 24, 2024

K8s v1.22 compatibility

from charts-clickhouse.

Comments (3)

tiina303 commented on June 24, 2024

We only need to change

ingress.yaml for networking.k8s.io/v1beta1
clickhouse crds for apiextensions.k8s.io/v1beta1

Note that the frontend config is networking.gke not k8s which isn't getting deprecated yet and is still used in various docs e.g. https://cloud.google.com/kubernetes-engine/docs/how-to/ingress-features#1.16-gke.3+_1

based on

$ grep "/v1beta1" -r charts/posthog
charts/posthog/crds/clickhouse_installation_template.yaml:apiVersion: apiextensions.k8s.io/v1beta1
charts/posthog/crds/clickhouse_operator_configurations.yaml:apiVersion: apiextensions.k8s.io/v1beta1
charts/posthog/crds/clickhouse_installation.yaml:apiVersion: apiextensions.k8s.io/v1beta1
charts/posthog/templates/gce-frontend-config.yaml:apiVersion: networking.gke.io/v1beta1
charts/posthog/templates/ingress.yaml:apiVersion: networking.k8s.io/v1beta1
charts/posthog/templates/ingress.yaml:    networking.gke.io/v1beta1.FrontendConfig: "{{ .Release.Name }}-frontend-config"

from charts-clickhouse.

tiina303 commented on June 24, 2024

TODO: add a 1.22 test to the ci as well

from charts-clickhouse.

tiina303 commented on June 24, 2024

Based on the earlier grep (no more v1beta1's) the good news is we're going to be k8s 1.25 compatible (as of now, I'm sure they will add more stuff there) after these changes as we don't have anything that will be deprecated there https://kubernetes.io/docs/reference/using-api/deprecation-guide/#v1-25

from charts-clickhouse.

Recommend Projects