首页 > 其他分享 >Kubernetes学习指南：保姆级实操手册06——部署kubernetes集群

Kubernetes学习指南：保姆级实操手册06——部署kubernetes集群

时间：2024-09-05 15:23:47浏览次数：10  
标签：学习指南 k8s 06 kubernetes system kubelet kubeadm kube config

Kubernetes学习指南：保姆级实操手册06——部署kubernetes集群

1、配置YUM源

### 在所有Master节点执行  
# 配置yum源  
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=1  
repo_gpgcheck=1  
gpgkey=https://mirrors.aliyun.com/kubernetes/yum/doc/yum-key.gpg https://mirrors.aliyun.com/kubernetes/yum/doc/rpm-package-key.gpg  

EOF
   
yum clean all  
yum repolist

2、配置kubelet参数

cat > /etc/sysconfig/kubelet <<EOF  
KUBELET_EXTRA_ARGS="--fail-swap-on=false"  
EOF

3、安装kubeadm、kubelet和kubectl

yum list kubeadm --showduplicates | sort -r 
yum install -y kubelet-1.28.2-0 kubeadm-1.28.2-0 kubectl-1.28.2-0

4、检测kubectl工具版本

kubectl version --client --output=yaml

5、配置kubeadm文件

kubeadm在初始化控制平面时会生成部署Kubernetes集群中各个组件所需的相关配置文件在/etc/kubernetes目录下

5.1、生成默认配置文件 （master01）
kubeadm config print init-defaults > kubeadm-init.yaml
5.2、根据默认的配置格式进行参数修改（cri-docker配置文件）
[root@k8s-master01 ~]# cat kubeadm-init.yaml  
apiVersion: kubeadm.k8s.io/v1beta3  
bootstrapTokens:  
- groups:  
  - system:bootstrappers:kubeadm:default-node-token  
  token: abcdef.0123456789abcdef  
  ttl: 24h0m0s  
  usages:  
  - signing  
  - authentication  
kind: InitConfiguration  
localAPIEndpoint:  
  advertiseAddress: 10.255.210.1  # 修改为k8s-master01节点的IP  
  bindPort: 6443  
nodeRegistration:  
  criSocket: unix:///var/run/cri-dockerd.sock  # 修改为cri-docker的路径  
  imagePullPolicy: IfNotPresent  
  name: k8s-master01  # 修改为master01的主机名  
  taints: null  
---  
apiServer:  
  timeoutForControlPlane: 4m0s  
apiVersion: kubeadm.k8s.io/v1beta3  
certificatesDir: /etc/kubernetes/pki  
clusterName: kubernetes  
controllerManager: {}  
dns: {}  
etcd:  
  local:  
    dataDir: /var/lib/etcd  
controlPlaneEndpoint: "10.255.210.99:16443"   # 添加apiserver的IP  
imageRepository: registry.aliyuncs.com/google_containers  #修改为aliyun的镜像地址  
kind: ClusterConfiguration  
kubernetesVersion: 1.28.2  
networking:  
  dnsDomain: cluster.local  
  serviceSubnet: 10.96.0.0/12  
  podSubnet: 10.100.0.0/16  # 新增pod节点的网段  
scheduler: {}  

## 增加下面配置  
---  
apiVersion: kubeproxy.config.k8s.io/v1alpha1  
kind: KubeProxyConfiguration  
mode: ipvs  
---  
apiVersion: kubelet.config.k8s.io/v1beta1  
kind: KubeletConfiguration  
cgroupDriver: systemd
5.3检查配置文件是否有错误
kubeadm init --config kubeadm-init.yaml --dry-run
5.4、镜像报取
[root@k8s-master01 ~]# kubeadm config images pull --config=kubeadm-init.yaml
[config/images] Pulled registry.aliyuncs.com/google_containers/kube-apiserver:v1.28.2
[config/images] Pulled registry.aliyuncs.com/google_containers/kube-controller-manager:v1.28.2
[config/images] Pulled registry.aliyuncs.com/google_containers/kube-scheduler:v1.28.2
[config/images] Pulled registry.aliyuncs.com/google_containers/kube-proxy:v1.28.2
[config/images] Pulled registry.aliyuncs.com/google_containers/pause:3.9
[config/images] Pulled registry.aliyuncs.com/google_containers/etcd:3.5.9-0
[config/images] Pulled registry.aliyuncs.com/google_containers/coredns:v1.10.1

