Feedback: ratel should be disabled by default and available on port 80 / 443

Issues
, ,
8

orange-oranje commented :

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

I wrote a custom ingress for ratel by myself

apiVersion: extensions/v1beta1
kind: Ingress
metadata:
  name: dgraph-dgraph-ratel
  labels:
    app: dgraph
    chart: dgraph
    component: ratel
    release: dgraph
    heritage: Helm
  annotations:
    kubernetes.io/ingress.class: nginx
spec:
  rules:
    - host: "route53"
      http:
        paths:
          - path: /
            backend:
              serviceName: dgraph-dgraph-ratel
              servicePort: 8000

But unable to connect to alpha from the external dashboard, so alpha needs an ingress as well