系统信息

角色 系统 CPU Core memory
master 18.04.1-Ubuntu 4 8G
slave 18.04.1-Ubuntu 4 4G

安装前准备（主节点和从节点都需要执行）

  1. 关闭swap

    1. sudo swapoff -a
    2. sudo  sed -i '/ swap / s/^\(.*\)$/#\1/g' /etc/fstab

  2. 配置系统安装源和kubernetes安装源

    在/etc/apt/sources.list.d/ 追加以下两个文件

    1. cat > /etc/apt/sources.list.d/kubernetes.list << EOF
    2. deb https://mirrors.aliyun.com/kubernetes/apt kubernetes-xenial main
    3. EOF  
    5. cat > /etc/apt/sources.list.d/system.list << EOF
    6. deb http://mirrors.aliyun.com/ubuntu/ bionic main restricted
    7. deb http://mirrors.aliyun.com/ubuntu/ bionic-updates main restricted
    8. deb http://mirrors.aliyun.com/ubuntu/ bionic universe
    9. deb http://mirrors.aliyun.com/ubuntu/ bionic-updates universe
    10. deb http://mirrors.aliyun.com/ubuntu/ bionic multiverse
    11. deb http://mirrors.aliyun.com/ubuntu/ bionic-updates multiverse
    12. deb http://mirrors.aliyun.com/ubuntu/ bionic-backports main restricted universe multiverse
    13. EOF

    执行

    1. sudo apt-get update

  3. 安装依赖工具包

    1. apt install -y curl jq

  4. 安装kubernetes源的安全key

    1. suod curl -s https://mirrors.aliyun.com/kubernetes/apt/doc/apt-key.gpg | sudo apt-key add -

  5. 安装docker

    1. 下载安装包

      containerd.io_1.2.6-3_amd64.deb

      docker-ce-cli_19.03.5_3-0_ubuntu-bionic_amd64.deb

      docker-ce_19.03.5_3-0_ubuntu-bionic_amd64.deb

    2. 使用 sudo dpkg -i 依次安装上面的三个包

    3. 追加docker用户组

      1. sudo groupadd docker

    4. 将当前用户追加到docker用户组

      1. sudo usermod -aG docker $USER

    5. 使用户组生效

      1. newgrp docker

    6. 设置docker开机启动

      1. sudo systemctl enable docker

