容器云系列之Kubernetes部署及使用

最新推荐文章于 2024-04-30 21:59:16 发布

置顶 solihawk

最新推荐文章于 2024-04-30 21:59:16 发布

阅读量1.1k

点赞数 16

分类专栏：容器云系列 # Kubernetes 文章标签： kubernetes 运维 docker 容器

本文链接：https://blog.csdn.net/solihawk/article/details/124680058

版权

容器云系列同时被 2 个专栏收录

18 篇文章 11 订阅

订阅专栏

Kubernetes

3 篇文章 0 订阅

订阅专栏

上一章节介绍了Kubernetes的整体架构和一些基本概念，这一章节继续介绍Kubernetes的环境部署以及使用。
容器云系列之Kubernetes基本架构介绍

2、K8S集群部署及使用

2.1 K8S集群配置部署

2.1.1 环境准备

部署环境配置如下：
在这里插入图片描述

工作流程如下：

在这里插入图片描述

2.1.2 初始化系统配置

在所有节点执行以下操作：

# 关闭防火墙
systemctl stop firewalld
systemctl disable firewalld
[root@tango-centos01 ~]# 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)

# 关闭selinux
sed -i 's/enforcing/disabled/' /etc/selinux/config  # 永久
setenforce 0  # 临时
[root@tango-centos01 ~]# setenforce 0
setenforce: SELinux is disabled

# 关闭swap
swapoff -a  # 临时
sed -ri 's/.*swap.*/#&/' /etc/fstab    # 永久

# 根据规划设置主机名
hostnamectl set-hostname <hostname>
[root@tango-centos01 ~]# hostname
tango-centos01

# 在master添加hosts
[root@tango-centos01 ~]# cat /etc/hosts
192.168.112.101 tango-centos01
192.168.112.102 tango-centos02
192.168.112.103 tango-centos03 

# 将桥接的IPv4流量传递到iptables的链
cat > /etc/sysctl.d/k8s.conf << EOF
net.bridge.bridge-nf-call-ip6tables = 1
net.bridge.bridge-nf-call-iptables = 1
EOF
sysctl --system  # 生效

# 时间同步
yum install ntpdate -y
ntpdate time.windows.com

2.1.3 安装 Docker、kubeadm、kubelet

1）安装docker

wget https://mirrors.aliyun.com/docker-ce/linux/centos/docker-ce.repo -O /etc/yum.repos.d/docker-ce.repo
yum -y install docker-ce
systemctl enable docker && systemctl start docker
[root@tango-centos01 ~]# docker -v
Docker version 20.10.14, build a224086

配置镜像下载加速器

vim /etc/docker/daemon.json
{
  "registry-mirrors": ["https://b9pmyelo.mirror.aliyuncs.com"],
  "exec-opts": ["native.cgroupdriver=systemd"]
}

#重新启动docker进程
systemctl restart docker
#查看docker信息，进行确认
[root@tango-centos01 ~]# docker info
Client:
 Context:    default
 Debug Mode: false
 Plugins:
  app: Docker App (Docker Inc., v0.9.1-beta3)
  buildx: Docker Buildx (Docker Inc., v0.8.1-docker)
  scan: Docker Scan (Docker Inc., v0.17.0)

2）添加阿里云软件源

cat > /etc/yum.repos.d/kubernetes.repo << EOF
[kubernetes]
name=Kubernetes
baseurl=https://mirrors.aliyun.com/kubernetes/yum/repos/kubernetes-el7-x86_64
enabled=1
gpgcheck=0
repo_gpgcheck=0
gpgkey=https://mirrors.aliyun.com/kubernetes/yum/doc/yum-key.gpg https://mirrors.aliyun.com/kubernetes/yum/doc/rpm-package-key.gpg
EOF

3）安装kubeadm、kubelet、kubectl

