Skip to content
This repository has been archived by the owner on Dec 7, 2023. It is now read-only.

Support fetching IP addresses from CNI #303

Closed
twelho opened this issue Aug 8, 2019 · 1 comment · Fixed by #308
Closed

Support fetching IP addresses from CNI #303

twelho opened this issue Aug 8, 2019 · 1 comment · Fixed by #308
Assignees
Labels
kind/enhancement Categorizes issue or PR as related to improving an existing feature. kind/feature Categorizes issue or PR as related to a new feature. priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete.
Milestone

Comments

@twelho
Copy link
Contributor

twelho commented Aug 8, 2019

As of #300 ignite-spawn is not responsible for managing IP addresses anymore, they are fetched from the runtime by Ignite itself. In the case of CNI networking we need handling implemented to fetch the addresses from it instead of the runtime.

@twelho twelho added kind/feature Categorizes issue or PR as related to a new feature. priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete. kind/enhancement Categorizes issue or PR as related to improving an existing feature. labels Aug 8, 2019
@luxas luxas added this to the v0.5.0 milestone Aug 9, 2019
@luxas
Copy link
Contributor

luxas commented Aug 9, 2019

We should do this for in time for v0.5.0

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
kind/enhancement Categorizes issue or PR as related to improving an existing feature. kind/feature Categorizes issue or PR as related to a new feature. priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants