The following directory contains a set of kubelet manifests: https://github.com/Juniper/contrail-kubernetes/tree/master/cluster
These can be used by the k8s kubelet to starts the controller services on the master: e.g. The files should be copied to /etc/kubernetes/manifests assuming that the kubelet is running with the options: /usr/bin/kubelet --logtostderr=true --v=2 --address=127.0.0.1 --port=10250 --hostname_override=127.0.0.1 --allow_privileged=true --config=/etc/kubernetes/manifests The manifests pull docker containers from the registry opencontrail/<x> The config image has been patched with https://review.opencontrail.org/#/c/12816/ The control image has been patched with https://review.opencontrail.org/#/c/12837/ The kube-network-manager is set to autobuild on any commit to github. Docker hub will build an image whenever the github repository is updated. The manifests above translate directly to docker commands… it is also possible to use the docker hub containers directly via the docker command line (If you are integrating with a different system). The next steps in provisioning are to integrate with the salt provisioning used by kubernetes and build a container for the vrouter-agent. TODO items for k8s: - salt integration for master and node provisioning. - node plugin: replace the python scripts in the node with golang code that can be compiled directly in the kubelet or run as an independent command. o ensure that interfaces get readded when the agent restarts o report pod IP to kubelet o don’t depend on talking to the master (security concern). - network-manager: o use an external load-balancer for L7 load-balancing; o configuration parsing; o add port filtering rules to network-policies; Pedro.
_______________________________________________ Dev mailing list [email protected] http://lists.opencontrail.org/mailman/listinfo/dev_lists.opencontrail.org
