1 Kubernetes的基本概念与centos7安装

已于 2024-05-15 14:48:16 修改
阅读量297 收藏 7
点赞数 3
分类专栏： Kubernetes 文章标签： kubernetes 容器 云原生
于 2024-05-15 14:10:15 首次发布
版权声明：本文为博主原创文章，遵循 CC 4.0 BY-SA 版权协议，转载请附上原文出处链接和本声明。
本文链接：https://blog.csdn.net/weixin_44142987/article/details/138870195
版权

1 节点基础环境准备

这里提供VMware和centos7.9的软件包
https://pan.quark.cn/s/82d707d94cb8#/list/share
https://mirrors.tuna.tsinghua.edu.cn/centos/7.9.2009/isos/x86_64/CentOS-7-x86_64-Minimal-2009.iso

1.1 节点规划

master 192.168.100.10
node1 192.168.100.20
node2 192.168.100.30
| 服务器 | 操作系统 |
| master | CentOS Linux release 7.9.2009 (Core)|
| node1 | CentOS Linux release 7.9.2009 (Core)|
| node2 | CentOS Linux release 7.9.2009 (Core)|

1.2 配置VMware的虚拟网络模式

选择虚拟网络编辑器
在这里插入图片描述
在这里插入图片描述
在这里插入图片描述

1.3 更改网卡IP

//更改IP
//只需要修改ONBOOT="yes"
//加上IPADDR=192.168.100.10
//加上NETMASK=255.255.255.0
//加上GATEWAY=192.168.100.2
//加上DNS1=114.114.114.114
//这里演示master节点，node1、node2更改IPADDR即可
[root@master ~]# vi /etc/sysconfig/network-scripts/ifcfg-ens33 
TYPE="Ethernet"
PROXY_METHOD="none"
BROWSER_ONLY="no"
BOOTPROTO="static"
DEFROUTE="yes"
IPV4_FAILURE_FATAL="no"
IPV6INIT="yes"
IPV6_AUTOCONF="yes"
IPV6_DEFROUTE="yes"
IPV6_FAILURE_FATAL="no"
IPV6_ADDR_GEN_MODE="stable-privacy"
NAME="ens33"
UUID="9e82244b-a44c-4e63-abf8-28f7f968d40f"
DEVICE="ens33"
IPADDR=192.168.100.10
NETMASK=255.255.255.0
GATEWAY=192.168.100.2
DNS1=114.114.114.114
ONBOOT="yes"
"/etc/sysconfig/network-scripts/ifcfg-ens33" 19L, 399C
//保存 然后重启网络服务
[root@master ~]# systemctl restart network

1.4 更改主机名称

//192.168.100.10
[root@localhost ~]#  hostnamectl set-hostname master && bash
//192.168.100.20
[root@localhost ~]#  hostnamectl set-hostname node1 && bash
//192.168.100.20
[root@localhost ~]#  hostnamectl set-hostname node2 && bash

1.5 一些预备操作

//所有机器都要做，演示master节点
//关闭swap分区  k8s不喜欢swap分区 不关闭swap k8s会初始化失败
//临时
[root@master ~]# swapoff -a
//永久
[root@master ~]# sed -ri 's/.*swap.*/#&/' /etc/fstab

//关闭SElinux
//临时
[root@master ~]# setenforce 0
//查看SElinux状态
[root@master ~]# getenforce 
Permissive
//永久
[root@master ~]# sed -i 's/SELINUX=.*/SELINUX=disabled/g' /etc/selinux/config
//查看SElinux状态
[root@master ~]# getenforce 
Disabled
//两种均可

//关闭防火墙
[root@master ~]# systemctl stop firewalld
//设置防火墙开机不自启
[root@master ~]# systemctl disable firewalld

1.6 编辑/etc/hosts文件

[root@master ~]# cat >> /etc/hosts << EOF
192.168.100.10 master
192.168.100.20 node1
192.168.100.30 node2
EOF
[root@node1 ~]# cat >> /etc/hosts << EOF
192.168.100.10 master
192.168.100.20 node1
192.168.100.30 node2
EOF
[root@node2 ~]# cat >> /etc/hosts << EOF
192.168.100.10 master
192.168.100.20 node1
192.168.100.30 node2
EOF

