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 configuring ingress #184

Closed
jvalkeal opened this issue Feb 9, 2018 · 2 comments
Closed

Support configuring ingress #184

jvalkeal opened this issue Feb 9, 2018 · 2 comments

Comments

@jvalkeal
Copy link
Contributor

jvalkeal commented Feb 9, 2018

Especially in skipper when upgrading app version you i.e. need to define a new node port which makes its usage rather cumbersome. If we could skip that step(defining actual port) and route traffic automatically via ingress, we'd get nice user level predictable addresses. Also it might allow better upgrade strategies on k8s.

@to-wi
Copy link

to-wi commented Mar 12, 2020

I think this relates to #370
From my experience most users want to expose a deployed stream via an Ingress. Therefore either a stable service name or an automatic Ingress creation is required

@chrisjs
Copy link
Contributor

chrisjs commented Jun 4, 2020

the service name which gets built from the info passed from skipper needs to be consistent and then this would be possible. see: spring-cloud/spring-cloud-skipper#953

@chrisjs chrisjs closed this as completed Jun 4, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants