asdf2014 / druid-helm

Helm Chart for Apache Druid
https://druid.apache.org
11 stars 8 forks source link

router ingress using depreciated ApiVersion #85

Open RyuCaelum opened 3 weeks ago

RyuCaelum commented 3 weeks ago

Hello,

I have recently setup the druid cluster and it seems to be working however.... I usually port-forward to access the UI. I am trying to setup the ingress

It seems the router ingress.yaml is using a deprecated ApiVersion here: https://github.com/asdf2014/druid-helm/blob/main/charts/druid/templates/router/ingress.yaml#L23

When using a EKS cluster above v1.22. This ApiVersion does not work as mentioned here: https://kubernetes.io/docs/reference/using-api/deprecation-guide/#ingress-v122

Currently I cannot deploy an ingress due to this.

Can this be amended so the ApiVersion can be changed to the newest version or have a variable to define which ApiVersion that can be used?

Below is my error:

16:01:56 │ Error: resource mapping not found for name: "druid-router" namespace: "" from "": no matches for kind "Ingress" in version "extensions/v1beta1" 16:01:56 │ ensure CRDs are installed first 16:01:56 │ 16:01:56 │ with helm_release.druid, 16:01:56 │ on druid.tf line 1, in resource "helm_release" "druid": 16:01:56 │ 1: resource "helm_release" "druid" {

This is due to my kubernetes EKS cluster being a version that does not support this older ApiVersion

asdf2014 commented 3 weeks ago

@RyuCaelum Thanks for reporting this, as https://kubernetes.io/docs/reference/using-api/deprecation-guide/#ingress-v122 mentioned, we might need update it to networking.k8s.io/v1 to resolve this compatibility issue, would you like to raise up a pull request for this :smile: