data-8 / kubeadm-bootstrap Goto Github PK

View Code? Open in Web Editor NEW

22.0 4.0 20.0 55 KB

Supporting code + documentation for bootstrapping a kubeadm installation on bare-metal-ish machinery

License: BSD 3-Clause "New" or "Revised" License

Shell 100.00%

kubernetes-deployment kubeadm kubernetes

kubeadm-bootstrap's Issues

Issues running on Jetstream

Reporting issues as I go installing this on a Jetstream Ubuntu 16.04 image Devel + Docker, version 1.6, small instance:

Master setup

WARNING: docker version is greater than the most recently validated version. Docker version: 17.06.0-ce. Max validated version: 1.12 I guess I shouldn't worry about this, but wanted to note it here
kubeadm doesn't start due to /var/lib/kubelet, fixed with kubeadm reset, see
kubernetes/kubernetes#37063 (comment)
Error: could not find a ready tiller pod, I guess sleep 1m was not enough, I commented out the first part of the script and reran sudo ./init-master.bash

Small issues, everything looks to be working fine!

Worker setup

No issues on the commands

Should I do curl localhost on master again or on the worker? on the worker gives "Connection refused"

etcdserver related error while running init-master.bash

After first running ./init-kubeadm.bash which completes successfully I then run ./init-master.bash which gives this error message:

Tiller (the helm server side component) has been installed into your Kubernetes Cluster.
Happy Helming!
Error: release support failed: etcdserver: request timed out

System is:

# . /etc/os-release ; echo $PRETTY_NAME
Ubuntu 16.04.2 LTS

Need to Update Kubernetes to Remove Vulnerability CVE-2018-1002105

A vulnerability has been identified in Kubernetes which impacts Kubernetes v1.0.x-1.9.x

The patch for this vulnerability is only available in Kubernetes 1.10, 1.11, and 1.12, there are no official patches for 1.9 (which is the version of Kubernetes installed by this script).

This vulnerability is only a risk if you allow remote access to kubectl. As a matter of course we don't allow that in our setups, however other users of this script could expose themselves to this.

Should we update this repo to install the new, patched version of Kubernetes 1.10?

init-worker error on Jetstream

The first step went fine:

root@js-168-217:~/kubeadm-bootstrap# ./install-kubeadm.bash

But I got this error on the 2nd step::

root@js-168-217:~/kubeadm-bootstrap# ./init-worker.bash
[preflight] Running pre-flight checks.
        [WARNING FileExisting-crictl]: crictl not found in system path
discovery: Invalid value: "": using token-based discovery without DiscoveryTokenCACertHashes can be unsafe. set --discovery-token-unsafe-skip-ca-verification to continue

get pod not showing nginx-controller

Under "Setting up a Work Node", in step 4b, it says to run:

kubectl --namespace=kube-system get pod -o wide

That is to be run on master, right? On my deployment, when I run on master, I don't see nginx-controller running, like the docs say, although I do get kube-controller-manager running. Is that okay?

$ sudo kubectl --namespace=kube-system get pod -o wide

NAME                                                     READY     STATUS    RESTARTS   AGE       IP              NODE
etcd-js-169-176.jetstream-cloud.org                      1/1       Running   0          1h        172.27.247.13   js-169-176.jetstream-cloud.org
kube-apiserver-js-169-176.jetstream-cloud.org            1/1       Running   0          1h        172.27.247.13   js-169-176.jetstream-cloud.org
kube-controller-manager-js-169-176.jetstream-cloud.org   1/1       Running   0          1h        172.27.247.13   js-169-176.jetstream-cloud.org
kube-dns-6f4fd4bdf-52pp5                                 3/3       Running   0          1h        10.244.0.2      js-169-176.jetstream-cloud.org
kube-flannel-ds-g9bwx                                    1/1       Running   1          1h        172.27.247.13   js-169-176.jetstream-cloud.org
kube-flannel-ds-sjsjv                                    1/1       Running   0          1h        172.27.247.15   js-169-117.jetstream-cloud.org
kube-proxy-gbhbv                                         1/1       Running   0          1h        172.27.247.13   js-169-176.jetstream-cloud.org
kube-proxy-kjkx6                                         1/1       Running   0          1h        172.27.247.15   js-169-117.jetstream-cloud.org
kube-scheduler-js-169-176.jetstream-cloud.org            1/1       Running   0          1h        172.27.247.13   js-169-176.jetstream-cloud.org
tiller-deploy-69cb6984f-zm7x7                            1/1       Running   0          1h        10.244.0.3      js-169-176.jetstream-cloud.org

504 Gateway Time-out

On the worker node

https://github.com/data-8/kubeadm-bootstrap/blob/master/README.md#L147

curl localhost

yields

<html>
<head><title>504 Gateway Time-out</title></head>
<body bgcolor="white">
<center><h1>504 Gateway Time-out</h1></center>
<hr><center>nginx/1.13.8</center>
</body>
</html>

for me

I am pretty sure I've followed the instructions quite carefully, including the opening of ports.

data-8 / kubeadm-bootstrap Goto Github PK

kubeadm-bootstrap's Issues

Issues running on Jetstream

Master setup

Worker setup

etcdserver related error while running init-master.bash

Need to Update Kubernetes to Remove Vulnerability CVE-2018-1002105

init-worker error on Jetstream

get pod not showing nginx-controller

504 Gateway Time-out

Recommend Projects

React

Vue.js

Typescript

TensorFlow

Django

Laravel

D3

Recommend Topics

javascript

web

server

Machine learning

Visualization

Game

Recommend Org

Facebook

Microsoft

Google

Alibaba

D3

Tencent