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

Service-to-service network discovery #89

Closed
lukehoban opened this issue Oct 9, 2017 · 1 comment
Closed

Service-to-service network discovery #89

lukehoban opened this issue Oct 9, 2017 · 1 comment
Milestone

Comments

@lukehoban
Copy link
Member

For Services defined outside of Pulumi, we may want a mechanism for simple in-cluster service dsicovery along the lines of Docker links or Kubernetes proxies.

There are several reasons this might not actually be appealing:

  1. We already have direct service discovery via closure capture within our Pulumi model, and it's a shame to have to invent another mechanism for purely-outside-of-Pulumi cases
  2. It's still possible to pass in references via env vars or similar, which would help make dependencies more explicit anyway.
  3. We don't (in our current model) have a private network or in-cluster DNS like Kubernetes, so our options here aren't as clean (see Networking #67).

But all that said - we may decide we still want to do something. We'll need to flesh out use cases more to understand if and where there is real friction in the current experience.

@lukehoban lukehoban added this to the 0.12 milestone Feb 8, 2018
@lukehoban lukehoban modified the milestones: 0.12, 0.14 Mar 15, 2018
@lukehoban lukehoban modified the milestones: 0.14, 0.16 Apr 20, 2018
@lukehoban
Copy link
Member Author

If we do this we'll likely do it via #441, so closing this one out and we'll track there.

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

1 participant