[che-dev] Using the networking.k8s.io/v1 API

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]

[che-dev] Using the networking.k8s.io/v1 API

From: Anatolii Bazko <abazko@xxxxxxxxxx>
Date: Tue, 27 Jul 2021 12:02:04 +0300
Delivered-to: che-dev@xxxxxxxxxxx
List-archive: <https://www.eclipse.org/mailman/private/che-dev/>
List-help: <mailto:che-dev-request@eclipse.org?subject=help>
List-subscribe: <https://www.eclipse.org/mailman/listinfo/che-dev>, <mailto:che-dev-request@eclipse.org?subject=subscribe>
List-unsubscribe: <https://www.eclipse.org/mailman/options/che-dev>, <mailto:che-dev-request@eclipse.org?subject=unsubscribe>

Hello.

Currently che-operator [1] and che-server [2] use the extensions/v1beta1 API to create Ingress objects. This API won't be available in Kubernetes v1.22 [3]. That's why we are moving to use networking.k8s.io/v1 API which is available since Kubernetes v1.19.

After that Eclipse Che will require minimum Kubernetes v1.19 which is the oldest maintainable version of Kubernetes

Issue to track [4]

[1] https://github.com/eclipse-che/che-operator/
[2] https://github.com/eclipse-che/che-server/
[3] https://kubernetes.io/docs/reference/using-api/deprecation-guide/#ingress-v122

[4] https://github.com/eclipse/che/issues/20019

ANATOLII BAZKO

PRINCIPAL DEVELOPER

Red Hat Ukraine

Prev by Date: [che-dev] Reducing installations options for Che
Next by Date: [che-dev] Committer Election for David Kwon on Eclipse Che® has started
Previous by thread: [che-dev] Reducing installations options for Che
Next by thread: [che-dev] Committer Election for David Kwon on Eclipse Che® has started
Index(es):
- Date
- Thread

Breadcrumbs