使用Kubeadm在CentOS7.2上部署Kubernetes集群的方法

发布时间:2024-03-05 点击:133
服务器
本文参考kubernetes官网文章installing kubernetes on linux with kubeadm在centos7.2使用kubeadm部署kuebernetes集群,解决了一些在按照该文档部署时遇到的问题。
操作系统版本
# cat /etc/redhat-release centos linux release 7.2.1511 (core)内核版本
# uname -r3.10.0-327.el7.x86_64集群节点
192.168.120.122 kube-master192.168.120.123 kube-agent1192.168.120.124 kube-agent2192.168.120.125 kube-agent3即该集群包含一个控制节点和三个工作节点。
部署前的准备
配置可以访问google相关网站
这种部署方式使用的软件包由google相关源提供,因此集群节点必须能够访问外网,至于如何配置请自行解决。
关闭防火墙
# systemctl stop firewalld.service && systemctl disable firewalld.service禁用selinux
# setenforce 0# sed -i.bak \\\'s/selinux=enforcing/selinux=permissive/\\\' /etc/selinux/config配置yum源
# cat <<eof > /etc/yum.repos.d/kubernetes.repo[kubernetes]name=kubernetesbaseurl=https://packages.cloud.google.com/yum/repos/kubernetes-el7-x86_64enabled=1gpgcheck=1repo_gpgcheck=1gpgkey=https://packages.cloud.google.com/yum/doc/yum-key.gpg https://packages.cloud.google.com/yum/doc/rpm-package-key.gpgeof安装kubelet和kubeadm
在所有节点上安装以下软件包:
# yum install -y docker kubelet kubeadm kubectl kubernetes-cni# systemctl enable docker && systemctl start docker# systemctl enable kubelet && systemctl start kubelet然后设置内核参数:
# sysctl net.bridge.bridge-nf-call-iptables=1# sysctl net.bridge.bridge-nf-call-ip6tables=1初始化控制节点
# kubeadm init --pod-network-cidr=10.244.0.0/16因为在该集群中将使用flannel搭建pod网络,因此必须添加–pod-network-cidr参数。
注意:初始化较慢,因为该过程会pull一些docker image。
该命令的输出如下:
initializing your master...[kubeadm] warning: kubeadm is in beta, please do not use it for production clusters.[init] using kubernetes version: v1.6.4[init] using authorization mode: rbac[preflight] running pre-flight checks[certificates] generated ca certificate and key.[certificates] generated api server certificate and key.[certificates] api server serving cert is signed for dns names [kube-master kubernetes kubernetes.default kubernetes.default.svc kubernetes.default.svc.cluster.local] and ips [10.96.0.1 192.168.120.122][certificates] generated api server kubelet client certificate and key.[certificates] generated service account token signing key and public key.[certificates] generated front-proxy ca certificate and key.[certificates] generated front-proxy client certificate and key.[certificates] valid certificates and keys now exist in /etc/kubernetes/pki[kubeconfig] wrote kubeconfig file to disk: /etc/kubernetes/admin.conf[kubeconfig] wrote kubeconfig file to disk: /etc/kubernetes/kubelet.conf[kubeconfig] wrote kubeconfig file to disk: /etc/kubernetes/controller-manager.conf[kubeconfig] wrote kubeconfig file to disk: /etc/kubernetes/scheduler.conf[apiclient] created api client, waiting for the control plane to become ready[apiclient] all control plane components are healthy after 1377.560339 seconds[apiclient] waiting for at least one node to register[apiclient] first node has registered after 6.039626 seconds[token] using token: 60bc68.e94800f3c5c4c2d5[apiconfig] created rbac rules[addons] created essential addon: kube-proxy[addons] created essential addon: kube-dnsyour kubernetes master has initialized successfully!to start using your cluster, you need to run (as a regular user): sudo cp /etc/kubernetes/admin.conf $home/ sudo chown $(id -u):$(id -g) $home/admin.conf export kubeconfig=$home/admin.confyou should now deploy a pod network to the cluster.run kubectl apply -f [podnetwork].yaml with one of the options listed at: http://kubernetes.io/docs/admin/addons/you can now join any number of machines by running the following on each node as root: kubeadm join --token <token> 192.168.120.122:6443观察控制节点的docker image:
# docker imagesrepository tag image id created sizegcr.io/google_containers/kube-apiserver-amd64 v1.6.4 4e3810a19a64 2 days ago 150.6 mbgcr.io/google_containers/kube-controller-manager-amd64 v1.6.4 0ea16a85ac34 2 days ago 132.8 mbgcr.io/google_containers/kube-proxy-amd64

阿里云服务器续费88
临海云服务器价格
平板游戏交互式设计的10大规则
域名解析要钱吗
开发公众号需要购买域名吗 公众号域名的空间需要购买吗
阿里云服务器不用了怎么转租号
更改备案信息-备案平台
公安网备案信息-备案平台