k8s master init and add node

k8s tutorial series main reference

1. add google apt-key

reference kubernetes添加不了google apt-key

k8s repository (中科大源)

deb http://us.archive.ubuntu.com/ubuntu/ xenial main restricted
deb http://us.archive.ubuntu.com/ubuntu/ xenial-updates main restricted
deb http://us.archive.ubuntu.com/ubuntu/ xenial universe
deb http://us.archive.ubuntu.com/ubuntu/ xenial-updates universe
deb http://us.archive.ubuntu.com/ubuntu/ xenial multiverse
deb http://us.archive.ubuntu.com/ubuntu/ xenial-updates multiverse
deb http://us.archive.ubuntu.com/ubuntu/ xenial-backports main restricted universe multiverse
deb http://security.ubuntu.com/ubuntu xenial-security main restricted
deb http://security.ubuntu.com/ubuntu xenial-security universe
deb http://security.ubuntu.com/ubuntu xenial-security multiverse
deb http://ppa.launchpad.net/tbfr/zabbix/ubuntu precise main
deb-src http://ppa.launchpad.net/tbfr/zabbix/ubuntu precise main
deb [arch=amd64] https://mirrors.ustc.edu.cn/kubernetes/apt kubernetes-xenial main
deb [arch=amd64] https://mirrors.ustc.edu.cn/kubernetes/apt kubernetes-xenial main

ali repository

deb http://mirrors.aliyuncs.com/ubuntu/ xenial main restricted universe multiverse
deb http://mirrors.aliyuncs.com/ubuntu/ xenial-security main restricted universe multiverse
deb http://mirrors.aliyuncs.com/ubuntu/ xenial-updates main restricted universe multiverse
deb http://mirrors.aliyuncs.com/ubuntu/ xenial-proposed main restricted universe multiverse
deb http://mirrors.aliyuncs.com/ubuntu/ xenial-backports main restricted universe multiverse
deb-src http://mirrors.aliyuncs.com/ubuntu/ xenial main restricted universe multiverse
deb-src http://mirrors.aliyuncs.com/ubuntu/ xenial-security main restricted universe multiverse
deb-src http://mirrors.aliyuncs.com/ubuntu/ xenial-updates main restricted universe multiverse
deb-src http://mirrors.aliyuncs.com/ubuntu/ xenial-proposed main restricted universe multiverse
deb-src http://mirrors.aliyuncs.com/ubuntu/ xenial-backports main restricted universe multiverse

2. k8s master init

reference kubeadm 搭建 kubernetes 集群

change hostname

echo "192-168-43-134.master" > /etc/hostname
echo "127.0.0.1   192-168-43-134.master" >> /etc/hosts
sysctl kernel.hostname=192-168-43-134.master

pull images

images=(kube-proxy-amd64:v1.11.0 coredns:1.1.3 pause:3.1 kubedns-amd64:1.7 kube-scheduler-amd64:v1.11.0 kube-controller-manager-amd64:v1.11.0 kube-apiserver-amd64:v1.11.0 etcd-amd64:3.2.18 pause-amd64:3.1)
for imageName in ${images[@]} ; do
  docker pull vickeywu/$imageName
  docker tag vickeywu/$imageName k8s.gcr.io/$imageName
  docker rmi vickeywu/$imageName
done

shutdown swap and start kubelet

kubeadm reset
sudo swapoff -a
systemctl stop kubelet
systemctl enable kubelet
systemctl start kubelet

update kube* (just one time)

apt-get update
apt-get install -y kubelet kubeadm kubectl

kubeadm init

kubeadm init --kubernetes-version=v1.11.0 --apiserver-advertise-address 192.168.43.131 --pod-network-cidr=10.244.0.0/16 --skip-preflight-checks

copy token from init output(use fork8s nodes join master cluster)

  kubeadm join 192.168.43.131:6443 --token yepdrb.7le3m7v0lrzuqkbj --discovery-token-ca-cert-hash sha256:6594be2785a7e216fda80ccf5560924aa0c802f08afdc187006a711fb75b40eb

run the following as a regular user and root

su vickey/root
mkdir -p $HOME/.kube
sudo cp -i /etc/kubernetes/admin.conf $HOME/.kube/config
sudo chown $(id -u):$(id -g) $HOME/.kube/config
echo "source <(kubectl completion bash)" >> ~/.bashrc

apply network solution

kubectl apply -f https://raw.githubusercontent.com/coreos/flannel/master/Documentation/kube-flannel.yml

3. k8s node add to master cluster(use this command when you wanna add node)

 kubeadm join 192.168.43.131:6443 --token yepdrb.7le3m7v0lrzuqkbj --discovery-token-ca-cert-hash sha256:6594be2785a7e216fda80ccf5560924aa0c802f08afdc187006a711fb75b40eb

manually pull flannel network image

reference blog

