Expose application inside a container
Registered by
hongbin
Application inside a container might be consumed by end-users/other containers. Although each container has its own IP address that can be used to access, those IP addresses cannot be relied upon to be stable over time (container could die and be re-created). It would be useful to have a way to reliably expose the service inside container(s). The solution might be similar to k8s service.
NOTE: this BP requires a spec to clarify the design
Blueprint information
- Status:
- Complete
- Approver:
- hongbin
- Priority:
- Medium
- Drafter:
- hongbin
- Direction:
- Approved
- Assignee:
- Pradeep Kumar Singh
- Definition:
- Obsolete
- Series goal:
- None
- Implementation:
- Not started
- Milestone target:
- None
- Started by
- Completed by
- hongbin
Related branches
Related bugs
Sprints
Whiteboard
I will start investigating this in coming weeks.
(hongbin 2018-03-11): I have re-visited this BP and I don't think we have use cases for this feature. I closed it for now and will re-open it if we have a demand for it.
(?)