[root@tango-centos01 ~]# yum install -y kubelet-1.23.0 kubeadm-1.23.0 kubectl-1.23.0
[root@tango-centos01 yum.repos.d]# systemctl enable kubelet
Created symlink from /etc/systemd/system/multi-user.target.wants/kubelet.service to /usr/lib/systemd/system/kubelet.service.
[root@tango-centos01 ~]# kubeadm version
kubeadm version: &version.Info{Major:"1", Minor:"23", GitVersion:"v1.23.0", GitCommit:"ab69524f795c42094a6630298ff53f3c3ebab7f4", GitTreeState:"clean", BuildDate:"2021-12-07T18:15:11Z", GoVersion:"go1.17.3", Compiler:"gc", Platform:"linux/amd64"}

在这里插入图片描述

2.1.4 部署k8s-master（master执行）

1）kubeadm部署

kubeadm init \
  --apiserver-advertise-address=192.168.112.101\
  --image-repository registry.aliyuncs.com/google_containers \
  --kubernetes-version v1.23.0 \
  --service-cidr=10.10.0.0/12 \
  --pod-network-cidr=10.20.0.0/16 \
  --ignore-preflight-errors=all

–apiserver-advertise-address 集群通告地址
–image-repository 由于默认拉取镜像地址k8s.gcr.io国内无法访问，这里指定阿里云镜像仓库地址
–kubernetes-version K8s版本，与上面安装的一致
–service-cidr 集群内部虚拟网络，Pod统一访问入口
–pod-network-cidr Pod网络，与下面部署的CNI网络组件yaml中保持一致

