Container is a trend, it is time out from the virtual machine out of the container into the arms of the.
Have tried to install k8s, without success, various error mess, then dragged this finally found a tool can be quickly deployed, and finally the installation was successful.
This k8s rapid deployment tool is kubekit
github address is
https://github.com/Orientsoft/kubekit
According to the above address directly this step can also be deployed.
Next, I talk about specific deployment instructions:
General steps in closing the firewall Centos7.3, download the installation package and unzip kubekit package archive, unzip the package into kubekit out of the folder, and add executable permissions to the file package in the sh. Kubekit into the folder, perform ./kubekit init server ip address. Under normal circumstances, the installation is successful will be prompted to 9000 port is listening. This is k8s web interface.
System environment:
Centos7.3
kubekit Download
https://kubekit.orientsoft.cn/kubekit-linux64-0.3.tar.gz
Download package
https://kubekit.orientsoft.cn/package-1.7.2.tar.gz
I posted directly to the command history, you can refer to
[bogon to set a root @ ~] # the ls the anaconda kscfg kubekit-linux64 0.3 . tar gz package of 1.7 . 2 . tar gz [to set a root @ bogon ~] # tar xf kubekit-linux64 0.3 . tar gz [to set a root @ bogon ~] # the ls the anaconda kscfg kubekit-linux64 0.3 . tar gz kubekit-release- package of 1.7 . 2 . tar gz [to set a root @ bogon ~] # with the mv kubekit release- kubekit [to set a root @ bogon ~] #tar -xf package-1.7.2.tar.gz [root@bogon ~]# ls anaconda-ks.cfg kubekit kubekit-linux64-0.3.tar.gz package package-1.7.2.tar.gz [root@bogon ~]# mv package kubekit [root@bogon ~]# cd kubekit [root@bogon kubekit]# ls assets kubekit LICENSE package README.md server.sh templates [root@bogon kubekit]# cd package/ [root@bogon package]# ls docker.sh images master.sh network node.sh rpms [root@bogon package]# chmod +x *.sh [root@bogon package]# ls docker.sh images master.sh network node.sh rpms [root@bogon package]# cd .. [root@bogon kubekit]# ls assets kubekit LICENSE package README.md server.sh templates [root@bogon kubekit]# cat /etc/redhat-release CentOS Linux release 7.3.1611 (Core) [root@bogon kubekit]# systemctl status firewalld ● firewalld.service - firewalld - dynamic firewall daemon Loaded: loaded (/usr/lib/systemd/system/firewalld.service; disabled; vendor preset: enabled) Active: inactive (dead) Docs: man:firewalld(1) Dec 09 15:46:23 localhost.localdomain systemd[1]: Starting firewalld - dynamic firewall daemon... Dec 09 15:46:24 localhost.localdomain systemd[1]: Started firewalld - dynamic firewall daemon. Dec 09 07:53:04 bogon systemd[1]: Stopping firewalld - dynamic firewall daemon... Dec 09 07:53:04 bogon systemd[1]: Stopped firewalld - dynamic firewall daemon. [root@bogon kubekit]# getenforce Enforcing [root@bogon kubekit]# ip addre|grep inet inet 127.0.0.1/8 scope host lo inet6 ::1/128 scope host inet 192.168.2.133/24 brd 192.168.2.255 scope global ens33 inet6 fe80::a59c:93:e68e:ae/64 scope link [root@bogon kubekit]# ./kubekit init 192.168.2.133 ___ __ ___ ___ ________ _______ ___ __ ___ _________ |\ \|\ \ |\ \|\ \ |\ __ \ |\ ___ \ |\ \|\ \ |\ \ |\___ ___\ \ \ \/ /|_ \ \ \\\ \ \ \ \|\ /_ \ \ __/| \ \ \/ /|_ \ \ \ \|___ \ \_| \ \ ___ \ \ \ \\\ \ \ \ __ \ \ \ \_|/__ \ \ ___ \ \ \ \ \ \ \ \ \ \\ \ \ \ \ \\\ \ \ \ \|\ \ \ \ \_|\ \ \ \ \\ \ \ \ \ \ \ \ \ \ \__\\ \__\ \ \_______\ \ \_______\ \ \_______\ \ \__\\ \__\ \ \__\ \ \__\ \|__| \|__| \|_______| \|_______| \|_______| \|__| \|__| \|__| \|__| KubeKit V0.3 ⓒ OrientSoft 2018 Initialization process started, with kubernetes master IP: 192.168.2.133 ✔ HTTP file server listening at: 0.0.0.0:8000 Start to install docker engine... (1/2) Start to install docker... (2/2) Start to config docker... ✔ Docker engine installed... Start to initialize Kubernetes master node... (1/6) Start to load images for Kubernetes master... (2/6) Start to install components for Kubernetes master... (3/6) Start to configure firewall... (4/6) Start to initialize Kubernetes master... ✔ Master token 733899.b275f2c2c6bb5e78 saved into .k8s.token file. (5/6) Start to config Kubernetes network... (6/6) Start to install Kubernetes dashboard... ✔ Kubernetes master node initialized... Remember to reload shell with: source ~/.bashrc before using kubectl! [GIN-debug] [WARNING] Creating an Engine instance with the Logger and Recovery middleware already attached. [GIN-debug] [WARNING] Running in "debug" mode. Switch to "release" mode in production. - using env: export GIN_MODE=release - using code: gin.SetMode(gin.ReleaseMode) [GIN-debug] GET /assets/*filepath --> github.com/gin-gonic/gin.(*RouterGroup).createStaticHandler.func1 (4 handlers) [GIN-debug] HEAD /assets/*filepath --> github.com/gin-gonic/gin.(*RouterGroup).createStaticHandler.func1 (4 handlers) [GIN-debug] Loaded HTML Templates (3): - - index.html - locale.html open ./.nodes: no such file or directory [GIN-debug] GET / --> github.com/Orientsoft/kubekit/controllers.(*MainRouter).IndexHandler-fm (4 handlers) [GIN-debug] GET /ws --> github.com/Orientsoft/kubekit/controllers.(*MainRouter).Initialize.func1 (4 handlers) [GIN-debug] GET /node/list --> github.com/Orientsoft/kubekit/controllers.(*MainRouter).ListNodesHandler-fm (4 handlers) [GIN-debug] POST /node --> github.com/Orientsoft/kubekit/controllers.(*MainRouter).CreateNodeHandler-fm (4 handlers) [GIN-debug] PUT /node/remove/:id --> github.com/Orientsoft/kubekit/controllers.(*MainRouter).RemoveNodeHandler-fm (4 handlers) [GIN-debug] GET /node/refresh/:id --> github.com/Orientsoft/kubekit/controllers.(*MainRouter).RefreshNodeHandler-fm (4 handlers) [GIN-debug] GET /node/log/:id --> github.com/Orientsoft/kubekit/controllers.(*MainRouter).GetInstallLog-fm (4 handlers) [GIN-debug] POST /install --> github.com/Orientsoft/kubekit/controllers.(*MainRouter).InstallNodeHandler-fm (4 handlers) [GIN-debug] GET /install/progress/:id/:step --> github.com/Orientsoft/kubekit/controllers.(*MainRouter).NodeProgressHandler-fm (4 handlers) ✔ Toolkit server is listening at: 0.0.0.0:9000 [GIN-debug] Listening and serving HTTP on :9000
Access in your browser. The interface can see k8s
These are on my own computer test, but it seems not replace a computer, is still looking for the cause, if found, I'm coming up again