部署k8s集群步骤 kubernetes实施步骤

admin · 发表于 2024-9-2 15:00:03

购买主题本主题需向作者支付 5 金钱 才能浏览

admin · 发表于 2024-9-6 17:37:32

kubernetes的yum源
cat > /etc/yum.repos.d/kubernetes.repo <<EOF
[kubernetes]
name=kubernetes
baseurl=http://172.24.21.35/centos/kubernetes/
gpgcheck=0
EOF

admin · 发表于 2024-9-9 10:37:01

kubeadm init --apiserver-advertise-address=172.24.21.55 --image-repository registry.aliyuncs.com/google_containers --kubernetes-version v1.28.0 --service-cidr=10.177.100.0/12 --pod-network-cidr=10.233.0.0/16 --cri-socket=unix:///var/run/cri-dockerd.sock [init] Using Kubernetes version: v1.28.0 [preflight] Running pre-flight checks [WARNING Firewalld]: firewalld is active, please ensure ports [6443 10250] are open or your cluster may not function correctly [WARNING HTTPProxy]: Connection to "https://172.24.21.55" uses proxy "http://172.24.118.199:3128". If that is not intended, adjust your proxy settings [WARNING HTTPProxyCIDR]: connection to "10.177.100.0/12" uses proxy "http://172.24.118.199:3128". This may lead to malfunctional cluster setup. Make sure that Pod and Services IP ranges specified correctly as exceptions in proxy configuration [WARNING HTTPProxyCIDR]: connection to "10.233.0.0/16" uses proxy "http://172.24.118.199:3128". This may lead to malfunctional cluster setup. Make sure that Pod and Services IP ranges specified correctly as exceptions in proxy configuration [WARNING Hostname]: hostname "k8s-master" could not be reached [WARNING Hostname]: hostname "k8s-master": lookup k8s-master on 114.114.114.114:53: read udp 172.24.21.55:51870->114.114.114.114:53: i/o timeout [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'

admin · 发表于 2024-9-9 10:42:18

--apiserver-advertise-address #声明监听ip地址
--image-repository registry.aliyuncs.com/google_containers #指定仓库
--kubernetes-version 指定k8s的版本

--service-cidr=10.177.100.0/12 #service网段
--pod-network-cidr=10.233.0.0/16 #pod网段
--cri-socket 指定docker的中间链接软件

admin · 发表于 2024-9-10 15:57:57

--kubernetes-version=v1.17.2

版本号，根据自己的情况更改，一般应该和 kubeadm 的版本一致

通过如下命令获得

kubeadm version

输出的 GitVersion:"v1.20.4" 就是版本号了

--pod-network-cidr=10.244.0.0/16

pod 使用的网络，可以自定义，这个根据自己的情况修改，不修改也可以

好像是固定的

--apiserver-advertise-address=192.168.1.200
master 节点的有效 IP 或者可以被解析的 DNS 名称，需要是 master 节点的有效网卡地址，比如 ens33, eth0 等。

--ignore-preflight-errors=Swap
忽略检查 Swap 时候的报错

--control-plane-endpoint

负载均衡的地址，支持dns解析名或者IP，添加该选项后支持高可用，如果使用dns 记得该dns一定要可以被解析

--upload-certs

配合高可用使用，可以自动上传证书

admin · 发表于 2024-9-10 17:12:32

vim deploy-kubeadm.yml
---
- name: Deploy  kubeadm  kubelet kubectl
  hosts: k8s
  gather_facts: no
  vars:
pkg_dir: /kubeadm-pkg
pkg_names: ["kubelet", "kubeadm", "kubectl"]

# 变量 download_host 需要手动设置
# 且值需要是此 playbook 目标主机中的一个
# 需要写在 inventory 文件中的名称
download_host: "master"
local_pkg_dir: "{{ playbook_dir }}/{{ download_host }}"

  tasks:
- name: 测试使用 -e 是否设置并覆盖了变量
   debug:
      msg: "{{ local_pkg_dir }} {{ download_host }}"
   tags:
      - deploy
      - test

- name: "只需要给 {{ download_host }}安装仓库文件"
   when: inventory_hostname == download_host
   copy:
      src: file/kubernetes.repo
      dest: /etc/yum.repos.d/kubernetes.repo
   tags:
      - deploy

- name: 创建存放 rmp 包的目录
   when: inventory_hostname == download_host
   file:
      path: "{{ pkg_dir }}"
      state: directory
   tags:
      - deploy

- name:  下载软件包
   when: inventory_hostname == download_host
   yum:
      name: "{{ pkg_names }}"
      download_only: yes
      download_dir: "{{ pkg_dir }}"
   tags:
      - deploy

- name: 获取下载目录 "{{ pkg_dir }}" 中的文件列表
   when: inventory_hostname == download_host
   shell: ls -1 "{{ pkg_dir }}"
   register: files
   tags:
      - deploy

- name: 把远程主机下载的软件包传输到 ansible 本地
   when: inventory_hostname == download_host
   fetch:
      src: "{{ pkg_dir }}/{{ item }}"
      dest: ./
   loop: "{{files.stdout_lines}}"
   tags:
      - deploy

- name: 传输 rpm 包到远程节点
   when: inventory_hostname != download_host
   copy:
      src: "{{ local_pkg_dir }}{{ pkg_dir }}"
      dest: "/"
   tags:
      - deploy

- name: 正在执行从本地安装软件包
   shell:
      cmd: yum -y localinstall *
      chdir: "{{ pkg_dir }}"
      warn: no
   async: 600
   poll: 0
   register: yum_info
   tags:
      - deploy

- name: 打印安装结果
   debug: var=yum_info.ansible_job_id
   tags:
      - deploy

# 查看kubernetes依赖的镜像
kubeadm config images list