1.7 使用Kubernetes的yum源

//安装wget
[root@master ~]# yum install -y wget
//移动原本yum源，增加新的Kubernetes yum源
[root@master ~]# mv /etc/yum.repos.d/* /mnt/;wget ftp://ftp.rhce.cc/k8s/* -P /etc/yum.repos.d/

1.8 安装docker和Kubernetes

//所有机器都要做，演示master节点
//安装docker-ce
[root@master ~]# yum -y install docker-ce
//查看docker版本
[root@master ~]# docker --version
Docker version 26.1.2, build 211e74b
//配置docker镜像加速器
[root@master ~]# cat > /etc/docker/daemon.json <<EOF
> {
> "registry-mirrors": ["https://frz7i079.mirror.aliyuncs.com"] 
> }
> EOF
//启动docker，并设置开机自启动
[root@master ~]# systemctl start docker
[root@master ~]# systemctl enable docker
//安装k8s1.20.0
[root@master ~]# yum -y install kubelet-1.20.0-0 kubeadm-1.20.0-0 kubectl-1.20.0-0 --disableexcludes=kubernetes
//设置不开启swap
[root@master ~]# sed -i "s/KUBELET_EXTRA_ARGS.*/KUBELET_EXTRA_ARGS=\"--fail-swap-on=false\"/g" /etc/sysconfig/kubelet
//设置kubelet开机自启动并现在启动kubelet
[root@master ~]# systemctl enable kubelet --now

2 节点基础环境准备

2.1 安装docker和Kubernetes

//查看kubernetes启动需要的镜像
[root@master ~]# kubeadm config images list
I0514 22:25:56.094454    9247 version.go:251] remote version is much newer: v1.30.0; falling back to: stable-1.20
k8s.gcr.io/kube-apiserver:v1.20.15
k8s.gcr.io/kube-controller-manager:v1.20.15
k8s.gcr.io/kube-scheduler:v1.20.15
k8s.gcr.io/kube-proxy:v1.20.15
k8s.gcr.io/pause:3.2
k8s.gcr.io/etcd:3.4.13-0
k8s.gcr.io/coredns:1.7.0
//进行kubeadm初始化
//要是初始化失败，使用下面命令可以重新设置Kubernetes节点
[root@master ~]# kubeadm reset -f
//--image-repository registry.aliyuncs.com/google_containers：使用阿里云镜像仓库，不然有些镜像下载不下来
//--kubernetes-version=v1.20.0：指定k8s的版本
//--pod-network-cidr=10.244.0.0/16：指定pod的网段
//--apiserver-advertise-address=192.168.100.10：API服务器将通告它正在侦听的IP地址。如果没有设置，将使用默认的网络接口。
//--ignore-preflight-errors=NumCPU：检查的列表，其错误将显示为警告。例如:“IsPrivilegedUser,交换”。值'all'忽略所有检查的错误。
//--ignore-preflight-errors=Swap：检查的列表，其错误将显示为警告。例如:“IsPrivilegedUser,交换”。值'all'忽略所有检查的错误。
//--service-cidr=10.96.0.0/12：为业务贵宾使用其他范围的IP地址。(默认“10.96.0.0/12”)
//会自动pull镜像进行Kubernetes搭建，不用自己再docker pull
[root@master ~]# kubeadm init --kubernetes-version=v1.20.0 --pod-network-cidr=10.244.0.0/16 --service-cidr=10.96.0.0/12 --apiserver-advertise-address=192.168.100.10 --ignore-preflight-errors=Swap --ignore-preflight-errors=NumCPU --image-repository registry.aliyuncs.com/google_containers
[init] Using Kubernetes version: v1.20.0
[preflight] Running pre-flight checks
        [WARNING IsDockerSystemdCheck]: detected "cgroupfs" as the Docker cgroup driver. The recommended driver is "systemd". Please follow the guide at https://kubernetes.io/docs/setup/cri/
        [WARNING SystemVerification]: this Docker version is not on the list of validated versions: 26.1.2. Latest validated version: 19.03