[root@k8s-master01 ~]# docker image ls  # 显示下载的镜像
REPOSITORY                                                        TAG       IMAGE ID       CREATED         SIZE
registry.aliyuncs.com/google_containers/kube-apiserver            v1.28.2   cdcab12b2dd1   11 months ago   126MB
registry.aliyuncs.com/google_containers/kube-proxy                v1.28.2   c120fed2beb8   11 months ago   73.1MB
registry.aliyuncs.com/google_containers/kube-controller-manager   v1.28.2   55f13c92defb   11 months ago   122MB
registry.aliyuncs.com/google_containers/kube-scheduler            v1.28.2   7a5d9d67a13f   11 months ago   60.1MB
registry.aliyuncs.com/google_containers/etcd                      3.5.9-0   73deb9a3f702   15 months ago   294MB
registry.aliyuncs.com/google_containers/coredns                   v1.10.1   ead0a4a53df8   18 months ago   53.6MB
registry.aliyuncs.com/google_containers/pause                     3.9       e6f181688397   22 months ago   744kB
[root@k8s-master01 ~]#
5.5、kubeadm命令为源码安装，需要配置一下kubelet服务
[root@k8s-master01 ~]# kubeadm init phase kubelet-start --config kubeadm-init.yaml
[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
5.6、基于kubeadm配置文件 初始化集群
[root@k8s-master01 ~]# kubeadm init --config kubeadm-init.yaml --upload-certs
[init] Using Kubernetes version: v1.28.2
[preflight] Running pre-flight checks
        [WARNING Service-Kubelet]: kubelet service is not enabled, please run 'systemctl enable kubelet.service'
[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 [k8s-master01 kubernetes kubernetes.default kubernetes.default.svc kubernetes.default.svc.cluster.local] and IPs [10.96.0.1 10.255.210.1 10.255.210.99]
[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 [k8s-master01 localhost] and IPs [10.255.210.1 127.0.0.1 ::1]
[certs] Generating "etcd/peer" certificate and key
[certs] etcd/peer serving cert is signed for DNS names [k8s-master01 localhost] and IPs [10.255.210.1 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"
W0816 11:23:43.760627   30431 endpoint.go:57] [endpoint] WARNING: port specified in controlPlaneEndpoint overrides bindPort in the controlplane address
[kubeconfig] Writing "admin.conf" kubeconfig file
W0816 11:23:43.876266   30431 endpoint.go:57] [endpoint] WARNING: port specified in controlPlaneEndpoint overrides bindPort in the controlplane address
[kubeconfig] Writing "kubelet.conf" kubeconfig file
W0816 11:23:44.056103   30431 endpoint.go:57] [endpoint] WARNING: port specified in controlPlaneEndpoint overrides bindPort in the controlplane address
[kubeconfig] Writing "controller-manager.conf" kubeconfig file
W0816 11:23:44.145409   30431 endpoint.go:57] [endpoint] WARNING: port specified in controlPlaneEndpoint overrides bindPort in the controlplane address
[kubeconfig] Writing "scheduler.conf" kubeconfig file
[etcd] Creating static Pod manifest for local etcd in "/etc/kubernetes/manifests"
[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"
[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
[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 14.528431 seconds
[upload-config] Storing the configuration used in ConfigMap "kubeadm-config" in the "kube-system" Namespace
[kubelet] Creating a ConfigMap "kubelet-config" in namespace kube-system with the configuration for the kubelets in the cluster
[upload-certs] Storing the certificates in Secret "kubeadm-certs" in the "kube-system" Namespace
[upload-certs] Using certificate key:
8efbfd6e5068798c6d4a01fe56b0446ec8a357ca03fc31862192942a01b14ee9
[mark-control-plane] Marking the node k8s-master01 as control-plane by adding the labels: [node-role.kubernetes.io/control-plane node.kubernetes.io/exclude-from-external-load-balancers]
[mark-control-plane] Marking the node k8s-master01 as control-plane by adding the taints [node-role.kubernetes.io/control-plane:NoSchedule]
[bootstrap-token] Using token: abcdef.0123456789abcdef
[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
W0816 11:24:05.436284   30431 endpoint.go:57] [endpoint] WARNING: port specified in controlPlaneEndpoint overrides bindPort in the controlplane address
[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/

You can now join any number of the control-plane node running the following command on each as root:

  kubeadm join 10.255.210.99:16443 --token abcdef.0123456789abcdef \
        --discovery-token-ca-cert-hash sha256:5388538b15cb69bcb09e575aa569e753f8d4ed3fe70199ac8669686b039f4d29 \
        --control-plane --certificate-key 8efbfd6e5068798c6d4a01fe56b0446ec8a357ca03fc31862192942a01b14ee9

Please note that the certificate-key gives access to cluster sensitive data, keep it secret!
As a safeguard, uploaded-certs will be deleted in two hours; If necessary, you can use
"kubeadm init phase upload-certs --upload-certs" to reload certs afterward.

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

kubeadm join 10.255.210.99:16443 --token abcdef.0123456789abcdef \
        --discovery-token-ca-cert-hash sha256:5388538b15cb69bcb09e575aa569e753f8d4ed3fe70199ac8669686b039f4d29
5.7、配置 kubectl 命令行工具以便管理和使用 Kubernetes 集群
  • 作为普通用户：你需要将 admin.conf 文件复制到你自己的 .kube 目录，并确保你有权访问和使用它。这允许你以非 root 用户身份管理集群。
  • 作为 root 用户：你可以直接设置 KUBECONFIG 环境变量来指向 admin.conf，从而使用该文件来管理集群，而不需要复制文件。
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

6、添加master控制平台节点到集群

kubeadm join 10.255.210.99:16443 --token abcdef.0123456789abcdef \
        --discovery-token-ca-cert-hash sha256:5388538b15cb69bcb09e575aa569e753f8d4ed3fe70199ac8669686b039f4d29 \
        --control-plane --certificate-key  194d3f66187040195a509af9f350f914d62c23cab12e4724147b885115c0414a\
        --cri-socket unix:///var/run/cri-dockerd.sock

7、将work节点添加到集群

yum install -y kubelet-1.28.2-0 kubeadm-1.28.2-0  

kubeadm join 10.255.210.99:16443 --token abcdef.0123456789abcdef \  
        --discovery-token-ca-cert-hash sha256:5388538b15cb69bcb09e575aa569e753f8d4ed3fe70199ac8669686b039f4d29 \  
        --cri-socket unix:///var/run/cri-dockerd.sock

8、查看kubeadm-config的configmap信息

# kubectl -n kube-system get cm kubeadm-config -o yaml
apiVersion: v1
data:
  ClusterConfiguration: |
    apiServer:
      extraArgs:
        authorization-mode: Node,RBAC
      timeoutForControlPlane: 4m0s
    apiVersion: kubeadm.k8s.io/v1beta3
    certificatesDir: /etc/kubernetes/pki
    clusterName: kubernetes
    controlPlaneEndpoint: 10.255.210.99:16443
    controllerManager: {}
    dns: {}
    etcd:
      local:
        dataDir: /var/lib/etcd
    imageRepository: registry.aliyuncs.com/google_containers
    kind: ClusterConfiguration
    kubernetesVersion: v1.28.2
    networking:
      dnsDomain: cluster.local
      podSubnet: 10.200.0.0/16
      serviceSubnet: 10.96.0.0/12
    scheduler: {}
kind: ConfigMap
metadata:
  creationTimestamp: "2024-08-16T03:23:58Z"
  name: kubeadm-config
  namespace: kube-system
  resourceVersion: "236"
  uid: 3402d8fe-8c2b-45f4-a701-2b18db32f5a8

9、查看集群状态

9.1、查看node资源
[root@k8s-master01 ~]# kubectl get node
NAME           STATUS     ROLES           AGE     VERSION
k8s-master01   NotReady   control-plane   3h37m   v1.28.2
k8s-master02   NotReady   control-plane   3h4m    v1.28.2
k8s-master03   NotReady   control-plane   22m     v1.28.2
k8s-node01     NotReady   <none>          9m49s   v1.28.2
k8s-node02     NotReady   <none>          9m31s   v1.28.2
k8s-node03     NotReady   <none>          9m22s   v1.28.2
9.2、查看pod资源
[root@k8s-master01 ~]# kubectl get all -A
NAMESPACE     NAME                                       READY   STATUS    RESTARTS       AGE
kube-system   pod/coredns-66f779496c-9ttn2               0/1     Pending   0              3h39m
kube-system   pod/coredns-66f779496c-zq8k5               0/1     Pending   0              3h39m
kube-system   pod/etcd-k8s-master01                      1/1     Running   0              3h39m
kube-system   pod/etcd-k8s-master02                      1/1     Running   0              3h6m
kube-system   pod/etcd-k8s-master03                      1/1     Running   0              24m
kube-system   pod/kube-apiserver-k8s-master01            1/1     Running   0              3h39m
kube-system   pod/kube-apiserver-k8s-master02            1/1     Running   0              3h6m
kube-system   pod/kube-apiserver-k8s-master03            1/1     Running   0              24m
kube-system   pod/kube-controller-manager-k8s-master01   1/1     Running   1 (3h6m ago)   3h39m
kube-system   pod/kube-controller-manager-k8s-master02   1/1     Running   0              3h6m
kube-system   pod/kube-controller-manager-k8s-master03   1/1     Running   0              24m
kube-system   pod/kube-proxy-cm5dq                       1/1     Running   0              3h39m
kube-system   pod/kube-proxy-hd72m                       1/1     Running   0              3h6m
kube-system   pod/kube-proxy-lp5ds                       1/1     Running   0              11m
kube-system   pod/kube-proxy-nddj7                       1/1     Running   0              24m
kube-system   pod/kube-proxy-v68jh                       1/1     Running   0              11m
kube-system   pod/kube-proxy-zdz2s                       1/1     Running   0              11m
kube-system   pod/kube-scheduler-k8s-master01            1/1     Running   1 (3h6m ago)   3h39m
kube-system   pod/kube-scheduler-k8s-master02            1/1     Running   0              3h6m
kube-system   pod/kube-scheduler-k8s-master03            1/1     Running   0              24m

NAMESPACE     NAME                 TYPE        CLUSTER-IP   EXTERNAL-IP   PORT(S)                  AGE
default       service/kubernetes   ClusterIP   10.96.0.1    <none>        443/TCP                  3h39m
kube-system   service/kube-dns     ClusterIP   10.96.0.10   <none>        53/UDP,53/TCP,9153/TCP   3h39m

NAMESPACE     NAME                        DESIRED   CURRENT   READY   UP-TO-DATE   AVAILABLE   NODE SELECTOR            AGE
kube-system   daemonset.apps/kube-proxy   6         6         6       6            6           kubernetes.io/os=linux   3h39m

NAMESPACE     NAME                      READY   UP-TO-DATE   AVAILABLE   AGE
kube-system   deployment.apps/coredns   0/2     2            0           3h39m

NAMESPACE     NAME                                 DESIRED   CURRENT   READY   AGE
kube-system   replicaset.apps/coredns-66f779496c   2         2         0       3h39m
9.3、查看k8s证书有效期
[root@k8s-master01 ~]# kubeadm certs check-expiration
[check-expiration] Reading configuration from the cluster...
[check-expiration] FYI: You can look at this config file with 'kubectl -n kube-system get cm kubeadm-config -o yaml'

CERTIFICATE                EXPIRES                  RESIDUAL TIME   CERTIFICATE AUTHORITY   EXTERNALLY MANAGED
admin.conf                 Aug 16, 2025 03:23 UTC   364d            ca                      no
apiserver                  Aug 16, 2025 03:23 UTC   364d            ca                      no
apiserver-etcd-client      Aug 16, 2025 03:23 UTC   364d            etcd-ca                 no
apiserver-kubelet-client   Aug 16, 2025 03:23 UTC   364d            ca                      no
controller-manager.conf    Aug 16, 2025 03:23 UTC   364d            ca                      no
etcd-healthcheck-client    Aug 16, 2025 03:23 UTC   364d            etcd-ca                 no
etcd-peer                  Aug 16, 2025 03:23 UTC   364d            etcd-ca                 no
etcd-server                Aug 16, 2025 03:23 UTC   364d            etcd-ca                 no
front-proxy-client         Aug 16, 2025 03:23 UTC   364d            front-proxy-ca          no
scheduler.conf             Aug 16, 2025 03:23 UTC   364d            ca                      no

CERTIFICATE AUTHORITY   EXPIRES                  RESIDUAL TIME   EXTERNALLY MANAGED
ca                      Aug 14, 2034 03:23 UTC   9y              no
etcd-ca                 Aug 14, 2034 03:23 UTC   9y              no
front-proxy-ca          Aug 14, 2034 03:23 UTC   9y              no
9.4、查看token资源
kubeadm token list

10、命令自动补全

yum –y install bash-completion  

kubectl completion bash > ~/.kube/completion.bash.inc  
echo "source '$HOME/.kube/completion.bash.inc'" >> $HOME/.bash_profile  
source $HOME/.bash_profile

标签：学习指南,k8s,06,kubernetes,system,kubelet,kubeadm,kube,config
From： https://blog.51cto.com/u_4068847/11928480

相关文章

  • 最新版Kubernetes部署教程v1.31.0
    最新版Kubernetes高可用部署教程v1.31.0系统：Almalinux9架构：192.168.100.10control-plane-endpoint.k8s.localcontrol-plane-endpoint#负载均衡服务器，配置负载均衡后修改ip后续会讲解192.168.100.10masterA.k8s.localmasterA192.168.100.20masterB.k8s.localma......
  • LZC3106A国产高性能、高精度谐振模式双端控制器，专用LLC半桥谐振电路的控制应用
    综合描述LZC3106是一款高性能、高精度谐振模式双端控制器，专用于LLC半桥谐振电路的控制应用。它提供50%的互补占空比：高压侧开关和低压侧开关在完全相同的时间内以180°反相方式导通/关断。控制器通过调节系统工作频率来实现对输出电压的调制和稳定.LZC3106......
  • https://www.zhihu.com/pin/1814343061205024769
    在开发Docmatix时，我们发现经其微调的Florence-2在DocVQA任务上表现出色，但在基准测试中得分仍比较低。为了提高基准测试得分，我们必须在DocVQA数据集上进一步对模型进行微调，以学习该基准测试的语法风格。有意思的是，人类评估者认为经额外微调后，模型的表现似乎反而不如仅在Do......
  • 【Java】ApiPost请求返回 `406` 状态码（jackson）
    Java系列文章目录补充内容Windows通过SSH连接Linux第一章Linux基本命令的学习与Linux历史文章目录Java系列文章目录一、前言二、学习内容：三、问题描述3.1问题截图3.2错误简介3.2.1HTTP状态码`406NotAcceptable`3.2.2序列化和反序列化3.3后端问题位置四......
  • SP30906 解题报告
    题目传送门题目大意：给定一个长度为\(n\)的序列，\(q\)次询问区间\([l,r]\)内只出现过一次的数有多少个。思路：很明显带修莫队可以做。复习一下，带修莫队就是在普通莫队的基础上加上了时间轴，把操作分为询问操作和修改操作两种分别存下来。因为修改是有顺序的，每次修改只会会......
  • 力扣SQL仅数据库（1068~1084）
    1068.产品销售分析1需求编写解决方案，以获取Sales表中所有sale_id对应的product_name以及该产品的所有year和price。输入：Sales表：+---------+------------+------+----------+-------+|sale_id|product_id|year|quantity|price|+---------+--------......
  • POJ-1066
    题解告诉我：大意：在一个矩形区域内，有n条线段，线段的端点是在矩形边上的，有一个特殊点，问从这个点到矩形边的最少经过的线段条数最少的书目，穿越只能在中点穿越思路：需要巧妙的转换一下这个问题，因为从一个点到终点不可能“绕过”围墙，只能穿过去，所以门是否开在中点是无所谓的，只要求四周线......
  • Kubernetes学习指南：保姆级实操手册04——主机系统初始化
    四、Kubernetes学习指南：保姆级实操手册04——主机系统初始化前言：本章节主要内容是对主机操作系统的初始化操作，如发另外标注，所有的节点操作步骤一致，可以使用软件批量初始化。1.检查系统端口确保以下端口未被占用：运行后未有任务显示，表示端口未被占用。[root@k8s-master01~]#ss-......
  • Kubernetes学习指南：保姆级实操手册05——配置集群HA负载均衡
    五、Kubernetes学习指南：保姆级实操手册05——配置集群HA负载均衡简介：Keepalived提供VRRP实现，并允许您配置Linux机器使负载均衡，预防单点故障。HAProxy提供可靠、高性能的负载均衡，能与Keepalived完美配合1、配置Keepalive官方文档提供了两种运行方式（此案例使用选项1）：选项1：在......
  • Kubernetes从零到精通（03-资源对象）
    资源对象的种类今天我们开始研究Kubernetes中的资源对象，资源对象是Kubernetes这个软件定义的抽象逻辑概念，这些资源对象及其对应的属性（如资源对象之间的对应关系），都会保存到ectd数据库中并通过Kubernetes各控制组件实时更新，下面我们先看一下资源对象的分类和用途，然后再根据一个......

赞助商

阅读排行

网站主页关于我们联系我们网站地图

本网站内容转载自其他媒体，侵权联系[admin##ips99.com]。

Copyright © 2020-2023 IPS99 版权所有 IPS99