Plan of K8s integration - futurewei-cloud/alcor-int GitHub Wiki

Plan

  • Phase one host integration by 1/2/2020 (low risk)
  • Phase two E2E integration by 1/9/2020 (unknown risk)

Work Items

  • K8s cluster pre-configuration
    • Download and build mizar and its dependency (done)
    • Load XDP program (done)
    • Kernel patch ( Action item: tested and integrated with K8s cluster pre-configuration flow)
  • Mizar transit daemon deployment as K8s DaemonSet
    • Status: deployment flow done and tested on AWS, to be tested for on-premise SC machines
  • ACA deployment as K8s DaemonSet
    • Status: plan to research on DaemonSet usage pattern for other host agents (separate pod or on the same pod as Transit Daemon)
    • Challenge: to shorten build time of ACA and its dependency (ep. gRPC)
  • Controller deployed with K8s
    • Challenge: to sort out the boostrap issue (including initial ip allocation, and machine.json generation)

Supported User Scenarios

  • Users wants to upgrade existing K8s clusters and use Alcor/Mizar for container networking provisioning and connectivity
  • Users wants to create new K8s clusters with user-selected OS (eg. Debian GNU/Linux) and install Alcor/Mizar for container networking provisioning and connectivity
  • Users wants to create new K8s clusters and tries out Alcor/Mizar (trial with the provided limited OS version)