[preflight] Pulling images required for setting up a Kubernetes cluster
[preflight] This might take a minute or two, depending on the speed of your internet connection
[preflight] You can also perform this action in beforehand using 'kubeadm config images pull'
[certs] Using certificateDir folder "/etc/kubernetes/pki"
[certs] Generating "ca" certificate and key
[certs] Generating "apiserver" certificate and key
[certs] apiserver serving cert is signed for DNS names [kubernetes kubernetes.default kubernetes.default.svc kubernetes.default.svc.cluster.local master] and IPs [10.96.0.1 192.168.100.10]
[certs] Generating "apiserver-kubelet-client" certificate and key
[certs] Generating "front-proxy-ca" certificate and key
[certs] Generating "front-proxy-client" certificate and key
[certs] Generating "etcd/ca" certificate and key
[certs] Generating "etcd/server" certificate and key
[certs] etcd/server serving cert is signed for DNS names [localhost master] and IPs [192.168.100.10 127.0.0.1 ::1]
[certs] Generating "etcd/peer" certificate and key
[certs] etcd/peer serving cert is signed for DNS names [localhost master] and IPs [192.168.100.10 127.0.0.1 ::1]
[certs] Generating "etcd/healthcheck-client" certificate and key
[certs] Generating "apiserver-etcd-client" certificate and key
[certs] Generating "sa" key and public key
[kubeconfig] Using kubeconfig folder "/etc/kubernetes"
[kubeconfig] Writing "admin.conf" kubeconfig file
[kubeconfig] Writing "kubelet.conf" kubeconfig file
[kubeconfig] Writing "controller-manager.conf" kubeconfig file
[kubeconfig] Writing "scheduler.conf" kubeconfig file
[kubelet-start] Writing kubelet environment file with flags to file "/var/lib/kubelet/kubeadm-flags.env"
[kubelet-start] Writing kubelet configuration to file "/var/lib/kubelet/config.yaml"
[kubelet-start] Starting the kubelet
[control-plane] Using manifest folder "/etc/kubernetes/manifests"
[control-plane] Creating static Pod manifest for "kube-apiserver"
[control-plane] Creating static Pod manifest for "kube-controller-manager"
[control-plane] Creating static Pod manifest for "kube-scheduler"
[etcd] Creating static Pod manifest for local etcd in "/etc/kubernetes/manifests"
[wait-control-plane] Waiting for the kubelet to boot up the control plane as static Pods from directory "/etc/kubernetes/manifests". This can take up to 4m0s
[apiclient] All control plane components are healthy after 11.504263 seconds
[upload-config] Storing the configuration used in ConfigMap "kubeadm-config" in the "kube-system" Namespace
[kubelet] Creating a ConfigMap "kubelet-config-1.20" in namespace kube-system with the configuration for the kubelets in the cluster
[upload-certs] Skipping phase. Please see --upload-certs
[mark-control-plane] Marking the node master as control-plane by adding the labels "node-role.kubernetes.io/master=''" and "node-role.kubernetes.io/control-plane='' (deprecated)"
[mark-control-plane] Marking the node master as control-plane by adding the taints [node-role.kubernetes.io/master:NoSchedule]
[bootstrap-token] Using token: pev1kk.qdp5e2usn5gxm20v
[bootstrap-token] Configuring bootstrap tokens, cluster-info ConfigMap, RBAC Roles
[bootstrap-token] configured RBAC rules to allow Node Bootstrap tokens to get nodes
[bootstrap-token] configured RBAC rules to allow Node Bootstrap tokens to post CSRs in order for nodes to get long term certificate credentials
[bootstrap-token] configured RBAC rules to allow the csrapprover controller automatically approve CSRs from a Node Bootstrap Token
[bootstrap-token] configured RBAC rules to allow certificate rotation for all node client certificates in the cluster
[bootstrap-token] Creating the "cluster-info" ConfigMap in the "kube-public" namespace
[kubelet-finalize] Updating "/etc/kubernetes/kubelet.conf" to point to a rotatable kubelet client certificate and key
[addons] Applied essential addon: CoreDNS
[addons] Applied essential addon: kube-proxy

Your Kubernetes control-plane has initialized successfully!

To start using your cluster, you need to run the following as a regular user:

  mkdir -p $HOME/.kube
  sudo cp -i /etc/kubernetes/admin.conf $HOME/.kube/config
  sudo chown $(id -u):$(id -g) $HOME/.kube/config

