准备3台主机  master最少4G内存2核  且全部恢复到最初装机状态去做

master	192.168.80.20
node1	192.168.80.30
node2	192.168.80.40

准备工作，所有主机都要此操作

//关闭三台主机的防火墙和selinux、还有swap分区空间

[root@localhost ~]# systemctl disable --now firewalld
Removed /etc/systemd/system/multi-user.target.wants/firewalld.service.
Removed /etc/systemd/system/dbus-org.fedoraproject.FirewallD1.service.
[root@localhost ~]# setenforce 0
[root@localhost ~]# vi /etc/selinux/config 
[root@localhost ~]# vi /etc/fstab


#/dev/mapper/cs-swap     none                    swap    defaults        0 0

//同样的操作在node1 node2上面操作一次

//配置DNS域名解析、master上IPv4流量传递到iptables的链
[root@master ~]# vi /etc/hosts

127.0.0.1   localhost localhost.localdomain localhost4 localhost4.localdomain4
::1         localhost localhost.localdomain localhost6 localhost6.localdomain6
192.168.80.20 master
192.168.80.30 node1
192.168.80.40 node2

[root@master ~]# cat > /etc/sysctl.d/k8s.conf << EOF
> net.bridge.bridge-nf-call-ip6tables = 1
> net.bridge.bridge-nf-call-iptables = 1
> EOF

[root@master ~]# sysctl --system
* Applying /usr/lib/sysctl.d/10-default-yama-scope.conf ...
kernel.yama.ptrace_scope = 0
* Applying /usr/lib/sysctl.d/50-coredump.conf ...
kernel.core_pattern = |/usr/lib/systemd/systemd-coredump %P %u %g %s %t %c %h %e
kernel.core_pipe_limit = 16
* Applying /usr/lib/sysctl.d/50-default.conf ...
kernel.sysrq = 16
kernel.core_uses_pid = 1
kernel.kptr_restrict = 1
net.ipv4.conf.all.rp_filter = 1
net.ipv4.conf.all.accept_source_route = 0
net.ipv4.conf.all.promote_secondaries = 1
net.core.default_qdisc = fq_codel
fs.protected_hardlinks = 1
fs.protected_symlinks = 1
* Applying /usr/lib/sysctl.d/50-libkcapi-optmem_max.conf ...
net.core.optmem_max = 81920
* Applying /usr/lib/sysctl.d/50-pid-max.conf ...
kernel.pid_max = 4194304
* Applying /etc/sysctl.d/99-sysctl.conf ...
* Applying /etc/sysctl.d/k8s.conf ...   //看到这个代表成功了
* Applying /etc/sysctl.conf ...

//让更改的配置文件生效



[root@node1 ~]# vi /etc/hosts

127.0.0.1   localhost localhost.localdomain localhost4 localhost4.localdomain4
::1         localhost localhost.localdomain localhost6 localhost6.localdomain6
192.168.80.20 master
192.168.80.30 node1
192.168.80.40 node2
//node1添加


[root@node2 ~]# vi /etc/hosts

127.0.0.1   localhost localhost.localdomain localhost4 localhost4.localdomain4
::1         localhost localhost.localdomain localhost6 localhost6.localdomain6
192.168.80.20 master
192.168.80.30 node1
192.168.80.40 node2
//nede2上添加

//时间同步 配置chrony 并设置开机自启 免密认证 而免密登陆是在master上操作,node节点无需任何操作
[root@master ~]# yum -y install chrony
[root@master ~]# vi /etc/chrony.conf

# Use public servers from the pool.ntp.org project.
# Please consider joining the pool (http://www.pool.ntp.org/join.html).
pool time1.aliyun.com iburst

[root@master ~]# systemctl enable --now chronyd 


[root@node1 ~]# yum -y install chrony
[root@node2 ~]# yum -y install chrony
vi /etc/chrony.conf

# Use public servers from the pool.ntp.org project.
# Please consider joining the pool (http://www.pool.ntp.org/join.html).
pool time1.aliyun.com iburst
//跟master一样