安装主节点 （在master节点上执行）

  1. 安装kubelet组件

    1. 获取可安装的kubernetes版本号

      1. apt-cache madison kubeadm
      2. apt-cache madison kubelet
      3. apt-cache madison kubectl

      从返回列表中找一个自己要安装的版本号，我们以1.16.3-00为例

    2. 执行如下命令，开始安装

      1. sudo apt install -y kubelet=1.16.3-00 kubeadm=1.16.3-00 kubectl=1.16.3-00

  2. 下载相关镜像

    使用如下命令获取需要的镜像

    1. chengf@chengf:~$ kubeadm config images list
    2. W1126 21:01:07.767448   20606 version.go:101] could not fetch a Kubernetes version from the internet: unable to get URL "https://dl.k8s.io/release/stable-1.txt": Get https://dl.k8s.io/release/stable-1.txt: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)
    3. W1126 21:01:07.767516   20606 version.go:102] falling back to the local client version: v1.16.3
    4. k8s.gcr.io/kube-apiserver:v1.16.3
    5. k8s.gcr.io/kube-controller-manager:v1.16.3
    6. k8s.gcr.io/kube-scheduler:v1.16.3
    7. k8s.gcr.io/kube-proxy:v1.16.3
    8. k8s.gcr.io/pause:3.1
    9. k8s.gcr.io/etcd:3.3.15-0
    10. k8s.gcr.io/coredns:1.6.2

    因为k8s.gcr.io在国内无法访问，所以我们需要提前将这些镜像下载好，并tag成kubernetes需要的镜像名称

    1. chengf@chengf:~$ docker images
    2. REPOSITORY                                TAG                 IMAGE ID            CREATED             SIZE
    3. kubeimage/kube-proxy-amd64                v1.16.3             9b65a0f78b09        13 days ago         86.1MB
    4. k8s.gcr.io/kube-proxy                     v1.16.3             9b65a0f78b09        13 days ago         86.1MB
    5. kubeimage/kube-apiserver-amd64            v1.16.3             df60c7526a3d        13 days ago         217MB
    6. k8s.gcr.io/kube-apiserver                 v1.16.3             df60c7526a3d        13 days ago         217MB
    7. kubeimage/kube-controller-manager-amd64   v1.16.3             bb16442bcd94        13 days ago         163MB
    8. k8s.gcr.io/kube-controller-manager        v1.16.3             bb16442bcd94        13 days ago         163MB
    9. kubeimage/kube-scheduler-amd64            v1.16.3             98fecf43a54f        13 days ago         87.3MB
    10. k8s.gcr.io/kube-scheduler                 v1.16.3             98fecf43a54f        13 days ago         87.3MB
    11. coredns/coredns                           1.6.5               70f311871ae1        2 weeks ago         41.6MB
    12. gcr.azk8s.cn/google_containers/etcd       3.3.15-0            b2756210eeab        2 months ago        247MB
    13. k8s.gcr.io/etcd                           3.3.15-0            b2756210eeab        2 months ago        247MB
    14. coredns/coredns                           1.6.2               bf261d157914        3 months ago        44.1MB
    15. k8s.gcr.io/coredns                        1.6.2               bf261d157914        3 months ago        44.1MB
    16. kubeimage/pause                           3.1                 da86e6ba6ca1        23 months ago       742kB
    17. k8s.gcr.io/pause                          3.1                 da86e6ba6ca1        23 months ago       742kB

  3. 获取默认pod的network范围

    1. chengf@chengf:~$ kubeadm config print init-defaults
    2. apiVersion: kubeadm.k8s.io/v1beta2
    3. bootstrapTokens:
    4. - groups:
    5.   - system:bootstrappers:kubeadm:default-node-token
    6.   token: abcdef.0123456789abcdef
    7.   ttl: 24h0m0s
    8.   usages:
    9.   - signing
    10.   - authentication
    11. kind: InitConfiguration
    12. localAPIEndpoint:
    13.   advertiseAddress: 1.2.3.4
    14.   bindPort: 6443
    15. nodeRegistration:
    16.   criSocket: /var/run/dockershim.sock
    17.   name: chengf
    18.   taints:
    19.   - effect: NoSchedule
    20.     key: node-role.kubernetes.io/master
    21. ---
    22. apiServer:
    23.   timeoutForControlPlane: 4m0s
    24. apiVersion: kubeadm.k8s.io/v1beta2
    25. certificatesDir: /etc/kubernetes/pki
    26. clusterName: kubernetes
    27. controllerManager: {}
    28. dns:
    29.   type: CoreDNS
    30. etcd:
    31.   local:
    32.     dataDir: /var/lib/etcd
    33. imageRepository: k8s.gcr.io
    34. kind: ClusterConfiguration
    35. kubernetesVersion: v1.16.0
    36. networking:
    37.   dnsDomain: cluster.local
    38.   serviceSubnet: 10.96.0.0/12
    39. scheduler: {}

  4. 通过kubeadm init安装master

    1. root@chengf:/etc/kubernetes# kubeadm init --kubernetes-version=v1.16.3 --pod-network-cidr=10.96.0.0/12 --apiserver-advertise-address=192.168.0.107 --node-name=chengf --ignore-preflight-errors=ImagePull
    2. [init] Using Kubernetes version: v1.16.3
    3. [preflight] Running pre-flight checks
    4.     [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/
    5.     [WARNING SystemVerification]: this Docker version is not on the list of validated versions: 19.03.5. Latest validated version: 18.09
    6. [preflight] Pulling images required for setting up a Kubernetes cluster
    7. [preflight] This might take a minute or two, depending on the speed of your internet connection
    8. [preflight] You can also perform this action in beforehand using 'kubeadm config images pull'
    9. [kubelet-start] Writing kubelet environment file with flags to file "/var/lib/kubelet/kubeadm-flags.env"
    10. [kubelet-start] Writing kubelet configuration to file "/var/lib/kubelet/config.yaml"
    11. [kubelet-start] Activating the kubelet service
    12. [certs] Using certificateDir folder "/etc/kubernetes/pki"
    13. [certs] Generating "ca" certificate and key
    14. [certs] Generating "apiserver" certificate and key
    15. [certs] apiserver serving cert is signed for DNS names [chengf kubernetes kubernetes.default kubernetes.default.svc kubernetes.default.svc.cluster.local] and IPs [10.96.0.1 192.168.0.107]
    16. [certs] Generating "apiserver-kubelet-client" certificate and key
    17. [certs] Generating "front-proxy-ca" certificate and key
    18. [certs] Generating "front-proxy-client" certificate and key
    19. [certs] Generating "etcd/ca" certificate and key
    20. [certs] Generating "etcd/server" certificate and key
    21. [certs] etcd/server serving cert is signed for DNS names [chengf localhost] and IPs [192.168.0.107 127.0.0.1 ::1]
    22. [certs] Generating "etcd/peer" certificate and key
    23. [certs] etcd/peer serving cert is signed for DNS names [chengf localhost] and IPs [192.168.0.107 127.0.0.1 ::1]
    24. [certs] Generating "etcd/healthcheck-client" certificate and key
    25. [certs] Generating "apiserver-etcd-client" certificate and key
    26. [certs] Generating "sa" key and public key
    27. [kubeconfig] Using kubeconfig folder "/etc/kubernetes"
    28. [kubeconfig] Writing "admin.conf" kubeconfig file
    29. [kubeconfig] Writing "kubelet.conf" kubeconfig file
    30. [kubeconfig] Writing "controller-manager.conf" kubeconfig file
    31. [kubeconfig] Writing "scheduler.conf" kubeconfig file
    32. [control-plane] Using manifest folder "/etc/kubernetes/manifests"
    33. [control-plane] Creating static Pod manifest for "kube-apiserver"
    34. [control-plane] Creating static Pod manifest for "kube-controller-manager"
    35. [control-plane] Creating static Pod manifest for "kube-scheduler"
    36. [etcd] Creating static Pod manifest for local etcd in "/etc/kubernetes/manifests"
    37. [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
    38. [apiclient] All control plane components are healthy after 17.505256 seconds
    39. [upload-config] Storing the configuration used in ConfigMap "kubeadm-config" in the "kube-system" Namespace
    40. [kubelet] Creating a ConfigMap "kubelet-config-1.16" in namespace kube-system with the configuration for the kubelets in the cluster
    41. [upload-certs] Skipping phase. Please see --upload-certs
    42. [mark-control-plane] Marking the node chengf as control-plane by adding the label "node-role.kubernetes.io/master=''"
    43. [mark-control-plane] Marking the node chengf as control-plane by adding the taints [node-role.kubernetes.io/master:NoSchedule]
    44. [bootstrap-token] Using token: 7zi6wy.j3mm4fzdyxc0m3bx
    45. [bootstrap-token] Configuring bootstrap tokens, cluster-info ConfigMap, RBAC Roles
    46. [bootstrap-token] configured RBAC rules to allow Node Bootstrap tokens to post CSRs in order for nodes to get long term certificate credentials
    47. [bootstrap-token] configured RBAC rules to allow the csrapprover controller automatically approve CSRs from a Node Bootstrap Token
    48. [bootstrap-token] configured RBAC rules to allow certificate rotation for all node client certificates in the cluster
    49. [bootstrap-token] Creating the "cluster-info" ConfigMap in the "kube-public" namespace
    50. [addons] Applied essential addon: CoreDNS
    51. [addons] Applied essential addon: kube-proxy  
    53. Your Kubernetes control-plane has initialized successfully!  
    55. To start using your cluster, you need to run the following as a regular user:  
    57.   mkdir -p $HOME/.kube
    58.   sudo cp -i /etc/kubernetes/admin.conf $HOME/.kube/config
    59.   sudo chown $(id -u):$(id -g) $HOME/.kube/config  
    61. You should now deploy a pod network to the cluster.
    62. Run "kubectl apply -f [podnetwork].yaml" with one of the options listed at:
    63.   https://kubernetes.io/docs/concepts/cluster-administration/addons/  
    65. Then you can join any number of worker nodes by running the following on each as root:  
    67. kubeadm join 192.168.0.107:6443 --token 7zi6wy.j3mm4fzdyxc0m3bx \
    68.     --discovery-token-ca-cert-hash sha256:27e0d9fd7e5e309249cf3a515514e370c230b2115cea5170ec9e5be61c18b2c1
    • kubernetes-version 版本号
    • pod-network-cidr 设置上一步骤中获取的IP范围
    • apiserver-advertise-address 设置成主机IP
    • node-name 主机名称
    • ignore-preflight-errors 忽略拉不到镜像的错误

    安装过程会有如下警告：

    [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: 19.03.5. Latest validated version: 18.09

  5. 按照输出，执行如下命令，使当前普通用户可以执行kubectl命令

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

安装node(在slave节点上执行）

  1. 安装kubelet kubeadm

    1. sudo apt install -y kubelet=1.16.3-00 kubeadm=1.16.3-00
    2. sudo systemctl enable kubelet && systemctl start kubelet

  2. 将从节点加入集群，执行主节点安装完成后生成的加入命令

    1. sudo kubeadm join 192.168.0.107:6443 --token 7zi6wy.j3mm4fzdyxc0m3bx --discovery-token-ca-cert-hash sha256:27e0d9fd7e5e309249cf3a515514e370c230b2115cea5170ec9e5be61c18b2c1

如果加入过程出错了，可以在命令行后面加上 --5来看具体的错误信息

看到如下信息证明加入成功

  1. ```
  2. This node has joined the cluster:
  3. * Certificate signing request was sent to apiserver and a response was received.
  4. * The Kubelet was informed of the new secure connection details. 
  6. Run 'kubectl get nodes' on the control-plane to see this node join the cluster. 
  8. ```

  1. 在master节点上执行

    1. chengf@chengf:~$ kubectl get nodes
    2. NAME     STATUS     ROLES    AGE     VERSION
    3. chengf   NotReady   master   3d23h   v1.16.3
    4. slave    NotReady   <none>   2m43s   v1.16.3

    节点状态为NotReady，这是因为还没有安装CNI网络插件，现在安装下，具体CNI可参考

    CNI,本例选择weave

  2. 在主节点执行

    1. kubectl apply -f "https://cloud.weave.works/k8s/net?k8s-version=$(kubectl version| base64 | tr -d  '\n')"

    如果执行出现如下错误，

    1. chengf@chengf:~$ kubectl apply -f "https://cloud.weave.works/k8s/net?k8s-version=$(kubectl version| base64 | tr -d  '\n')"
    2. Unable to connect to the server: net/http: TLS handshake timeout

    分成三步做

    1. 获取version

      1. chengf@chengf:~$ kubectl version | base64 | tr -d '\n'
      2. Q2xpZW50IFZlcnNpb246IHZlcnNpb24uSW5mb3tNYWpvcjoiMSIsIE1pbm9yOiIxNiIsIEdpdFZlcnNpb246InYxLjE2LjMiLCBHaXRDb21taXQ6ImIzY2JiYWUwOGVjNTJhN2ZjNzNkMzM0ODM4ZTE4ZDE3ZTg1MTI3NDkiLCBHaXRUcmVlU3RhdGU6ImNsZWFuIiwgQnVpbGREYXRlOiIyMDE5LTExLTEzVDExOjIzOjExWiIsIEdvVmVyc2lvbjoiZ28xLjEyLjEyIiwgQ29tcGlsZXI6ImdjIiwgUGxhdGZvcm06ImxpbnV4L2FtZDY0In0KU2VydmVyIFZlcnNpb246IHZlcnNpb24uSW5mb3tNYWpvcjoiMSIsIE1pbm9yOiIxNiIsIEdpdFZlcnNpb246InYxLjE2LjMiLCBHaXRDb21taXQ6ImIzY2JiYWUwOGVjNTJhN2ZjNzNkMzM0ODM4ZTE4ZDE3ZTg1MTI3NDkiLCBHaXRUcmVlU3RhdGU6ImNsZWFuIiwgQnVpbGREYXRlOiIyMDE5LTExLTEzVDExOjEzOjQ5WiIsIEdvVmVyc2lvbjoiZ28xLjEyLjEyIiwgQ29tcGlsZXI6ImdjIiwgUGxhdGZvcm06ImxpbnV4L2FtZDY0In0K

    2. 从浏览器执行

      1. https://cloud.weave.works/k8s/net?k8s-version=Q2xpZW50IFZlcnNpb246IHZlcnNpb24uSW5mb3tNYWpvcjoiMSIsIE1pbm9yOiIxNiIsIEdpdFZlcnNpb246InYxLjE2LjMiLCBHaXRDb21taXQ6ImIzY2JiYWUwOGVjNTJhN2ZjNzNkMzM0ODM4ZTE4ZDE3ZTg1MTI3NDkiLCBHaXRUcmVlU3RhdGU6ImNsZWFuIiwgQnVpbGREYXRlOiIyMDE5LTExLTEzVDExOjIzOjExWiIsIEdvVmVyc2lvbjoiZ28xLjEyLjEyIiwgQ29tcGlsZXI6ImdjIiwgUGxhdGZvcm06ImxpbnV4L2FtZDY0In0KU2VydmVyIFZlcnNpb246IHZlcnNpb24uSW5mb3tNYWpvcjoiMSIsIE1pbm9yOiIxNiIsIEdpdFZlcnNpb246InYxLjE2LjMiLCBHaXRDb21taXQ6ImIzY2JiYWUwOGVjNTJhN2ZjNzNkMzM0ODM4ZTE4ZDE3ZTg1MTI3NDkiLCBHaXRUcmVlU3RhdGU6ImNsZWFuIiwgQnVpbGREYXRlOiIyMDE5LTExLTEzVDExOjEzOjQ5WiIsIEdvVmVyc2lvbjoiZ28xLjEyLjEyIiwgQ29tcGlsZXI6ImdjIiwgUGxhdGZvcm06ImxpbnV4L2FtZDY0In0K

      执行完会下载下来一个net.yaml,传到服务器上

    3. 执行

      1. chengf@chengf:~/soft$ kubectl apply -f net.yaml
      2. serviceaccount/weave-net created
      3. clusterrole.rbac.authorization.k8s.io/weave-net created
      4. clusterrolebinding.rbac.authorization.k8s.io/weave-net created
      5. role.rbac.authorization.k8s.io/weave-net created
      6. rolebinding.rbac.authorization.k8s.io/weave-net created
      7. daemonset.apps/weave-net created

  3. 再次确认节点状态

    1. chengf@chengf:~/soft$ kubectl get nodes
    2. NAME     STATUS     ROLES    AGE     VERSION
    3. chengf   Ready      master   3d23h   v1.16.3
    4. slave    NotReady   <none>   40m     v1.16.3  
    6. chengf@chengf:~/soft$ kubectl get pods --all-namespaces
    7. NAMESPACE     NAME                             READY   STATUS              RESTARTS   AGE
    8. kube-system   coredns-5644d7b6d9-gdjwp         1/1     Running             0          3d23h
    9. kube-system   coredns-5644d7b6d9-s9l76         1/1     Running             0          3d23h
    10. kube-system   etcd-chengf                      1/1     Running             0          3d23h
    11. kube-system   kube-apiserver-chengf            1/1     Running             6          3d23h
    12. kube-system   kube-controller-manager-chengf   1/1     Running             6          3d23h
    13. kube-system   kube-proxy-g7f6j                 1/1     Running             0          3d23h
    14. kube-system   kube-proxy-nljf6                 0/1     ContainerCreating   0          42m
    15. kube-system   kube-scheduler-chengf            1/1     Running             7          3d23h
    16. kube-system   weave-net-7zbps                  2/2     Running             0          7m31s
    17. kube-system   weave-net-kt2rz                  0/2     ContainerCreating   0          7m31s

    发现weave-net-kt2rz没有启动起来，查看原因

    1. kubectl --namespace=kube-system describe pod weave-net-kt2rz 
    3. Failed create pod sandbox: rpc error: code = Unknown desc = failed pulling image "k8s.gcr.io/pause:3.1": Error response from daemon: Get https://k8s.gcr.io/v2/: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)

    是下不下来镜像k8s.gcr.io/pause:3.1，解决方法

    1. chengf@slave:~/soft$ docker pull kubeimage/pause:3.1
    2. Pulling from kubeimage/pause
    3. Image docker.io/kubeimage/pause:3.1 uses outdated schema1 manifest format. Please upgrade to a schema2 image for better future compatibility. More information at https://docs.docker.com/registry/spec/deprecated-schema-v1/
    4. 7675586df687: Pull complete
    5. Digest: sha256:c780ae1f699e27c67bb6f1ac38f9b0a576a9d22c862aaae0d3549b6000569958
    6. Status: Downloaded newer image for kubeimage/pause:3.1
    7. docker.io/kubeimage/pause:3.1
    8. chengf@slave:~/soft$ docker tag kubeimage/pause:3.1 k8s.gcr.io/pause:3.1

    如果还有错误，可以一一排查，直到问题解决 ,最终结果

    1. chengf@chengf:~/soft$ kubectl get pods --all-namespaces
    2. NAMESPACE     NAME                             READY   STATUS    RESTARTS   AGE
    3. kube-system   coredns-5644d7b6d9-gdjwp         1/1     Running   0          3d23h
    4. kube-system   coredns-5644d7b6d9-s9l76         1/1     Running   0          3d23h
    5. kube-system   etcd-chengf                      1/1     Running   0          3d23h
    6. kube-system   kube-apiserver-chengf            1/1     Running   6          3d23h
    7. kube-system   kube-controller-manager-chengf   1/1     Running   6          3d23h
    8. kube-system   kube-proxy-g7f6j                 1/1     Running   0          3d23h
    9. kube-system   kube-proxy-nljf6                 1/1     Running   0          56m
    10. kube-system   kube-scheduler-chengf            1/1     Running   7          3d23h
    11. kube-system   weave-net-7zbps                  2/2     Running   0          21m
    12. kube-system   weave-net-kt2rz                  2/2     Running   6          21m

这样通过kubeadm工具就实现了kubernetes集群的搭建，如果集群安装失败，可以通过kubeadm reset命令恢复主机，之后再重新安装

kubernetes安装-kubeadm的更多相关文章

  1. kubernetes之Kubeadm快速安装v1.12.0版

    通过Kubeadm只需几条命令即起一个单机版kubernetes集群系统,而后快速上手k8s.在kubeadm中,需手动安装Docker和kubeket服务,Docker运行容器引擎,kubelet是 ...

  2. centos7安装kubeadm

    安装配置docker v1.9.0版本推荐使用docker v1.12, v1.11, v1.13, 17.03也可以使用,再高版本的docker可能无法正常使用. 测试发现17.09无法正常使用,不 ...

  3. 轻松加愉快的 Kubernetes 安装教程

    轻松加愉快的 Kubernetes 安装教程 马哥Linux运维 2 days ago 作者:无聊的学习者 来源:见文末 在国内安装 K8S,一直是大家很头痛的问题,各种麻烦,关键是还不知道需要下载什 ...

  4. kubernetes安装-二进制

    主要参考https://github.com/opsnull/follow-me-install-kubernetes-cluster,采用Flanel和docker 系统信息 角色 系统 CPU C ...

  5. 服务网格Istio入门-详细记录Kubernetes安装Istio并使用

    我最新最全的文章都在南瓜慢说 www.pkslow.com,文章更新也只在官网,欢迎大家来喝茶~~ 1 服务网格Istio Istio是开源的Service Mesh实现,一般用于Kubernetes ...

  6. Kubernetes 使用kubeadm创建集群

    镜像下载.域名解析.时间同步请点击 阿里巴巴开源镜像站 实践环境 CentOS-7-x86_64-DVD-1810 Docker 19.03.9 Kubernetes version: v1.20.5 ...

  7. Docker系列(九)Kubernetes安装

    环境: A.B两天机器A机器IP:192.169.0.104,B机器IP:192.168.0.102,其中A为Master节点,B为Slave节点 操作系统:Centos7 Master与Slave节 ...

  8. Kuboard Kubernetes安装

    一.简介 Kubernetes 容器编排已越来越被大家关注,然而使用 Kubernetes 的门槛却依然很高,主要体现在这几个方面: 集群的安装复杂,出错概率大 Kubernetes相较于容器化,引入 ...

  9. kubernetes之kubeadm 安装kubernetes 高可用集群

    1. 架构信息 系统版本:CentOS 7.6 内核:3.10.0-957.el7.x86_64 Kubernetes: v1.14.1 Docker-ce: 18.09.5 推荐硬件配置:4核8G ...

随机推荐

  1. Tangram: Optimized Coarse-Grained Dataflow for Scalable NN Accelerators 阅读笔记

    目录 Tangram: Optimized Coarse-Grained Dataflow for Scalable NN Accelerators 1.Abstract 2.Introduction ...

  2. acwing 1250. 格子游戏 并查集

    地址 https://www.acwing.com/problem/content/1252/ Alice和Bob玩了一个古老的游戏:首先画一个 n×nn×n 的点阵(下图 n=3n=3 ). 接着, ...

  3. 使用Selenium对网页元素进行定位的诸种方法

    使用Selenium进行自动化操作,首先要做的就是通过webdriver的get()方法打开一个URL链接. 在打开链接,完成页面加载之后,就可以通过Selenium提供的接口,在页面上进行各种操作了 ...

  4. 预告:Windows 7 + Tiny Linux 4.19 + XFS + Vmware Workstation 15 (PRO)下篇dockerの奥义

    困 困 等明天再写吧 主题将围绕在Vmware使用持久化XFS disk后machine rm default后不丢失images containers volumes etc.的奇观 并将展开部署c ...

  5. vue入门，vue指令，vue组件，vue模板

    vue 使用虚拟dom操作减少真实dom操作 提高页面的渲染效率 虚拟dom的本质就是内存中的一个对象,该对象和dom结构相互对应 将开发者经历从dom中释放出来,转移到数据的操作 开发者不需要关注页 ...

  6. 个性化重排--Personalized Re-ranking for Recommendation

    推荐中的个性化重排--Personalized Re-ranking for Recommendation 这篇文章是阿里在ResSys'19发表的,主要贡献是在重排序阶段,引入了用户的相关信息,很符 ...

  7. vim的常用指令（脑图）

    将正在编辑的文件另存新文件名   :w newfilename 在正在编辑的文件中,读取一个filename    :r filename 做了很多编辑工作,想还原成原来的文件内容   :e! 我在v ...

  8. [JavaScript设计模式] 什么是单例模式

    概念 保证一个类仅有一个实例,并提供一个全局访问点 为什么要用单例模式 想象一下某些web应用,当点击登录按钮时,会弹出一个登录框,无论你点击多少次这个登录按钮,登录框都只会出现一个,不会出现多个登录 ...

  9. 公司没有 DBA，Mysql 运维自己来

    如果你的公司有 DBA,那么我恭喜你,你可以无视 Mysql 运维.如果你的公司没有 DBA,那你就好好学两手 Mysql 基本运维操作,行走江湖,防身必备. 环境:CentOS7 版本: 一.虚拟机 ...

  10. Spring Boot2 系列教程 (六) | 使用 JdbcTemplates 访问 Mysql

    前言 如题,今天介绍 springboot 通过jdbc访问关系型mysql,通过 spring 的 JdbcTemplate 去访问. 准备工作 SpringBoot 2.x jdk 1.8 mav ...