Alternatively, if you are the root user, you can run:

  export KUBECONFIG=/etc/kubernetes/admin.conf

You should now deploy a pod network to the cluster.
Run "kubectl apply -f [podnetwork].yaml" with one of the options listed at:
  https://kubernetes.io/docs/concepts/cluster-administration/addons/

Then you can join any number of worker nodes by running the following on each as root:

kubeadm join 192.168.100.10:6443 --token pev1kk.qdp5e2usn5gxm20v \
    --discovery-token-ca-cert-hash sha256:6ee80937073b051e17644f4294fad1ac0c0928d4b3bf38980bb9d29efec81ead 
//查看docker images
[root@master ~]# docker images
REPOSITORY                                                        TAG        IMAGE ID       CREATED       SIZE
registry.aliyuncs.com/google_containers/kube-proxy                v1.20.0    10cc881966cf   3 years ago   118MB
registry.aliyuncs.com/google_containers/kube-apiserver            v1.20.0    ca9843d3b545   3 years ago   122MB
registry.aliyuncs.com/google_containers/kube-controller-manager   v1.20.0    b9fa1895dcaa   3 years ago   116MB
registry.aliyuncs.com/google_containers/kube-scheduler            v1.20.0    3138b6e3d471   3 years ago   46.4MB
registry.aliyuncs.com/google_containers/etcd                      3.4.13-0   0369cf4303ff   3 years ago   253MB
registry.aliyuncs.com/google_containers/coredns                   1.7.0      bfe3a36ebd25   3 years ago   45.2MB
registry.aliyuncs.com/google_containers/pause                     3.2        80d28bedfe5d   4 years ago   683kB
//根据提示创建目录和配置文件
[root@master ~]# mkdir -p $HOME/.kube
[root@master ~]# cp -i /etc/kubernetes/admin.conf $HOME/.kube/config
[root@master ~]# chown $(id -u):$(id -g) $HOME/.kube/config

//第二台机器node1

[root@node1 ~]# kubeadm join 192.168.100.10:6443 --token fvqpjn.8po0dy1edzattpsr     --discovery-token-ca-cert-hash sha256:6ee80937073b051e17644f4294fad1ac0c0928d4b3bf38980bb9d29efec81ead 
[preflight] Running pre-flight checks
        [WARNING IsDockerSystemdCheck]: detected "cgroupfs" as the Docker cgroup driver. The recommended driver is "systemd". Please follow the guide at https://kubernetes.io/docs/setup/cri/
        [WARNING SystemVerification]: this Docker version is not on the list of validated versions: 26.1.2. Latest validated version: 19.03