[root@master ~]# ssh-keygen -t rsa
[root@master ~]# ssh-keygen -t rsa
Generating public/private rsa key pair.
Enter file in which to save the key (/root/.ssh/id_rsa): 
Created directory '/root/.ssh'.
Enter passphrase (empty for no passphrase): 
Enter same passphrase again: 
Your identification has been saved in /root/.ssh/id_rsa.
Your public key has been saved in /root/.ssh/id_rsa.pub.
The key fingerprint is:
SHA256:iq8VvWOHYXdeYd5LqiPFDdQhF/w0U4hHc3WHLwLipZc root@master
The key's randomart image is:
+---[RSA 3072]----+
|           .o*=oO|
|        . o.+o+*o|
|       . +.o .=.o|
|       .o E..o.+.|
|      . S.o +.oo.|
|     . + = = oo .|
|    . o = o .. . |
|     o . + ..    |
|    ...   ...    |
+----[SHA256]-----+
[root@master ~]# ssh-copy-id master
root@master's password: 

Number of key(s) added: 1

Now try logging into the machine, with:   "ssh 'master'"
and check to make sure that only the key(s) you wanted were added.

[root@master ~]# ssh-copy-id node1
[root@master ~]# ssh-copy-id node2

[root@master ~]# ssh root@node1
Last login: Wed Sep  7 09:40:23 2022 from 192.168.80.1
[root@node1 ~]# 
//可以互通登录就可以了

准备工作完成后把所有的主机全部重启一遍

所有节点安装Docker/kubeadm/kubelet

这一部分的操作是所有主机都要做的，同样是以master为例，如果有特殊配置会单独指出

所有主机安装Docker（包括master），这里以master为例
[root@master ~]# wget https://mirrors.aliyun.com/docker-ce/linux/centos/docker-ce.repo -O /etc/yum.repos.d/docker-ce.repo
--2022-09-07 10:08:44--  https://mirrors.aliyun.com/docker-ce/linux/centos/docker-ce.repo
Resolving mirrors.aliyun.com (mirrors.aliyun.com)... 183.136.209.240, 58.42.55.236, 58.42.55.239, ...
Connecting to mirrors.aliyun.com (mirrors.aliyun.com)|183.136.209.240|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 2081 (2.0K) [application/octet-stream]
Saving to: ‘/etc/yum.repos.d/docker-ce.repo’

/etc/yum.repos.d/docker-c 100%[==================================>]   2.03K  --.-KB/s    in 0.006s  

2022-09-07 10:08:44 (314 KB/s) - ‘/etc/yum.repos.d/docker-ce.repo’ saved [2081/2081]

[root@master ~]# yum -y install docker-ce

[root@master ~]# systemctl enable --now docker
Created symlink /etc/systemd/system/multi-user.target.wants/docker.service → /usr/lib/systemd/system/docker.service.

//配置加速器  和查看版本号
[root@master ~]# docker version
Version:           20.10.17
[root@node2 ~]# docker version
Client: Docker Engine - Community
 Version:           20.10.17
[root@node1 ~]#  docker version
Client: Docker Engine - Community
 Version:           20.10.17
//确保3台主机的版本一样

[root@master ~]# cat > /etc/docker/daemon.json << EOF
> {
>   "registry-mirrors": ["https://ay24c8ru.mirror.aliyuncs.com"],
>   "exec-opts": ["native.cgroupdriver=systemd"],
>   "log-driver": "json-file",
>   "log-opts": {
>     "max-size": "100m"
>   },
>   "storage-driver": "overlay2"
> }
> EOF
//配置加速器

2、添加kubernetes（K8s工具）阿里云YUM软件源
添加阿里云的kubernetes，便于安装工具
kubernetes源的地址
所有主机都要操作

[root@master ~]#  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

安装kubeadm，kubelet和kubectl
所有主机都要操作

[root@node1 yum.repos.d]# yum install -y kubelet-1.25.0 kubeadm-1.25.0 kubectl-1.25.0

[root@node1 yum.repos.d]# ls
CentOS-Base.repo  docker-ce.repo  kubernetes.repo
//确保3台主机都能看到源


