Installed DevLake on AWS EKS cluster using helm

[DarkoDevops]

I installed Apache DevLake on AWS EKS cluster using helm, but when I want to access it, it's not working. Even when I export node port and node ip I can't access it.

On EKS is already deployed ingress-nginx so I used: helm install devlake devlake/devlake --set "ingress.enabled=true,ingress.hostname=devlake.dev.site1.dev"

[arthurio]

@DarkoDevops I'm a new user but here are my 5cents: you probably need a load balancer to accept traffic and direct it to your services via your ingress configuration (which isn't recommended). I would recommend removing the ingress and just using the port-forward kubernetes feature so that only people with access to the cluster can access the dashboards.

I deployed an instance yesterday using approach and it worked well!

[daniel-hutao]

Hi @DarkoDevops, I'll complete the testing of deploying DevLake to EKS soon, and then I'll write a related deployment document. Please wait for a few days, and I will come back here to tell you the progress in time.

[DarkoDevops]

Great, thank you @daniel-hutao .

[daniel-hutao]

Regarding the deployment of DevLake on EKS, the biggest issue previously was compatibility with Ingress configuration, but that has now been resolved. You guys can try using this values.yaml configuration:

ingress:
  enabled: true
  enableHttps: false
  className: "alb"
  hostname: ""
  # url prefix, not works right now, keep "/"
  prefix: /
  # if using https provides the certificates secret name
  tlsSecretName: ""
  # ingress http port
  httpPort: 80
  # ingress https port
  httpsPort: 443
  useDefaultNginx: false
  annotations:
    alb.ingress.kubernetes.io/scheme: internet-facing
    alb.ingress.kubernetes.io/target-type: ip