[外链图片转存失败,源站可能有防盗链机制,建议将图片保存下来直接上传(img-rsRSuwK8-1652143069874)(https://note.youdao.com/favicon.ico)]

初始化之后，会输出一个join命令，先复制出来，node节点加入master会使用。

kubeadm join 192.168.112.101:6443 --token 84imqm.7o7z2agrdgwvbtmc \
        --discovery-token-ca-cert-hash sha256:e8231e87db94b63fdb7472c91cbee615666241b2f9119e97fbc69036e87ae937

2）拷贝k8s认证文件

[root@tango-centos01 ~]# mkdir -p $HOME/.kube
[root@tango-centos01 ~]# cp -i /etc/kubernetes/admin.conf $HOME/.kube/config
[root@tango-centos01 ~]# chown $(id -u):$(id -g) $HOME/.kube/config
[root@tango-centos01 ~]# cd $HOME/.kube
[root@tango-centos01 .kube]# ll -a
total 12
drwxr-xr-x   2 root root   20 May  1 00:21 .
dr-xr-x---. 14 root root 4096 May  1 00:21 ..
-rw-------   1 root root 5639 May  1 00:21 config

查看工作节点：

[root@tango-centos01 ~]# kubectl get nodes
NAME             STATUS     ROLES                  AGE     VERSION
tango-centos01   NotReady   control-plane,master   6m23s   v1.23.0

注：由于网络插件还没有部署，还没有准备就绪NotReady，继续操作

2.1.5 配置k8s的node节点

1）向集群添加新节点，执行在kubeadm init输出的kubeadm join命令

[root@tango-centos03 ~]# kubeadm join 192.168.112.101:6443 --token 84imqm.7o7z2agrdgwvbtmc         --discovery-token-ca-cert-hash sha256:e8231e87db94b63fdb7472c91cbee615666241b2f9119e97fbc69036e87ae937 --ignore-preflight-errors=all
[preflight] Running pre-flight checks
        [WARNING FileAvailable--etc-kubernetes-kubelet.conf]: /etc/kubernetes/kubelet.conf already exists
        [WARNING FileAvailable--etc-kubernetes-bootstrap-kubelet.conf]: /etc/kubernetes/bootstrap-kubelet.conf already exists
        [WARNING FileAvailable--etc-kubernetes-pki-ca.crt]: /etc/kubernetes/pki/ca.crt already exists
[preflight] Reading configuration from the cluster...
[preflight] FYI: You can look at this config file with 'kubectl -n kube-system get cm kubeadm-config -o yaml'
[kubelet-start] Writing kubelet configuration to file "/var/lib/kubelet/config.yaml"
[kubelet-start] Writing kubelet environment file with flags to file "/var/lib/kubelet/kubeadm-flags.env"
[kubelet-start] Starting the kubelet
[kubelet-start] Waiting for the kubelet to perform the TLS Bootstrap...

This node has joined the cluster:
* Certificate signing request was sent to apiserver and a response was received.
* The Kubelet was informed of the new secure connection details.

Run 'kubectl get nodes' on the control-plane to see this node join the cluster.

默认token有效期为24小时，当过期之后，该token就不可用了。这时就需要重新创建token，可以直接使用命令快捷生成：

kubeadm token create --print-join-command

2.1.6 部署容器网络（master执行）

Calico是一个纯三层的数据中心网络方案，是目前Kubernetes主流的网络方案。下载YAML：

wget https://docs.projectcalico.org/manifests/calico.yaml

下载完后还需要修改里面定义Pod网络（CALICO_IPV4POOL_CIDR），与前面kubeadm init的–pod-network-cidr指定的一样。

            - name: CALICO_IPV4POOL_CIDR
              value: "10.20.0.0/16"

修改完后文件后，进行部署：

[root@tango-centos01 ~]# kubectl apply -f calico.yaml
configmap/calico-config created
…
daemonset.apps/calico-node created
serviceaccount/calico-node created
deployment.apps/calico-kube-controllers created
serviceaccount/calico-kube-controllers created
Warning: policy/v1beta1 PodDisruptionBudget is deprecated in v1.21+, unavailable in v1.25+; use policy/v1 PodDisruptionBudget
poddisruptionbudget.policy/calico-kube-controllers created
[root@tango-centos01 ~]# kubectl get pods -n kube-system
NAME                                      READY   STATUS    RESTARTS       AGE
calico-kube-controllers-7c845d499-h4tdh   1/1     Running   0              14m
calico-node-bvtww                         1/1     Running   0              14m
calico-node-wfdjc                         1/1     Running   0              14m
coredns-6d8c4cb4d-h45n5                   1/1     Running   0              27m
coredns-6d8c4cb4d-k8xvq                   1/1     Running   0              27m
etcd-tango-centos01                       1/1     Running   11 (31m ago)   29m
kube-apiserver-tango-centos01             1/1     Running   9 (31m ago)    29m
kube-controller-manager-tango-centos01    1/1     Running   1              29m
kube-proxy-5xc5d                          1/1     Running   0              27m
kube-proxy-lktz4                          1/1     Running   0              18m
kube-scheduler-tango-centos01             1/1     Running   1              30m

#执行结束要等上一会才全部running，等Calico Pod都Running后，节点也会准备就绪。

2.1.7 部署Dashboard

Dashboard是官方提供的一个UI，可用于基本管理K8s资源。YAML下载地址：

wget https://raw.githubusercontent.com/kubernetes/dashboard/v2.4.0/aio/deploy/recommended.yaml

默认Dashboard只能集群内部访问，修改Service为NodePort类型，暴露到外部：

vi recommended.yaml
...
kind: Service
apiVersion: v1
metadata:
  labels:
    k8s-app: kubernetes-dashboard
  name: kubernetes-dashboard
  namespace: kubernetes-dashboard
spec:
  ports:
    - port: 443
      targetPort: 8443
      nodePort: 30001
  selector:
    k8s-app: kubernetes-dashboard
  type: NodePort
...

执行以下命令：

[root@tango-centos01 ~]# kubectl apply -f recommended.yaml 
namespace/kubernetes-dashboard created
serviceaccount/kubernetes-dashboard created
service/kubernetes-dashboard created
secret/kubernetes-dashboard-certs created
secret/kubernetes-dashboard-csrf created
secret/kubernetes-dashboard-key-holder created
configmap/kubernetes-dashboard-settings created
role.rbac.authorization.k8s.io/kubernetes-dashboard created
clusterrole.rbac.authorization.k8s.io/kubernetes-dashboard created
rolebinding.rbac.authorization.k8s.io/kubernetes-dashboard created
clusterrolebinding.rbac.authorization.k8s.io/kubernetes-dashboard created
deployment.apps/kubernetes-dashboard created
service/dashboard-metrics-scraper created
deployment.apps/dashboard-metrics-scraper created
[root@tango-centos01 ~]# kubectl get pod -n kubernetes-dashboard
NAME                                         READY   STATUS    RESTARTS   AGE
dashboard-metrics-scraper-799d786dbf-cmb95   1/1     Running   0          2m
kubernetes-dashboard-6b6b86c4c5-tkr7c        1/1     Running   0          2m1s

dashboard 服务的 namespace 是 kubernetes-dashboard，但是该服务的类型是ClusterIP，不便于我们通过浏览器访问，因此需要改成NodePort型的

[root@tango-centos01 ~]# kubectl get svc --all-namespaces
NAMESPACE              NAME                        TYPE        CLUSTER-IP      EXTERNAL-IP   PORT(S)                  AGE
default                kubernetes                  ClusterIP   10.0.0.1        <none>        443/TCP                  29m
kube-system            kube-dns                    ClusterIP   10.0.0.10       <none>        53/UDP,53/TCP,9153/TCP   25m
kubernetes-dashboard   dashboard-metrics-scraper   ClusterIP   10.15.132.106   <none>        8000/TCP                 4m54s
kubernetes-dashboard   kubernetes-dashboard        ClusterIP   10.11.13.27     <none>        443/TCP                  4m54s

删除现有的dashboard服务

[root@tango-centos01 ~]# kubectl delete service kubernetes-dashboard --namespace=kubernetes-dashboard
service "kubernetes-dashboard" deleted

修改，注意取值范围在30000-32767

kind: Service
apiVersion: v1
metadata:
  labels:
    k8s-app: kubernetes-dashboard
  name: kubernetes-dashboard
  namespace: kubernetes-dashboard
spec:
  type:NodePort
  ports:
    - port: 443
      targetPort: 8443
      nodePort: 10443
  selector:
    k8s-app: kubernetes-dashboard

重新查看namespace：

[root@tango-centos01 ~]# kubectl get svc --all-namespaces
NAMESPACE              NAME                        TYPE        CLUSTER-IP      EXTERNAL-IP   PORT(S)                  AGE
default                kubernetes                  ClusterIP   10.0.0.1        <none>        443/TCP                  39m
kube-system            kube-dns                    ClusterIP   10.0.0.10       <none>        53/UDP,53/TCP,9153/TCP   35m
kubernetes-dashboard   dashboard-metrics-scraper   ClusterIP   10.15.132.106   <none>        8000/TCP                 14m
kubernetes-dashboard   kubernetes-dashboard        NodePort    10.12.46.51     <none>        443:30001/TCP            41s

访问地址：https://192.168.112.101:30001/
在这里插入图片描述

想要访问dashboard服务，就要有访问权限，创建kubernetes-dashboard管理员角色

# 创建用户
kubectl create serviceaccount dashboard-admin -n kube-system
# 用户授权
[root@tango-centos01 ~]# kubectl create clusterrolebinding dashboard-admin --clusterrole=cluster-admin --serviceaccount=kube-system:dashboard-admin
clusterrolebinding.rbac.authorization.k8s.io/dashboard-admin created
# 获取用户Token
[root@tango-centos01 ~]# kubectl describe secrets -n kube-system $(kubectl -n kube-system get secret | awk '/dashboard-admin/{print $1}')
Name:         dashboard-admin-token-c5tdd
Namespace:    kube-system
Labels:       <none>
Annotations:  kubernetes.io/service-account.name: dashboard-admin
              kubernetes.io/service-account.uid: 188ca0a3-4a09-48ff-8298-1bbf9a11df35

Type:  kubernetes.io/service-account-token

Data
====
ca.crt:     1099 bytes
namespace:  11 bytes
token:      eyJhbGciOiJSUzI1NiIsImtpZCI6InMxVHV0YWxTQVBhb0tPcUtJV1pnWjlMS052ZXQ5S1dneVM3dDdWbldRdm8ifQ.eyJpc3MiOiJrdWJlcm5ldGVzL3NlcnZpY2VhY2NvdW50Iiwia3ViZXJuZXRlcy5pby9zZXJ2aWNlYWNjb3VudC9uYW1lc3BhY2UiOiJrdWJlLXN5c3RlbSIsImt1YmVybmV0ZXMuaW8vc2VydmljZWFjY291bnQvc2VjcmV0Lm5hbWUiOiJkYXNoYm9hcmQtYWRtaW4tdG9rZW4tYzV0ZGQiLCJrdWJlcm5ldGVzLmlvL3NlcnZpY2VhY2NvdW50L3NlcnZpY2UtYWNjb3VudC5uYW1lIjoiZGFzaGJvYXJkLWFkbWluIiwia3ViZXJuZXRlcy5pby9zZXJ2aWNlYWNjb3VudC9zZXJ2aWNlLWFjY291bnQudWlkIjoiMTg4Y2EwYTMtNGEwOS00OGZmLTgyOTgtMWJiZjlhMTFkZjM1Iiwic3ViIjoic3lzdGVtOnNlcnZpY2VhY2NvdW50Omt1YmUtc3lzdGVtOmRhc2hib2FyZC1hZG1pbiJ9.R_6NITlXwW1H-dB4p0ILxDz7MXJGMZ-D1kDTC1UBVWjQZ-zOs1yjDVV-1ViAYhQM99hlc2nnbdRto4LfqnDZ_8MUMUwmBSrPachSksZjC-mq4mKak2j_efVs4094I1tf6SfGLTzZ1ov_AWBnDrGCX87EUQVCziDkUUXX6NvDzW6dBxbyWJFXExA_r2DsVop3sG4uFfbubdyYseXLw1vFgBQMyKKYtZHvz96y1Fm2ANTJUMu_3ep_XAlDSQmevaMjhtDU6r8yp_w-7WuD1xGkKYB61-3sDjZEQ88tnOjlQU5aTzZUWeHKjsH0pPFJJlYmwzdT5rT7JPpdr5erx6SvWg

使用输出的token登录Dashboard
在这里插入图片描述

2.2 K8S集群交互

2.2.1 Kubelet与集群交互命令

在这里插入图片描述

2.2.2 API Rest接口

在这里插入图片描述

GET /< 资源名的复数格式 >：获得某一类型的资源列表，例如 GET /pods 返回一个 Pod 资源列表
POST /< 资源名的复数格式 >：创建一个资源
GET /< 资源名复数格式 >/< 名字 >：通过给出的名称（Name）获得单个资源
GET /pods/first 返回一个名称为“first”的 Pod
DELETE /< 资源名复数格式 >/< 名字 >：通过给出的名字删除单个资源

例如：访问API Server

curl -k --header "Authorization: Bearer sha256~XXX" –X GET https://api.lab.example.com:6443/apis

参考资料：

容器技术培训，张建锋老师
https://blog.csdn.net/tiny_du/article/details/123823093

转载请注明原文地址：https://blog.csdn.net/solihawk/article/details/124680058
文章会同步在公众号“牧羊人的方向”更新，感兴趣的可以关注公众号，谢谢！

solihawk

关注

16
点赞
踩
21

收藏

觉得还不错? 一键收藏
19
评论
容器云系列之Kubernetes部署及使用

Kubernetes集群环境的部署以及基本命令使用
复制链接

扫一扫

专栏目录

容器云系列之Kubernetes部署及使用

2、K8S集群部署及使用

2.1 K8S集群配置部署

2.1.1 环境准备

2.1.2 初始化系统配置

2.1.3 安装 Docker、kubeadm、kubelet

2.1.4 部署k8s-master（master执行）

2.1.5 配置k8s的node节点

2.1.6 部署容器网络（master执行）

2.1.7 部署Dashboard

2.2 K8S集群交互

2.2.1 Kubelet与集群交互命令

2.2.2 API Rest接口

“相关推荐”对你有帮助么？