You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@devlake.apache.org by "DarkoDevops (via GitHub)" <gi...@apache.org> on 2023/03/10 16:09:38 UTC
[GitHub] [incubator-devlake-helm-chart] DarkoDevops opened a new issue, #87: Installed DevLake on AWS EKS cluster using helm
DarkoDevops opened a new issue, #87:
URL: https://github.com/apache/incubator-devlake-helm-chart/issues/87
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"`
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: dev-unsubscribe@devlake.apache.org.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [incubator-devlake-helm-chart] daniel-hutao commented on issue #87: Installed DevLake on AWS EKS cluster using helm
Posted by "daniel-hutao (via GitHub)" <gi...@apache.org>.
daniel-hutao commented on issue #87:
URL: https://github.com/apache/incubator-devlake-helm-chart/issues/87#issuecomment-1504394756
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:
```yaml
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
```
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: dev-unsubscribe@devlake.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [incubator-devlake-helm-chart] DarkoDevops commented on issue #87: Installed DevLake on AWS EKS cluster using helm
Posted by "DarkoDevops (via GitHub)" <gi...@apache.org>.
DarkoDevops commented on issue #87:
URL: https://github.com/apache/incubator-devlake-helm-chart/issues/87#issuecomment-1467734149
Great, thank you @daniel-hutao .
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: dev-unsubscribe@devlake.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [incubator-devlake-helm-chart] daniel-hutao commented on issue #87: Installed DevLake on AWS EKS cluster using helm
Posted by "daniel-hutao (via GitHub)" <gi...@apache.org>.
daniel-hutao commented on issue #87:
URL: https://github.com/apache/incubator-devlake-helm-chart/issues/87#issuecomment-1467251544
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.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: dev-unsubscribe@devlake.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [incubator-devlake-helm-chart] arthurio commented on issue #87: Installed DevLake on AWS EKS cluster using helm
Posted by "arthurio (via GitHub)" <gi...@apache.org>.
arthurio commented on issue #87:
URL: https://github.com/apache/incubator-devlake-helm-chart/issues/87#issuecomment-1464050741
@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!
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: dev-unsubscribe@devlake.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org