Skip to content
This repository has been archived by the owner on Nov 30, 2021. It is now read-only.

Experimental Native Ingress not supporting deis domain #816

Closed
mariusmarais opened this issue Jun 1, 2017 · 1 comment
Closed

Experimental Native Ingress not supporting deis domain #816

mariusmarais opened this issue Jun 1, 2017 · 1 comment

Comments

@mariusmarais
Copy link

mariusmarais commented Jun 1, 2017

Yes, I know the feature is experimental :)

I've been testing the native ingress (per #732) in combination with Traefik and Let's Encrypt. Thus far it was pretty painless and seems to work well.

The lack of vanity domains does prevent me from giving it a proper test though, since deis domain:add xxx effectively does noting in this configuration.

Manually editing the app's ingress to add the correct host spec works as expected, so it seems that the only missing thing is the controller doing this automatically when native ingress is enabled:

...
spec:
  rules:
  # Original, deis-created rule
  - host: ui.apps.ss1.k8s.xxx
    http:
      paths:
      - backend:
          serviceName: ui
          servicePort: 80
        path: /
  # Manually added rule
  - host: helloworld.k8s.xxx
    http:
      paths:
      - backend:
          serviceName: ui
          servicePort: 80
        path: /

(FWIW: "Proper test" means giving devs access to this cluster to deploy a few low-risk apps without ops intervening to update hostnames.)

@bacongobbler
Copy link
Member

Closing as a dupe of deis/controller#1277

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

No branches or pull requests

2 participants