[root@master ~]# systemctl enable kubelet
Created symlink /etc/systemd/system/multi-user.target.wants/kubelet.service → /usr/lib/systemd/system/kubelet.service.
//只设置开机自启但不要立马启动

部署Kubernetes Master

只在master上做此操作

//生成默认配置文件  由于默认拉取镜像地址k8s.gcr.io国内无法访问，这里指定阿里云镜像仓库地址。
[root@master ~]# containerd config default > /etc/containerd/config.toml
//把配置文件里面的k8s.gcr.io替换成registry.aliyuncs.com/google_containers
:%s#k8s.gcr.io#registry.aliyuncs.com/google_containers#
//用set替换

接下来重启

[root@master ~]# systemctl restart containerd
[root@master ~]#  kubeadm init \
>   --apiserver-advertise-address=192.168.80.20 \
>   --image-repository registry.aliyuncs.com/google_containers \
>   --kubernetes-version v1.25.0 \
>   --service-cidr=10.96.0.0/12 \
>   --pod-network-cidr=10.244.0.0/16
[init] Using Kubernetes version: v1.25.0
[preflight] Running pre-flight checks
	[WARNING FileExisting-tc]: tc not found in system path
[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.80.20]
[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.80.20 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.80.20 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 15.514510 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] Skipping phase. Please see --upload-certs
[mark-control-plane] Marking the node master 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 master as control-plane by adding the taints [node-role.kubernetes.io/control-plane:NoSchedule]
[bootstrap-token] Using token: k9gbwr.ps0ndo60p8ilh89u
[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.
//你需要设置一个pod网络到集群中，使用下面的命令
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.80.20:6443 --token k9gbwr.ps0ndo60p8ilh89u \
	--discovery-token-ca-cert-hash sha256:492906d98fbc626748496b7651e0334c366567aa2cdc12d0114015c7d699f005


[root@master ~]# echo 'export KUBECONFIG=/etc/kubernetes/admin.conf' > /etc/profile.d/k8s.sh
[root@master ~]# source /etc/profile.d/k8s.sh
[root@master ~]# echo $KUBECONFIG
/etc/kubernetes/admin.conf

.安装Pod网络插件（CNI）

//master主机操作其他主机不用做。这一步前要确保主机可以正常访问quay.io这个registery(仓库)，因为是从红帽官方quay.io拉取镜像
//kube-flannel.yml内容地址https://github.com/flannel-io/flannel/blob/master/Documentation/kube-flannel.yml

[root@master ~]# cat kube-flannel.yml 
---
kind: Namespace
apiVersion: v1
metadata:
  name: kube-flannel
  labels:
    pod-security.kubernetes.io/enforce: privileged
---
kind: ClusterRole
apiVersion: rbac.authorization.k8s.io/v1
metadata:
  name: flannel
rules:
- apiGroups:
  - ""
  resources:
  - pods
  verbs:
  - get
- apiGroups:
  - ""
  resources:
  - nodes
  verbs:
  - list
  - watch
- apiGroups:
  - ""
  resources:
  - nodes/status
  verbs:
  - patch
---
kind: ClusterRoleBinding
apiVersion: rbac.authorization.k8s.io/v1
metadata:
  name: flannel
roleRef:
  apiGroup: rbac.authorization.k8s.io
  kind: ClusterRole
  name: flannel
subjects:
- kind: ServiceAccount
  name: flannel
  namespace: kube-flannel
---
apiVersion: v1
kind: ServiceAccount
metadata:
  name: flannel
  namespace: kube-flannel
---
kind: ConfigMap
apiVersion: v1
metadata:
  name: kube-flannel-cfg
  namespace: kube-flannel
  labels:
    tier: node
    app: flannel
data:
  cni-conf.json: |
    {
      "name": "cbr0",
      "cniVersion": "0.3.1",
      "plugins": [
        {
          "type": "flannel",
          "delegate": {
            "hairpinMode": true,
            "isDefaultGateway": true
          }
        },
        {
          "type": "portmap",
          "capabilities": {
            "portMappings": true
          }
        }
      ]
    }
  net-conf.json: |
    {
      "Network": "10.244.0.0/16",
      "Backend": {
        "Type": "vxlan"
      }
    }
---
apiVersion: apps/v1
kind: DaemonSet
metadata:
  name: kube-flannel-ds
  namespace: kube-flannel
  labels:
    tier: node
    app: flannel
spec:
  selector:
    matchLabels:
      app: flannel
  template:
    metadata:
      labels:
        tier: node
        app: flannel
    spec:
      affinity:
        nodeAffinity:
          requiredDuringSchedulingIgnoredDuringExecution:
            nodeSelectorTerms:
            - matchExpressions:
              - key: kubernetes.io/os
                operator: In
                values:
                - linux
      hostNetwork: true
      priorityClassName: system-node-critical
      tolerations:
      - operator: Exists
        effect: NoSchedule
      serviceAccountName: flannel
      initContainers:
      - name: install-cni-plugin
       #image: flannelcni/flannel-cni-plugin:v1.1.0 for ppc64le and mips64le (dockerhub limitations may apply)
        image: docker.io/rancher/mirrored-flannelcni-flannel-cni-plugin:v1.1.0
        command:
        - cp
        args:
        - -f
        - /flannel
        - /opt/cni/bin/flannel
        volumeMounts:
        - name: cni-plugin
          mountPath: /opt/cni/bin
      - name: install-cni
       #image: flannelcni/flannel:v0.19.2 for ppc64le and mips64le (dockerhub limitations may apply)
        image: docker.io/rancher/mirrored-flannelcni-flannel:v0.19.2
        command:
        - cp
        args:
        - -f
        - /etc/kube-flannel/cni-conf.json
        - /etc/cni/net.d/10-flannel.conflist
        volumeMounts:
        - name: cni
          mountPath: /etc/cni/net.d
        - name: flannel-cfg
          mountPath: /etc/kube-flannel/
      containers:
      - name: kube-flannel
       #image: flannelcni/flannel:v0.19.2 for ppc64le and mips64le (dockerhub limitations may apply)
        image: docker.io/rancher/mirrored-flannelcni-flannel:v0.19.2
        command:
        - /opt/bin/flanneld
        args:
        - --ip-masq
        - --kube-subnet-mgr
        resources:
          requests:
            cpu: "100m"
            memory: "50Mi"
          limits:
            cpu: "100m"
            memory: "50Mi"
        securityContext:
          privileged: false
          capabilities:
            add: ["NET_ADMIN", "NET_RAW"]
        env:
        - name: POD_NAME
          valueFrom:
            fieldRef:
              fieldPath: metadata.name
        - name: POD_NAMESPACE
          valueFrom:
            fieldRef:
              fieldPath: metadata.namespace
        - name: EVENT_QUEUE_DEPTH
          value: "5000"
        volumeMounts:
        - name: run
          mountPath: /run/flannel
        - name: flannel-cfg
          mountPath: /etc/kube-flannel/
        - name: xtables-lock
          mountPath: /run/xtables.lock
      volumes:
      - name: run
        hostPath:
          path: /run/flannel
      - name: cni-plugin
        hostPath:
          path: /opt/cni/bin
      - name: cni
        hostPath:
          path: /etc/cni/net.d
      - name: flannel-cfg
        configMap:
          name: kube-flannel-cfg
      - name: xtables-lock
        hostPath:
          path: /run/xtables.lock
          type: FileOrCreate



[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
//created 创建完成，出现这个表示完成

加入Kubernetes Node

在初始化集群的时候会反馈很多的信息，其中最后一句话是最重要的，这句话是一个命令，是在node端执行的，表示将node主机添加到k8s集群中

到所有的节点上执行这个命令 node1和node2

[root@node1 ~]# kubeadm join 192.168.80.20:6443 --token k9gbwr.ps0ndo60p8ilh89u \
> --discovery-token-ca-cert-hash sha256:492906d98fbc626748496b7651e0334c366567aa2cdc12d0114015c7d699f005
[preflight] Running pre-flight checks
	[WARNING FileExisting-tc]: tc not found in system path
[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.


[root@node2 ~]# kubeadm join 192.168.80.20:6443 --token k9gbwr.ps0ndo60p8ilh89u \
> --discovery-token-ca-cert-hash sha256:492906d98fbc626748496b7651e0334c366567aa2cdc12d0114015c7d699f005
[preflight] Running pre-flight checks
	[WARNING FileExisting-tc]: tc not found in system path
[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   Ready    control-plane   77m    v1.25.0
node1    Ready    <none>          111s   v1.25.0
node2    Ready    <none>          53s    v1.25.0

容器管理
[root@master ~]# kubectl get ns   //查看所有的名称空间类型
NAME              STATUS   AGE
default           Active   78m
kube-flannel      Active   60m
kube-node-lease   Active   78m
kube-public       Active   78m
kube-system       Active   78m

[root@master ~]# kubectl get pods -n kube-system
NAME                             READY   STATUS    RESTARTS   AGE
coredns-c676cc86f-5mnq4          1/1     Running   0          78m
coredns-c676cc86f-s478t          1/1     Running   0          78m
etcd-master                      1/1     Running   0          79m
kube-apiserver-master            1/1     Running   0          79m
kube-controller-manager-master   1/1     Running   0          79m
kube-proxy-64mdh                 1/1     Running   0          78m
kube-proxy-9xj9n                 1/1     Running   0          2m13s
kube-proxy-ltswd                 1/1     Running   0          3m11s
kube-scheduler-master            1/1     Running   0          79m
//查看现有的容器状态
查看容器的状态的时候要指定名称空间   pods：所有的容器； -n：指定名称空间


[root@master ~]# kubectl get pods -n kube-system -o wide
NAME                             READY   STATUS    RESTARTS   AGE     IP              NODE     NOMINATED NODE   READINESS GATES
coredns-c676cc86f-5mnq4          1/1     Running   0          80m     10.244.0.2      master   <none>           <none>
coredns-c676cc86f-s478t          1/1     Running   0          80m     10.244.0.3      master   <none>           <none>
etcd-master                      1/1     Running   0          80m     192.168.80.20   master   <none>           <none>
kube-apiserver-master            1/1     Running   0          80m     192.168.80.20   master   <none>           <none>
kube-controller-manager-master   1/1     Running   0          80m     192.168.80.20   master   <none>           <none>
kube-proxy-64mdh                 1/1     Running   0          80m     192.168.80.20   master   <none>           <none>
kube-proxy-9xj9n                 1/1     Running   0          3m39s   192.168.80.40   node2    <none>           <none>
kube-proxy-ltswd                 1/1     Running   0          4m37s   192.168.80.30   node1    <none>           <none>
kube-scheduler-master            1/1     Running   0          80m     192.168.80.20   master   <none>           <none>
/查看容器时在那个主机上运行、IP是多少

测试kubernetes集群

在Kubernetes集群中创建一个pod，验证是否正常运行：

[root@master ~]# kubectl create deployment nginx --image=nginx
deployment.apps/nginx created

//创建一个deployment类型的的容器 名字叫nginx 镜像使用nginx

[root@master ~]# kubectl expose deployment nginx --port=80 --type=NodePort
//暴露deployment类型中的nginx  端口号为80 类型为节点端口
//这里的暴露是service的端口号，而且他是有IP的。因为我们访问容器时访问的service的IP地址


[root@master ~]# kubectl get pod,svc
NAME                        READY   STATUS    RESTARTS   AGE
pod/nginx-76d6c9b8c-h2mj2   1/1     Running   0          101s

NAME                 TYPE        CLUSTER-IP       EXTERNAL-IP   PORT(S)        AGE
service/kubernetes   ClusterIP   10.96.0.1        <none>        443/TCP        83m
service/nginx        NodePort    10.103.112.159   <none>        80:31150/TCP   68s
[root@master ~]# curl http://10.103.112.159
<!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>
//访问一下