Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Can a ingress be added for ratel ? #13

Closed
orange-oranje opened this issue Apr 1, 2020 · 3 comments
Closed

Can a ingress be added for ratel ? #13

orange-oranje opened this issue Apr 1, 2020 · 3 comments

Comments

@orange-oranje
Copy link

Ratel is mainly used for access through http from the external world

The apps mostly use the alpha to communicate with Dgraph

I can pick this up, just wanted to know thoughts from someone who knows better

@orange-oranje
Copy link
Author

If ratel is exposed outside using an ingress should the alpha be exposed as well through an ingress ?

@encryptblockr
Copy link

encryptblockr commented Apr 29, 2020

honestly i don't understand who makes helm-charts and not have a way to expose endpoints so ppl can access outside the kubernetes cluster..like just can't understand why

appreciate help with creating helm charts for this but it is almost useless to use..where is use case to access this dgraph outside the cluster? where is ingress? just frustrating that many projects all over the place but only a few actually provide real help

the single instance dev using kubectl has the ingress but for some reason they too smart to think no one will need ingress with helm charts

@darkn3rd
Copy link
Contributor

@orange-oranje @encryptblockr Ingress support has been added, I dropped some examples here: https://github.com/dgraph-io/charts/tree/master/charts/dgraph/example_values/ingress. I saw this as a major gap back in 2021 and took efforts to add it and test it with a variety of ingress resources. Also, support for Dgraph ingress is added, with an example for mixed gRPC and HTTP. There should be care to restrict traffic, because the database generally should never be exposed to the public Internet.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

3 participants