[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.

//第三台机器node2

[root@node2 ~]# kubeadm join 192.168.100.10:6443 --token fvqpjn.8po0dy1edzattpsr     --discovery-token-ca-cert-hash sha256:6ee80937073b051e17644f4294fad1ac0c0928d4b3bf38980bb9d29efec81ead 
[preflight] Running pre-flight checks
        [WARNING IsDockerSystemdCheck]: detected "cgroupfs" as the Docker cgroup driver. The recommended driver is "systemd". Please follow the guide at https://kubernetes.io/docs/setup/cri/
        [WARNING SystemVerification]: this Docker version is not on the list of validated versions: 26.1.2. Latest validated version: 19.03
[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.

//master节点

//查看节点是否都加入进来了
[root@master ~]# kubectl get nodes
NAME     STATUS     ROLES                  AGE   VERSION
master   NotReady   control-plane,master   13m   v1.20.0
node1    NotReady   <none>                 15s   v1.20.0
node2    NotReady   <none>                 3s    v1.20.0

2.2 配置Kubernetes的网络，使用flannel网络模式

//下载flannel插件

[root@master ~]# wget https://raw.githubusercontent.com/coreos/flannel/master/Documentation/kube-flannel.yml
--2024-05-15 00:22:40--  https://raw.githubusercontent.com/coreos/flannel/master/Documentation/kube-flannel.yml
Resolving raw.githubusercontent.com (raw.githubusercontent.com)... 199.232.68.133
Connecting to raw.githubusercontent.com (raw.githubusercontent.com)|199.232.68.133|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 4345 (4.2K) [text/plain]
Saving to: 鈥榢ube-flannel.yml.1鈥

100%[===========================================================>] 4,345       --.-K/s   in 0s      

2024-05-15 00:22:41 (25.2 MB/s) - 鈥榢ube-flannel.yml.1鈥saved [4345/4345]

//如果下载失败，可使用下述命令

[root@master ~]# cat >> /etc/hosts << EOF
> 199.232.68.133 raw.githubusercontent.com
> EOF
[root@master ~]# wget https://raw.githubcontent.com/coreos/flannel/master/Documentation/kube-flannel.yml

//配置flannel网络

[root@master ~]# kubectl apply -f kube-flannel.yml 
namespace/kube-flannel created
clusterrole.rbac.authorization.k8s.io/flannel created
clusterrolebinding.rbac.authorization.k8s.io/flannel created
serviceaccount/flannel created
configmap/kube-flannel-cfg created
daemonset.apps/kube-flannel-ds created

//下载镜像
//三台机器都要做，演示master节点

//查看需要哪些flannel镜像
[root@master ~]# grep image kube-flannel.yml 
image: docker.io/flannel/flannel-cni-plugin:v1.4.1-flannel1
image: docker.io/flannel/flannel:v0.25.1
image: docker.io/flannel/flannel:v0.25.1
[root@master ~]# docker pull docker.io/flannel/flannel-cni-plugin:v1.4.1-flannel1
[root@master ~]# docker pull docker.io/flannel/flannel:v0.25.1

//获取节点状态，发现都是ready

[root@master ~]# kubectl get nodes
NAME     STATUS   ROLES                  AGE   VERSION
master   Ready    control-plane,master   96m   v1.20.0
node1    Ready    <none>                 82m   v1.20.0
node2    Ready    <none>                 82m   v1.20.0

3 基本运行与维护

3.1 部署nginx应用

//下载nginx镜像
[root@master ~]# docker pull nginx
//创建namespace
[root@master ~]# kubectl create namespace ns-nginx
namespace/ns-nginx created
//创建deployment
[root@master ~]# kubectl create deployment nginx-deployment --image=nginx -n ns-nginx
deployment.apps/nginx-deployment created
//查看namespace中的应用
[root@master ~]# kubectl get pod -o wide -n ns-nginx
NAME                                READY   STATUS    RESTARTS   AGE   IP           NODE    NOMINATED NODE   READINESS GATES
nginx-deployment-84cd76b964-gn6pp   1/1     Running   0          10m   10.244.1.2   node1   <none>           <none>
//访问nginx
[root@master ~]# curl -L 10.244.1.2
<!DOCTYPE html>
<html>
<head>
<title>Welcome to nginx!</title>
<style>
html { color-scheme: light dark; }
body { width: 35em; margin: 0 auto;
font-family: Tahoma, Verdana, Arial, sans-serif; }
</style>
</head>
<body>
<h1>Welcome to nginx!</h1>
<p>If you see this page, the nginx web server is successfully installed and
working. Further configuration is required.</p>

<p>For online documentation and support please refer to
<a href="http://nginx.org/">nginx.org</a>.<br/>
Commercial support is available at
<a href="http://nginx.com/">nginx.com</a>.</p>

<p><em>Thank you for using nginx.</em></p>
</body>
</html>

3.2 将应用的端口映射为nodeport端口，集群外机器通过nodeport端口能够访问应用主页

//创建nodeport服务
[root@master ~]# kubectl expose deployment nginx-deployment --port=80 --type=NodePort -n ns-nginx
//获取ip
[root@master ~]# kubectl get svc -n ns-nginx
NAME               TYPE       CLUSTER-IP       EXTERNAL-IP   PORT(S)        AGE
nginx-deployment   NodePort   10.111.200.188   <none>        80:30050/TCP   47s
//访问nginx
[root@master ~]# curl -L 192.168.100.10:30050
<!DOCTYPE html>
<html>
<head>
<title>Welcome to nginx!</title>
<style>
html { color-scheme: light dark; }
body { width: 35em; margin: 0 auto;
font-family: Tahoma, Verdana, Arial, sans-serif; }
</style>
</head>
<body>
<h1>Welcome to nginx!</h1>
<p>If you see this page, the nginx web server is successfully installed and
working. Further configuration is required.</p>

<p>For online documentation and support please refer to
<a href="http://nginx.org/">nginx.org</a>.<br/>
Commercial support is available at
<a href="http://nginx.com/">nginx.com</a>.</p>

<p><em>Thank you for using nginx.</em></p>
</body>
</html>

//节点node1和node2访问

[root@node1 ~]# curl -L 192.168.100.10:30050
<!DOCTYPE html>
<html>
<head>
<title>Welcome to nginx!</title>
<style>
html { color-scheme: light dark; }
body { width: 35em; margin: 0 auto;
font-family: Tahoma, Verdana, Arial, sans-serif; }
</style>
</head>
<body>
<h1>Welcome to nginx!</h1>
<p>If you see this page, the nginx web server is successfully installed and
working. Further configuration is required.</p>

<p>For online documentation and support please refer to
<a href="http://nginx.org/">nginx.org</a>.<br/>
Commercial support is available at
<a href="http://nginx.com/">nginx.com</a>.</p>

<p><em>Thank you for using nginx.</em></p>
</body>
</html>

[root@node2 ~]# curl -L 192.168.100.10:30050
<!DOCTYPE html>
<html>
<head>
<title>Welcome to nginx!</title>
<style>
html { color-scheme: light dark; }
body { width: 35em; margin: 0 auto;
font-family: Tahoma, Verdana, Arial, sans-serif; }
</style>
</head>
<body>
<h1>Welcome to nginx!</h1>
<p>If you see this page, the nginx web server is successfully installed and
working. Further configuration is required.</p>

<p>For online documentation and support please refer to
<a href="http://nginx.org/">nginx.org</a>.<br/>
Commercial support is available at
<a href="http://nginx.com/">nginx.com</a>.</p>

<p><em>Thank you for using nginx.</em></p>
</body>
</html>

3.3 应用的动态扩缩容

//扩容nginx 到3个pod
[root@master ~]# kubectl scale deployment/nginx-deployment --replicas=3 -n ns-nginx
deployment.apps/nginx-deployment scaled
//查看
[root@master ~]# kubectl get pod -o wide -n ns-nginx
NAME                                READY   STATUS    RESTARTS   AGE    IP           NODE    NOMINATED NODE   READINESS GATES
nginx-deployment-84cd76b964-c8slp   1/1     Running   0          3m1s   10.244.1.3   node1   <none>           <none>
nginx-deployment-84cd76b964-gn6pp   1/1     Running   0          37m    10.244.1.2   node1   <none>           <none>
nginx-deployment-84cd76b964-zv5zd   1/1     Running   0          3m1s   10.244.2.4   node2   <none>           <none>

//缩容nginx 到3个pod
[root@master ~]# kubectl scale deployment/nginx-deployment --replicas=2 -n ns-nginx
deployment.apps/nginx-deployment scaled
//查看
[root@master ~]# kubectl get pod -o wide -n ns-nginx
NAME                                READY   STATUS    RESTARTS   AGE     IP           NODE    NOMINATED NODE   READINESS GATES
nginx-deployment-84cd76b964-gn6pp   1/1     Running   0          38m     10.244.1.2   node1   <none>           <none>
nginx-deployment-84cd76b964-zv5zd   1/1     Running   0          4m14s   10.244.2.4   node2   <none>           <none>

4 kubernetes的常用命令

//查看namespace中的deploymen

[root@master ~]# kubectl describe deployment -n ns-nginx
Name:                   nginx-deployment
Namespace:              ns-nginx
CreationTimestamp:      Wed, 15 May 2024 01:27:48 -0400
Labels:                 app=nginx-deployment
Annotations:            deployment.kubernetes.io/revision: 1
Selector:               app=nginx-deployment
Replicas:               2 desired | 2 updated | 2 total | 2 available | 0 unavailable
StrategyType:           RollingUpdate
MinReadySeconds:        0
RollingUpdateStrategy:  25% max unavailable, 25% max surge
Pod Template:
  Labels:  app=nginx-deployment
  Containers:
   nginx:
    Image:        nginx
    Port:         <none>
    Host Port:    <none>
    Environment:  <none>
    Mounts:       <none>
  Volumes:        <none>
Conditions:
  Type           Status  Reason
  ----           ------  ------
  Progressing    True    NewReplicaSetAvailable
  Available      True    MinimumReplicasAvailable
OldReplicaSets:  <none>
NewReplicaSet:   nginx-deployment-84cd76b964 (2/2 replicas created)
Events:
  Type    Reason             Age    From                   Message
  ----    ------             ----   ----                   -------
  Normal  ScalingReplicaSet  40m    deployment-controller  Scaled up replica set nginx-deployment-84cd76b964 to 1
  Normal  ScalingReplicaSet  6m2s   deployment-controller  Scaled up replica set nginx-deployment-84cd76b964 to 3
  Normal  ScalingReplicaSet  2m18s  deployment-controller  Scaled down replica set nginx-deployment-84cd76b964 to 2

//更多可以

[root@master ~]# kubectl describe -h
15号计划-
关注
  • 3
    点赞
  • 踩
  • 7
    收藏
    觉得还不错? 一键收藏
  • 0
    评论
专栏目录
Centos7 安装部署Kubernetes(k8s)集群过程
weixin_51697917的博客
11-16 782
Kubernetes 是一个可移植、可扩展的开源平台，用于管理容器化的工作负载和服务，可促进声明式配置和自动化。 Kubernetes 拥有一个庞大且快速增长的生态，其服务、支持和工具的使用范围相当广泛。 Kubernetes 这个名字源于希腊语，意为“舵手”或“飞行员”。k8s 这个缩写是因为 k 和 s 之间有八个字符的关系。 Google 在 2014 年开源了 Kubernetes 项目。 Kubernetes 建立在 Google 大规模运行生产工作负载十几年经验的基础上， 结合了社区中最优秀。
Kubernetes的基本概念与安装
weixin_39372311的博客
07-05 883
Kubernetes 是一个强大的容器编排平台，它可以帮助我们自动化应用程序的部署、扩展和管理。通过理解 Kubernetes 的基本概念和安装步骤，我们可以开始使用 Kubernetes 来部署和管理我们的应用程序。
kubernetes---CentOS7使用KubeOperator安装k8s图文完整版
直到世界的尽头
10-20 4023
KubeOperator简介 KubeOperator与Kubeadm、kops的区别 我们在之前的文章中已经使用Kubeadm安装过k8s: kubernetes—CentOS7安装kubernetes1.11.2图文完整版 Kubeadm是Kubernetes官方推出的快速部署Kubernetes的集群工具，其思路是将Kubernetes相关服务容器化以简化部署。 安装k8s集群的工具有很多：Kubeadm，Kops，KubeOperator 和 RKE（Rancher)等。 实际上它们 是 适合不同场
基于Centos7安装k8s集群
justlpf的专栏
02-16 530
1、部署k8s的两种方式：目前生产部署Kubernetes集群主要有两种方式：kubeadmKubeadm是一个K8s部署工具，提供kubeadm init和kubeadm join，用于快速部署Kubernetes集群。二进制包从github下载发行版的二进制包，手动部署每个组件，组成Kubernetes集群。本实验采用kubeadm的方式搭建集群。2、环境准备2.1 服务器要求：建议最小硬件配置：2核CPU、2G内存、20G硬盘。
(1) Kubernetes基本概念和术语
一切有为法，如梦亦如幻，如露亦如电，应作如是观。
06-11 7849
kubernetes是一个完备的分布式系统支撑平台，大部分概念如Node、Pod、Replication Controller、Service等都可以看作是一种。
minikube安装kubernetes(Centos7)【图文】
it_lihongmin的博客
03-25 1411
k8s有很多种安装方式minikube允许使用mac、linux、windows快速创建一个k8s集群； 也可以使用kubeadm方式基于二进制快速安装一个集群； 但是需要在生产环境执行的k8s集群需要使用官方发行的二进制进行安装，快速安装方式虽然方便但是屏蔽了很多底层的细节，发现问题很难发现问题，并且基于二进制方式创建也非常利于去理解其运行原理，更有利于后期的维护。 能快速开始搭建也是蛮好的选择，否则就从可能放弃于繁琐的安装过程，kubernetes安装需要满足cpu 至少2核心、内存至少可用的1.
Kubernetes 基本概念和部署
WuDan_1112的博客
07-22 1907
在部署应用程序的方式上，主要经历了三个时代传统部署互联网早期，会直接将应用程序部署在物理机上优点简单，不需要其它技术的参与缺点不能为应用程序定义资源使用边界，很难合理地分配计算资源，而且程序之间容易产生影响虚拟化部署可以在一台物理机上运行多个虚拟机，每个虚拟机都是独立的一个环境优点程序环境不会相互产生影响，提供了一定程度的安全性缺点增加了操作系统，浪费了部分资源容器化部署与虚拟化类似，但是共享了操作系统优点可以保证每个容器拥有自己的文件系统、CPU、内存、进程空间等。....................
CentOS7安装k8s
weixin_43839635的博客
07-09 1303
借鉴博客：https://www.cnblogs.com/xkops/p/6169034.html此博客里面有每个k8s配置文件的注释：https://blog.csdn.net/qq_35904833/article/details/78190257啊西吧，啊西吧，根据上面的博客终于安装成功了。妈的，网上大部分博客安装k8s配置写得乱七八槽的，终于找到一篇条理清晰，安装详细的k8s安装博客啦，哈哈哈哈，不容易啊快三个星期了，从狗屁不懂搞这玩意。
Kubernetes基本概念
zzn0109的博客
08-12 692
kubernetes
CentOS 7 使用 Calico 网络插件部署Kubernetes 集群
03-17
首先，我们需要了解Kubernetes的基本概念。Kubernetes（简称K8s）是一个自动化容器管理平台，用于部署、管理和扩展应用。它将容器化应用组织成逻辑单元，便于管理和维护。在网络方面，Kubernetes要求每个Pod（容器的...
vagrant-kubernetes-3-node-cluster-centos7：[DevOps]由centos7组成的3节点本地kubernetes集群
02-06
1. **Kubernetes核心概念**：包括Pods（基本运行单元）、Services（服务发现和负载均衡）、Deployments（应用部署）、ReplicaSets（确保Pod副本数量）、ConfigMaps和Secrets（配置和安全数据管理）等。 2. **...
基于Centos7.x+Kubernetes-1.12.3+Da1.8.3的master，node节点全自动快速一键安装部署文件
10-10
为了确保部署过程顺利，用户需要提前准备满足硬件和网络要求的CentOS服务器，并了解基本的Linux操作和Kubernetes概念。 总的来说，这个一键安装部署方案旨在简化Kubernetes集群的搭建流程，让开发者和运维人员能够...
kubernetes高可用集群搭建手册
12-30
这包括了解硬件和网络需求，选择合适的操作系统，以及熟悉Kubernetes的基本概念，如Pod、Service、Deployment等。此外，还需要检查所有参与节点的系统更新和安全补丁，确保所有设备都符合Kubernetes的最低系统要求。...
K8S中Containerd之ctr和crictl简介以及常见操作
xu710263124的博客
08-06 118
containerd之ctr和crictl
4.k8s：cronJob计划任务，初始化容器，污点、容忍，亲和力，身份认证和权限
鹏哥哥Aaa
08-06 11
cronJob计划任务，初始化容器，污点、容忍，亲和力，身份认证和权限
从0开始安装一个本地K8s环境
最新发布
追求幸福，探索未知的博客
08-06 411
在一个节点上快速部署搭建本地k8s集群
k8s持久化存储PV和PVC
qinxue722的博客
08-06 578
PS： 1）accessModes 指定访问模式为 ReadWriteOnce ，⽀持的访问模式有： 3.创建PVC 1）编写yaml文件 2）应用并查看 4.创建pod 1）编写pod的yaml文件并应用 5.验证 三、PV的回收 1.Retain回收策略 四、PV&PVC应用在MySQL的持久化存储 1.创建pv和pvc 1）创建pv，mysql-pv.yaml文件 2）创建PVC，mysql-pvc.yaml文件
CentOS 7 Docker安装与使用全面指南
"Docker的安装与使用详解Centos7" Docker是一种流行的开源容器化平台，它允许开发者将应用程序及其依赖环境打包成轻量级、可移植的容器，以便在不同的计算环境中轻松部署和运行。本资源详细阐述了如何在CentOS 7...
评论
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

当前余额3.43元 前往充值 >
需支付：10.00元
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付元
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明：

1.余额是钱包充值的虚拟货币，按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载，可以购买VIP、付费专栏及课程。

余额充值