)]}'
{"doc/source/deployment-guide.rst":[{"author":{"_account_id":2834,"name":"Steven Dake","email":"steven.dake@gmail.com","username":"sdake"},"change_message_id":"ba62c4652d62e9984cb2c0cbc73aa70be026f16f","unresolved":false,"context_lines":[{"line_number":118,"context_line":"    CGROUP_DRIVER\u003d$(sudo docker info | grep \"Cgroup Driver\" | awk \u0027{print $3}\u0027)"},{"line_number":119,"context_line":"    sudo sed -i \"s|KUBELET_KUBECONFIG_ARGS\u003d|KUBELET_KUBECONFIG_ARGS\u003d--cgroup-driver\u003d$CGROUP_DRIVER --enable-cri\u003dfalse |g\" /etc/systemd/system/kubelet.service.d/10-kubeadm.conf"},{"line_number":120,"context_line":""},{"line_number":121,"context_line":".. note::"},{"line_number":122,"context_line":""},{"line_number":123,"context_line":"    If cgroup driver is not enable and CRI is not disabled then kubeadm init will"},{"line_number":124,"context_line":"    leave you into waiting state to get kubernetes up. "},{"line_number":125,"context_line":""},{"line_number":126,"context_line":"Setup the DNS server with the service CIDR::"},{"line_number":127,"context_line":""}],"source_content_type":"text/x-rst","patch_set":1,"id":"7ffa3b31_594fd991","line":124,"range":{"start_line":121,"start_character":0,"end_line":124,"end_character":55},"updated":"2017-04-18 13:12:06.000000000","message":"if you recall, the cgroup driver you suffered was because the docs needed to be refreshed in your web browser.  Instead I think this patch was intended to handle the synchronization step needed after kubernetes is installed.\n\nI\u0027d go with something like this prior to step 2\n\n.. warning::\n\n   Kubernetes must start completely before verification will function properly.  You will know kubernetes has completed initialization by checking using kubectl get pods -n kolla | grep dns that dns is in 3/3 RUNNING.  If you fail to wait, Step 2 will fail.","commit_id":"e8d29e6e02fa2adfc26d0a3a1d8f6d71bff9f1e3"}]}