docker pull vickeywu/flannel:v0.10.0-amd64
docker tag vickeywu/flannel:v0.10.0-amd64 quay.io/coreos/flannel:v0.10.0-amd64
docker rmi vickeywu/flannel:v0.10.0-amd64

原文地址:https://www.cnblogs.com/vickey-wu/p/9329135.html

时间: 2024-08-01 01:48:12

k8s master init and add node的相关文章

k8s master查看不到worker节点

k8s master查看不到worker节点 一. 问题 master节点已经安装好,但是worker加入master显示成功,但是在master节点上使用kubectl get nodes命令查看不到,且master节点时而ready时而NotReady,worker重置kubeadm reset后,master节点恢复正常. 二 . 解决方法 通过设置hosts和hostname解决 2.1 设置hosts $ cat /etc/hosts 192.168.25.131 master01 1

手动安装K8s第六节:node节点部署-kubelet

部署kubelet1.准备二进制包[[email protected] ~]# cd /usr/local/src/kubernetes/server/bin/ [[email protected] bin]# scp kubelet kube-proxy k8snode1:/opt/kubernetes/bin/ [[email protected] bin]# scp kubelet kube-proxy k8snode2:/opt/kubernetes/bin/ 2.创建角色绑定[[ema

k8s master 节点和 node 节点 启动分析

Master 节点 coredns 2 个 ,对应的pause 容器 2 个flannel 1 个 ,对应的pause 容器 1 个proxy 1 个 ,对应的pause 容器 1 个scheduler 1 个 ,对应的pause 容器 1 个controller 1 个 ,对应的pause 容器 1 个apiserver 1 个 ,对应的pause 容器 1 个etcd 1 个 ,对应的pause 容器 1 个 master 节点 端口监听情况 kubelet TCP:10248kubelet

k8s安装flannel报错“node &quot;master&quot; pod cidr not assigned”

一.在安装flannel网络插件后,发现pod: kube-flannel-ds 一直是CrashLoopBackOff 此报错是因为安装Kubeadm Init的时候,没有增加 --pod-network-cidr 10.244.0.0/16参数或者kube-flannel.yml如果yml中的"Network": "10.244.0.0/16"和--pod-network-cidr不一样,所以,修改yml文件中的Network为相同网段后即可 二.在创建pod时

git init,git add和git commit三者的区别和使用

git init(版本库初始化命令) $cd /usr/local $mkdir demo $cd demo $git init 之后可以在demo目录下看到看到一个.git隐藏文件夹,这个文件夹就是版本库,而demo目录及其子目录就是工作区. git add(将工作区文件提交到暂存区stage) $touch welcome.txt $git add 文件welcome.txt从工作区被提交到暂存区,但此时文件并没有真正进入到版本库当中,文件目前只处于一个中间状态. git commit(将暂

Kubernetes(k8s)集群部署(k8s企业级Docker容器集群管理)系列之部署master/node节点组件(四)

0.前言 整体架构目录:ASP.NET Core分布式项目实战-目录 k8s架构目录:Kubernetes(k8s)集群部署(k8s企业级Docker容器集群管理)系列目录 1.部署master组件 master 服务器的组件有:kube-apiserver.kube-controller-manager.kube-scheduler 因此需要下载k8s master,下载地址:https://github.com/kubernetes/kubernetes/blob/master/CHANGE

二进制搭建kubernetes多master集群【四、配置k8s node】

上一篇我们部署了kubernetes的master集群,参考:二进制搭建kubernetes多master集群[三.配置k8s master及高可用] 本文在以下主机上操作部署k8s node k8s-node1:192.168.80.10 k8s-node2:192.168.80.11 k8s-node3:192.168.80.12 以下kubeadm和kubectl命令操作都是在k8s-master1上执行的. kubernetes work 节点运行如下组件: docker kubelet

[转帖]k8s集群node节点一直NotReady, 且node节点(并非master)的kubelet报错:Unable to update cni config: No networks found in /etc/cni/net.d

k8s集群node节点一直NotReady, 且node节点(并非master)的kubelet报错:Unable to update cni config: No networks found in /etc/cni/net.d http://www.voidcn.com/article/p-wpuagtbj-byy.html ? 考虑到node节点的kubelet报错Unable to update cni config: No networks found in /etc/cni/net.

Kebernetes 学习总结(15) K8s多master

Kubernetes v1.13版本发布后,kubeadm才正式进入GA,可以生产使用.本人历经了线下环境 和线上阿里环境 使用kubeadm方式部署了多master kubernetes集群.版本采用v1.14.2,将线下 过程分享给朋友们,如下(不喜勿喷)本例环境如下说明:etcd集群最少需要3台,而且必须保持两个正常运行.故本例中如果三台master有两台同时故障时,将导致cluster 不可用.1.前提条件关闭selinux .关闭firewalld .关闭swap(swapoff -a