att-comdev / halcyon-kubernetes

Ansible playbooks for a kubadm-based kubernetes deployment, on supporting any cloud and any kubeadm-enabled OS.
Apache License 2.0
35 stars 22 forks source link

add multiple sdn providers to playbooks #3

Closed v1k0d3n closed 7 years ago

v1k0d3n commented 8 years ago

i think we need to add multiple cni-enabled sdn providers to the set of playbooks. i would like to see this done in the following (somewhat opinionated) way:

role:
  kube-sdn:
    tasks:
      main.yml (referring to other sdn playbooks)
        calico.yml
        canal.yml
        romana.yml
        weave.yml

i would like to add an "sdn boostrapped" artifact in /etc/kubernetes/halcyon/network/.sdn, and include the following output that can then be used later to identify which SDN is deployed:

ubuntu@kube1:~$ cat /etc/kubernetes/halcyon/network/.sdn

# Halcyon Network Deployment:
kube_sdn_deploy: {{ kube_sdn_deploy }}
kube_sdn: {{ kube_sdn }}

if any of the sdn folks are interested in this, that's fine...i can pick this up later as well.

v1k0d3n commented 8 years ago

along with this, i want to keep an eye on items like: https://github.com/kubernetes/kubernetes/issues/34101 http://stackoverflow.com/questions/39872332/how-to-fix-weave-net-crashloopbackoff-for-the-second-node

we may need to fetch the manifests, and adjust them based on the deployment. the instructions included with romana at least address this issue. the community is still trying to determine how to handle this going forward.

v1k0d3n commented 8 years ago

@aric49 do you want to take a stab at doing this? i can explain more, and help next week.

v1k0d3n commented 7 years ago

done. closing issue.