Move choosing of pool port from kuryr-controller to kuryr-daemon
In the crusade to decrease control plane latency and improve controller downtime behavior, a proposal was made to have:
* A VIF handler in kuryr-controller that only does pool management (e.g creation and deletion of ports in pools) and then updates pool information to the cni daemons. Communication may consist of:
* Annotating a node.
* Creating a CRD (Custom Resource Definition) object for each Pool.
* Creating a CRD object for each port in the Pool.
* a CNI daemon nested VIF driver that loads the existing VIF pool and when requests come just selects VIFs and annotates the pod with the VIF selection (or marks it somehow).
Blueprint information
- Status:
- Started
- Approver:
- Antoni Segura Puimedon
- Priority:
- High
- Drafter:
- Michal Dulko
- Direction:
- Approved
- Assignee:
- Michal Dulko
- Definition:
- Approved
- Series goal:
- Accepted for queens
- Implementation:
- Started
- Milestone target:
- queens-3
- Started by
- Antoni Segura Puimedon
- Completed by
Related branches
Related bugs
Sprints
Whiteboard
Gerrit topic: https:/
Addressed by: https:/
Use K8s 1.8 with Hyperkube
Addressed by: https:/
WiP: Preview of CNI daemon side VIF choice
Addressed by: https:/
Use K8s 1.8 with Hyperkube