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

Support Services of type ExternalName #127

Closed
julianvmodesto opened this issue May 30, 2017 · 4 comments

Comments

@julianvmodesto
Copy link
Contributor

commented May 30, 2017

Currently, Services of type ExternalName are unsupported.

For Services of type ExternalName, it would be great if we could support creating a simple HAProxy redirect rule to the ExternalName.

kind: Service
apiVersion: v1
metadata:
  name: foobar
spec:
  ports:
  type: ExternalName
  externalName: new.foobar.com

---

apiVersion: appscode.com/v1beta1
kind: Ingress
metadata:
  name: foobar
  annotations:
    kubernetes.io/ingress.class: voyager
spec:
  rules:
  - host: foobar.com
    http:
      paths:
      - path: '/'
        backend:
          serviceName: foobar

haproxy.cfg

backend foobar
    http-request redirect location new.foobar.com code 301
@tamalsaha

This comment has been minimized.

Copy link
Member

commented May 30, 2017

I think we should support this.

@tamalsaha tamalsaha added this to the 1.5.6 milestone May 30, 2017

@tamalsaha

This comment has been minimized.

Copy link
Member

commented May 30, 2017

@julianvmodesto , do you want to redirect or actually use the ExternalService as a backend. HAProxy can DNS resolve the IP and use that.

https://www.haproxy.com/blog/whats-new-in-haproxy-1-6/
HAProxy's DNS resolv feature https://cbonte.github.io/haproxy-dconv/1.7/configuration.html#5.3 ?

@julianvmodesto

This comment has been minimized.

Copy link
Contributor Author

commented May 30, 2017

Hmm that's neat.

I'd be happy with the http redirection if we have spec.rules.http.

Maybe for spec.rules.tcp, we'd want DNS resolution.

@tamalsaha

This comment has been minimized.

Copy link
Member

commented Jun 6, 2017

resolvers mydns
  nameserver dns1 10.0.0.1:53
  nameserver dns2 10.0.0.2:53
  resolve_retries       3
  timeout retry         1s
  hold other           30s
  hold refused         30s
  hold nx              30s
  hold timeout         30s
  hold valid           10s
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
3 participants
You can’t perform that action at this time.