# 不支持高可用的集群初始化
kubeadm init --kubernetes-version=v1.20.4 --pod-network-cidr=10.244.0.0/16 --apiserver-advertise-address=10.9.29.112 --ignore-preflight-errors=Swap

# 支持高可用的集群初始化
kubeadm init --kubernetes-version=v1.20.4 --pod-network-cidr=10.244.0.0/16 --apiserver-advertise-address=masterIP --control-plane-endpoint=kube-lab  --ignore-preflight-errors=Swap --upload-certs

# 初始化成功后，会有以下信息，复制后直接在node节点使用即可加入集群
kubeadm join 10.9.29.112:6443 --token en6s67.08rnsg20dc5t8z4n \
--discovery-token-ca-cert-hash sha256:7d034842b9ee7a6b17d9ce7088839f4570da1c61b29922f28e72b855c10003cc

# 如果是高可用，还会有一条，这个使用后会添加一个master进入集群
kubeadm join kub-lab:6443 --token s2ccws.tzb7v4olicidp032 \
--discovery-token-ca-cert-hash sha256:29a2b437f79c5e4958c3d73e6c64fe0a4df24f0f3bcabd5ced28392d7a882e10 \
--control-plane --certificate-key c0a9a1c4a067b20dca95447f809d95c973220244c740a47f71d5302e0a759ea7

1320503165 · 发表于 2024-9-14 11:01:25

cat > /etc/docker/daemon.json <<EOF
{
"registry-mirrors":[
"https://docker.m.daocloud.io",
"https://huecher.io",
"https://dockerhub.timeweb.cloud",
"https://noohub.ru",
"https://docker.aws19527.cn"
]
}
EOF

1320503165 · 发表于 2024-9-14 17:07:25

kubeadm init --apiserver-advertise-address=192.168.8.190 --image-repository registry.aliyuncs.com/google_containers --kubernetes-version v1.28.0 --service-cidr=10.177.100.0/12 --pod-network-cidr=10.233.0.0/16 --cri-socket=unix:///var/run/cri-dockerd.sock
[init] Using Kubernetes version: v1.28.0
[preflight] Running pre-flight checks
[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'
W0914 17:05:50.073955 7690 checks.go:835] detected that the sandbox image "registry.k8s.io/pause:3.6" of the container runtime is inconsistent with that used by kubeadm. It is recommended that using "registry.aliyuncs.com/google_containers/pause:3.9" as the CRI sandbox image.
[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-master kubernetes.default kubernetes.default.svc kubernetes.default.svc.cluster.local] and IPs [10.176.0.1 192.168.8.190]
[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 [kubernetes-master localhost] and IPs [192.168.8.190 127.0.0.1 ::1]
[certs] Generating "etcd/peer" certificate and key
[certs] etcd/peer serving cert is signed for DNS names [kubernetes-master localhost] and IPs [192.168.8.190 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
[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
[kubelet-check] Initial timeout of 40s passed.

1320503165 · 发表于 2024-9-15 10:54:27

[root@kubernetes-master net]# kubeadm init --apiserver-advertise-address=192.168.8.190  --image-repository registry.aliyuncs.com/google_containers  --kubernetes-version v1.28.0 --service-cidr=10.177.100.0/12 --pod-network-cidr=10.233.0.0/16  --cri-socket=unix:///var/run/cri-dockerd.sock
[init] Using Kubernetes version: v1.28.0
[preflight] Running pre-flight checks
[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-master kubernetes.default kubernetes.default.svc kubernetes.default.svc.cluster.local] and IPs [10.176.0.1 192.168.8.190]
[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 [kubernetes-master localhost] and IPs [192.168.8.190 127.0.0.1 ::1]
[certs] Generating "etcd/peer" certificate and key
[certs] etcd/peer serving cert is signed for DNS names [kubernetes-master localhost] and IPs [192.168.8.190 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
[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 17.005335 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 kubernetes-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 kubernetes-master as control-plane by adding the taints [node-role.kubernetes.io/control-plane:NoSchedule]
[bootstrap-token] Using token: ajiqtj.xwpscuol7csse0d9
[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/conce ... inistration/addons/

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

kubeadm join 192.168.8.190:6443 --token ajiqtj.xwpscuol7csse0d9 \
--discovery-token-ca-cert-hash sha256:87ab51d4f77f290e00c0060990eb5efa886752e39b2e74721d96d2c41bb92699
[root@kubernetes-master net]#

admin · 发表于 2024-9-15 15:03:28

# 安装ipset和ipvsadm
      yum install ipset ipvsadmin -y
# 添加需要加载的模块写入脚本文件
cat <<EOF > /etc/sysconfig/modules/ipvs.modules
#!/bin/bash
modprobe -- ip_vs
modprobe -- ip_vs_rr
modprobe -- ip_vs_wrr
modprobe -- ip_vs_sh
modprobe -- nf_conntrack_ipv4
EOF
# 为脚本文件添加执行权限
      chmod +x /etc/sysconfig/modules/ipvs.modules
# 执行脚本文件
      /bin/bash /etc/sysconfig/modules/ipvs.modules
# 查看对应的模块是否加载成功
      lsmod | grep -e ip_vs -e nf_conntrack_ipv4

账号		自动登录	找回密码
密码			开始注册

部署k8s集群步骤 kubernetes实施步骤

浏览过的版块

站长推荐 /4

admin admin 当前在线积分 16843 在线时间小时最后登录 1970-1-1 窥视卡雷达卡	发表于 2024-9-2 15:00:03 \| 显示全部楼层 \|阅读模式购买主题本主题需向作者支付 5 金钱才能浏览

	回复使用道具举报提升卡置顶卡沉默卡喧嚣卡变色卡千斤顶照妖镜