Kubernetes集群初始配置

最新推荐文章于 2024-08-11 03:23:17 发布
最新推荐文章于 2024-08-11 03:23:17 发布
阅读量834 收藏 2
点赞数
文章标签： kubernetes docker
版权声明：本文为博主原创文章，遵循 CC 4.0 BY-SA 版权协议，转载请附上原文出处链接和本声明。
本文链接：https://blog.csdn.net/Ricost/article/details/108765867
版权

配置IP

Ubuntu 18 修改IPvi /etc/netplan/50-cloud-init.yaml

network:
    ethernets:
        ens33:
          addresses: [192.168.141.110/24]
          gateway4: 192.168.141.2
          nameservers:
            addresses: [192.168.141.2]
    version: 2

指令生效：netplan apply

配置主机名

修改主机名

hostnamectl set-hostname you-computer-name

配置 hosts

cat >> /etc/hosts << EOF
192.168.123.110 you-computer-name
EOF

服务器信息

服务主机名IP/端口CPU/MEM说明
GitLabdocker-gitlab192.168.141.200:802 核 2G代码管理
Nexusdocker-nexus192.168.141.201:802 核 2G依赖管理
Harbordocker-harbor192.168.141.202:802 核 2G镜像管理
ZenTaodocker-zentao192.168.141.203:802 核 2G项目管理
主机名IP角色CPU/MEM磁盘
kubernetes-master192.168.141.110Master2 核 2G20G
kubernetes-node-01192.168.141.120Node2 核 4G20G
kubernetes-node-02192.168.141.121Node2 核 4G20G
kubernetes-node-03192.168.141.122Node2 核 4G20G
kubernetes-volumes192.168.141.130NFS2 核 2G按需扩容

Master

工作目录

/usr/local/kubernetes/cluster

# 导出配置文件
kubeadm config print init-defaults --kubeconfig ClusterConfiguration > kubeadm.yml

修改配置

apiVersion: kubeadm.k8s.io/v1beta2
bootstrapTokens:
- groups:
  - system:bootstrappers:kubeadm:default-node-token
  token: abcdef.0123456789abcdef
  ttl: 24h0m0s
  usages:
  - signing
  - authentication
kind: InitConfiguration
localAPIEndpoint:
  # 修改为主节点 IP
  advertiseAddress: 192.168.141.110
  bindPort: 6443
nodeRegistration:
  criSocket: /var/run/dockershim.sock
  name: kubernetes-master
  taints:
  - effect: NoSchedule
    key: node-role.kubernetes.io/master
---
apiServer:
  timeoutForControlPlane: 4m0s
apiVersion: kubeadm.k8s.io/v1beta2
certificatesDir: /etc/kubernetes/pki
clusterName: kubernetes
controllerManager: {}
dns:
  type: CoreDNS
etcd:
  local:
    dataDir: /var/lib/etcd
# 国内不能访问 Google，修改为阿里云
imageRepository: registry.aliyuncs.com/google_containers
kind: ClusterConfiguration
# 修改版本号
kubernetesVersion: v1.15.0
networking:
  dnsDomain: cluster.local
  # 配置 POD 所在网段为我们虚拟机不重叠的网段（这里用的是 Flannel 默认网段）
  podSubnet: "10.244.0.0/16"
  serviceSubnet: 10.96.0.0/12
scheduler: {}

查看所需镜像

kubeadm config images list --config kubeadm.yml

拉取镜像

配置结点

kubeadm init --config=kubeadm.yml --upload-certs | tee kubeadm-init.log

配置 kubectl

mkdir -p $HOME/.kube
cp -i /etc/kubernetes/admin.conf $HOME/.kube/config

加入结点

#master执行创建token
kubeadm token create 
#master执行查看token
kubeadm token list 
#mater执行创建sha256
openssl x509 -pubkey -in /etc/kubernetes/pki/ca.crt | openssl rsa -pubin -outform der 2>/dev/null | openssl dgst -sha256 -hex | sed 's/^.* //' 
kubeadm join 10.10.44.161:6443 --token 54fd3m.d2ck6x78ocljcp1y --discovery-token-ca-cert-hash sha256:2dd957bc218a766d87ba421a557140303bd2c22a6172bd123642dc2b9009a4cc

输出

# 输出如下
[preflight] Running pre-flight checks
[preflight] Reading configuration from the cluster...
[preflight] FYI: You can look at this config file with 'kubectl -n kube-system get cm kubeadm-config -oyaml'
[kubelet-start] Downloading configuration for the kubelet from the "kubelet-config-1.17" ConfigMap in the kube-system namespace
[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.

查看Pod

kubectl get pod -n kube-system -o wide

NAME                                        READY   STATUS    RESTARTS   AGE     IP                NODE                 NOMINATED NODE   READINESS GATES
coredns-9d85f5447-jdz27                     0/1     Pending   0          27m     <none>            <none>               <none>           <none>
coredns-9d85f5447-sh2fc                     0/1     Pending   0          27m     <none>            <none>               <none>           <none>
etcd-kubernetes-master                      1/1     Running   0          27m     192.168.123.110   kubernetes-master    <none>           <none>
kube-apiserver-kubernetes-master            1/1     Running   0          27m     192.168.123.110   kubernetes-master    <none>           <none>
kube-controller-manager-kubernetes-master   1/1     Running   0          27m     192.168.123.110   kubernetes-master    <none>           <none>
kube-proxy-8pcvf                            1/1     Running   0          2m10s   192.168.123.122   kubernetes-node-03   <none>           <none>
kube-proxy-s6cq7                            1/1     Running   0          21m     192.168.123.120   kubernetes-node-01   <none>           <none>
kube-proxy-tdr2l                            1/1     Running   0          5m52s   192.168.123.121   kubernetes-node-02   <none>           <none>
kube-proxy-z95pn                            1/1     Running   0          27m     192.168.123.110   kubernetes-master    <none>           <none>
kube-scheduler-kubernetes-master            1/1     Running   0          27m     192.168.123.110   kubernetes-master    <none>           <none>

安装插件Calico

工作目录

/usr/local/kubernetes/cluster

下载 Calico 配置文件并修改

wget https://docs.projectcalico.org/v3.8/manifests/calico.yaml

修改配置文件

vi calico.yaml

192.168.0.0/16 修改为 10.244.0.0/16

- name: CALICO_IPV4POOL_CIDR
  value: "10.244.0.0/16" 


# The default IPv4 pool to create on startup if none exists. Pod IPs will be
# chosen from this range. Changing this value after installation will have
# no effect. This should fall within `--cluster-cidr`.
- name: CALICO_IPV4POOL_CIDR
  value: "10.244.0.0/16" 
# Disable file logging so `kubectl logs` works.
- name: CALICO_DISABLE_FILE_LOGGING
  value: "true"
# Set Felix endpoint to host default action to ACCEPT.
- name: FELIX_DEFAULTENDPOINTTOHOSTACTION
  value: "ACCEPT"
# Disable IPv6 on Kubernetes.

部署calico

kubectl apply -f calico.yaml

查看pod状态

watch kubectl get pods --all-namespaces

NAMESPACE     NAME                                        READY   STATUS    RESTARTS   AGE
kube-system   calico-kube-controllers-bc44d789c-f6rl7     1/1     Running   0          15m
kube-system   calico-node-ch885                           1/1     Running   0          15m
kube-system   calico-node-cs8jb                           1/1     Running   0          15m
kube-system   calico-node-g5bcb                           1/1     Running   0          15m
kube-system   calico-node-mddc5                           1/1     Running   0          15m
kube-system   coredns-9d85f5447-jdz27                     1/1     Running   0          59m
kube-system   coredns-9d85f5447-sh2fc                     1/1     Running   0          59m
kube-system   etcd-kubernetes-master                      1/1     Running   0          59m
kube-system   kube-apiserver-kubernetes-master            1/1     Running   0          59m
kube-system   kube-controller-manager-kubernetes-master   1/1     Running   0          59m
kube-system   kube-proxy-8pcvf                            1/1     Running   0          33m
kube-system   kube-proxy-s6cq7                            1/1     Running   0          53m
kube-system   kube-proxy-tdr2l                            1/1     Running   0          37m
kube-system   kube-proxy-z95pn                            1/1     Running   0          59m
kube-system   kube-scheduler-kubernetes-master            1/1     Running   0          59m

查看结点状态

kubectl get node

NAME                 STATUS   ROLES    AGE   VERSION
kubernetes-master    Ready    master   60m   v1.17.4
kubernetes-node-01   Ready    <none>   54m   v1.17.4
kubernetes-node-02   Ready    <none>   38m   v1.17.4
kubernetes-node-03   Ready    <none>   34m   v1.17.4

重置Kubernetes

重置指令

sudo kubeadm reset

输出

[reset] Reading configuration from the cluster...
[reset] FYI: You can look at this config file with 'kubectl -n kube-system get cm kubeadm-config -oyaml'
[reset] WARNING: Changes made to this host by 'kubeadm init' or 'kubeadm join' will be reverted.
[reset] Are you sure you want to proceed? [y/N]: y
[preflight] Running pre-flight checks
[reset] Removing info for node "kubernetes-master" from the ConfigMap "kubeadm-config" in the "kube-system" Namespace
W0410 21:07:15.789401   71480 removeetcdmember.go:61] [reset] failed to remove etcd member: error syncing endpoints with etc: etcdclient: no available endpoints
.Please manually remove this etcd member using etcdctl
[reset] Stopping the kubelet service
[reset] Unmounting mounted directories in "/var/lib/kubelet"
[reset] Deleting contents of config directories: [/etc/kubernetes/manifests /etc/kubernetes/pki]
[reset] Deleting files: [/etc/kubernetes/admin.conf /etc/kubernetes/kubelet.conf /etc/kubernetes/bootstrap-kubelet.conf /etc/kubernetes/controller-manager.conf /etc/kubernetes/scheduler.conf]
[reset] Deleting contents of stateful directories: [/var/lib/etcd /var/lib/kubelet /var/lib/dockershim /var/run/kubernetes /var/lib/cni]

The reset process does not clean CNI configuration. To do so, you must remove /etc/cni/net.d

The reset process does not reset or clean up iptables rules or IPVS tables.
If you wish to reset iptables, you must do so manually by using the "iptables" command.

If your cluster was setup to utilize IPVS, run ipvsadm --clear (or similar)
to reset your system's IPVS tables.

The reset process does not clean your kubeconfig files and you must remove them manually.
Please, check the contents of the $HOME/.kube/config file.

重置iptables

iptables -F && iptables -t nat -F && iptables -t mangle -F && iptables -X
sysctl net.bridge.bridge-nf-call-iptables=1

手动执行以下命令来清楚对应的残余网卡信息

sudo ip link del cni0
sudo ip link del flannel.1

Node NotReady

systemctl restart kube-proxy
systemctl restart kubelet

Master NotReady

systemctl restart kubelet
```# 配置IP
Ubuntu 18 修改IP`vi /etc/netplan/50-cloud-init.yaml`
```YML
network:
    ethernets:
        ens33:
          addresses: [192.168.141.110/24]
          gateway4: 192.168.141.2
          nameservers:
            addresses: [192.168.141.2]
    version: 2

指令生效：netplan apply

配置主机名

修改主机名

hostnamectl set-hostname you-computer-name

配置 hosts

cat >> /etc/hosts << EOF
192.168.123.110 you-computer-name
EOF

服务器信息

服务主机名IP/端口CPU/MEM说明
GitLabdocker-gitlab192.168.141.200:802 核 2G代码管理
Nexusdocker-nexus192.168.141.201:802 核 2G依赖管理
Harbordocker-harbor192.168.141.202:802 核 2G镜像管理
ZenTaodocker-zentao192.168.141.203:802 核 2G项目管理
主机名IP角色CPU/MEM磁盘
kubernetes-master192.168.141.110Master2 核 2G20G
kubernetes-node-01192.168.141.120Node2 核 4G20G
kubernetes-node-02192.168.141.121Node2 核 4G20G
kubernetes-node-03192.168.141.122Node2 核 4G20G
kubernetes-volumes192.168.141.130NFS2 核 2G按需扩容

Master

工作目录

/usr/local/kubernetes/cluster

# 导出配置文件
kubeadm config print init-defaults --kubeconfig ClusterConfiguration > kubeadm.yml

修改配置

apiVersion: kubeadm.k8s.io/v1beta2
bootstrapTokens:
- groups:
  - system:bootstrappers:kubeadm:default-node-token
  token: abcdef.0123456789abcdef
  ttl: 24h0m0s
  usages:
  - signing
  - authentication
kind: InitConfiguration
localAPIEndpoint:
  # 修改为主节点 IP
  advertiseAddress: 192.168.141.110
  bindPort: 6443
nodeRegistration:
  criSocket: /var/run/dockershim.sock
  name: kubernetes-master
  taints:
  - effect: NoSchedule
    key: node-role.kubernetes.io/master
---
apiServer:
  timeoutForControlPlane: 4m0s
apiVersion: kubeadm.k8s.io/v1beta2
certificatesDir: /etc/kubernetes/pki
clusterName: kubernetes
controllerManager: {}
dns:
  type: CoreDNS
etcd:
  local:
    dataDir: /var/lib/etcd
# 国内不能访问 Google，修改为阿里云
imageRepository: registry.aliyuncs.com/google_containers
kind: ClusterConfiguration
# 修改版本号
kubernetesVersion: v1.15.0
networking:
  dnsDomain: cluster.local
  # 配置 POD 所在网段为我们虚拟机不重叠的网段（这里用的是 Flannel 默认网段）
  podSubnet: "10.244.0.0/16"
  serviceSubnet: 10.96.0.0/12
scheduler: {}

查看所需镜像

kubeadm config images list --config kubeadm.yml

拉取镜像

配置结点

kubeadm init --config=kubeadm.yml --upload-certs | tee kubeadm-init.log

配置 kubectl

mkdir -p $HOME/.kube
cp -i /etc/kubernetes/admin.conf $HOME/.kube/config

加入结点

#master执行创建token
kubeadm token create 
#master执行查看token
kubeadm token list 
#mater执行创建sha256
openssl x509 -pubkey -in /etc/kubernetes/pki/ca.crt | openssl rsa -pubin -outform der 2>/dev/null | openssl dgst -sha256 -hex | sed 's/^.* //' 
kubeadm join 10.10.44.161:6443 --token 54fd3m.d2ck6x78ocljcp1y --discovery-token-ca-cert-hash sha256:2dd957bc218a766d87ba421a557140303bd2c22a6172bd123642dc2b9009a4cc

输出

# 输出如下
[preflight] Running pre-flight checks
[preflight] Reading configuration from the cluster...
[preflight] FYI: You can look at this config file with 'kubectl -n kube-system get cm kubeadm-config -oyaml'
[kubelet-start] Downloading configuration for the kubelet from the "kubelet-config-1.17" ConfigMap in the kube-system namespace
[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.

查看Pod

kubectl get pod -n kube-system -o wide

NAME                                        READY   STATUS    RESTARTS   AGE     IP                NODE                 NOMINATED NODE   READINESS GATES
coredns-9d85f5447-jdz27                     0/1     Pending   0          27m     <none>            <none>               <none>           <none>
coredns-9d85f5447-sh2fc                     0/1     Pending   0          27m     <none>            <none>               <none>           <none>
etcd-kubernetes-master                      1/1     Running   0          27m     192.168.123.110   kubernetes-master    <none>           <none>
kube-apiserver-kubernetes-master            1/1     Running   0          27m     192.168.123.110   kubernetes-master    <none>           <none>
kube-controller-manager-kubernetes-master   1/1     Running   0          27m     192.168.123.110   kubernetes-master    <none>           <none>
kube-proxy-8pcvf                            1/1     Running   0          2m10s   192.168.123.122   kubernetes-node-03   <none>           <none>
kube-proxy-s6cq7                            1/1     Running   0          21m     192.168.123.120   kubernetes-node-01   <none>           <none>
kube-proxy-tdr2l                            1/1     Running   0          5m52s   192.168.123.121   kubernetes-node-02   <none>           <none>
kube-proxy-z95pn                            1/1     Running   0          27m     192.168.123.110   kubernetes-master    <none>           <none>
kube-scheduler-kubernetes-master            1/1     Running   0          27m     192.168.123.110   kubernetes-master    <none>           <none>

安装插件Calico

工作目录

/usr/local/kubernetes/cluster

下载 Calico 配置文件并修改

wget https://docs.projectcalico.org/v3.8/manifests/calico.yaml

修改配置文件

vi calico.yaml

192.168.0.0/16 修改为 10.244.0.0/16

- name: CALICO_IPV4POOL_CIDR
  value: "10.244.0.0/16" 


# The default IPv4 pool to create on startup if none exists. Pod IPs will be
# chosen from this range. Changing this value after installation will have
# no effect. This should fall within `--cluster-cidr`.
- name: CALICO_IPV4POOL_CIDR
  value: "10.244.0.0/16" 
# Disable file logging so `kubectl logs` works.
- name: CALICO_DISABLE_FILE_LOGGING
  value: "true"
# Set Felix endpoint to host default action to ACCEPT.
- name: FELIX_DEFAULTENDPOINTTOHOSTACTION
  value: "ACCEPT"
# Disable IPv6 on Kubernetes.

部署calico

kubectl apply -f calico.yaml

查看pod状态

watch kubectl get pods --all-namespaces

NAMESPACE     NAME                                        READY   STATUS    RESTARTS   AGE
kube-system   calico-kube-controllers-bc44d789c-f6rl7     1/1     Running   0          15m
kube-system   calico-node-ch885                           1/1     Running   0          15m
kube-system   calico-node-cs8jb                           1/1     Running   0          15m
kube-system   calico-node-g5bcb                           1/1     Running   0          15m
kube-system   calico-node-mddc5                           1/1     Running   0          15m
kube-system   coredns-9d85f5447-jdz27                     1/1     Running   0          59m
kube-system   coredns-9d85f5447-sh2fc                     1/1     Running   0          59m
kube-system   etcd-kubernetes-master                      1/1     Running   0          59m
kube-system   kube-apiserver-kubernetes-master            1/1     Running   0          59m
kube-system   kube-controller-manager-kubernetes-master   1/1     Running   0          59m
kube-system   kube-proxy-8pcvf                            1/1     Running   0          33m
kube-system   kube-proxy-s6cq7                            1/1     Running   0          53m
kube-system   kube-proxy-tdr2l                            1/1     Running   0          37m
kube-system   kube-proxy-z95pn                            1/1     Running   0          59m
kube-system   kube-scheduler-kubernetes-master            1/1     Running   0          59m

查看结点状态

kubectl get node

NAME                 STATUS   ROLES    AGE   VERSION
kubernetes-master    Ready    master   60m   v1.17.4
kubernetes-node-01   Ready    <none>   54m   v1.17.4
kubernetes-node-02   Ready    <none>   38m   v1.17.4
kubernetes-node-03   Ready    <none>   34m   v1.17.4

重置Kubernetes

重置指令

sudo kubeadm reset

输出

[reset] Reading configuration from the cluster...
[reset] FYI: You can look at this config file with 'kubectl -n kube-system get cm kubeadm-config -oyaml'
[reset] WARNING: Changes made to this host by 'kubeadm init' or 'kubeadm join' will be reverted.
[reset] Are you sure you want to proceed? [y/N]: y
[preflight] Running pre-flight checks
[reset] Removing info for node "kubernetes-master" from the ConfigMap "kubeadm-config" in the "kube-system" Namespace
W0410 21:07:15.789401   71480 removeetcdmember.go:61] [reset] failed to remove etcd member: error syncing endpoints with etc: etcdclient: no available endpoints
.Please manually remove this etcd member using etcdctl
[reset] Stopping the kubelet service
[reset] Unmounting mounted directories in "/var/lib/kubelet"
[reset] Deleting contents of config directories: [/etc/kubernetes/manifests /etc/kubernetes/pki]
[reset] Deleting files: [/etc/kubernetes/admin.conf /etc/kubernetes/kubelet.conf /etc/kubernetes/bootstrap-kubelet.conf /etc/kubernetes/controller-manager.conf /etc/kubernetes/scheduler.conf]
[reset] Deleting contents of stateful directories: [/var/lib/etcd /var/lib/kubelet /var/lib/dockershim /var/run/kubernetes /var/lib/cni]

The reset process does not clean CNI configuration. To do so, you must remove /etc/cni/net.d

The reset process does not reset or clean up iptables rules or IPVS tables.
If you wish to reset iptables, you must do so manually by using the "iptables" command.

If your cluster was setup to utilize IPVS, run ipvsadm --clear (or similar)
to reset your system's IPVS tables.

The reset process does not clean your kubeconfig files and you must remove them manually.
Please, check the contents of the $HOME/.kube/config file.

重置iptables

iptables -F && iptables -t nat -F && iptables -t mangle -F && iptables -X
sysctl net.bridge.bridge-nf-call-iptables=1

手动执行以下命令来清楚对应的残余网卡信息

sudo ip link del cni0
sudo ip link del flannel.1

Node NotReady

systemctl restart kube-proxy
systemctl restart kubelet

Master NotReady

systemctl restart kubelet
Ricost
关注
Kubernetes集群方方面面实战教程学习线路指南
江晓龙的博客
10-31 7万+
Kubernetes集群方方面面实战教程学习线路指南 学习路线指南 欢迎大家来到jiangxl~的《Kubernetes集群方方面面进阶之路》专栏，本文给大家详细列出Kubernetes集群方方面面每一章节文章指南，大家可以根据自己的需求阅读想要学习的文章。 本专栏涵盖Kubernetes集群方方面面的技术总结，包括高可用集群、Pod资源、Pod资源控制器、配置存储、数据存储、安全框架等各方面深入解析、Helm包管理机制、Istio网格服务，以及基于Kubernetes集群的CI/CD流程设计及实现，总文章
Kubernetes 系列之 kubeadm 搭建k8s集群
csdn_welearn的博客
09-21 1453
Kubeadm 搭建k8s集群 注意：Kubernetes 系列 所采用的kuberntetes版本都是 1.15+ 1 Master 节点安装 1.1 系统环境配置 1.1.1 设置主机名称 hostnamectl set-hostname kmaster-01 hostnamectl set-hostname knode-01 hostnamectl set-hostname knode-...
使用Kubeadm搭建Kubernetes集群
飘渺Jam的博客
04-15 1836
使用Kubeadm搭建Kubernetes集群
RedisClusterConfiguration配置
最新发布
weixin_35644453的博客
08-11 49
学习实现 RedisClusterConfiguration 配置的完整指南 Redis 集群是一种高可用、高性能的分布式存储解决方案。在 Java 应用程序中使用 Redis 集群时，我们通常会需要配置 RedisClusterConfiguration。本篇文章将带领刚入行的小白理解并实现 RedisClusterCo...
kubernetes高可用集群安装
水彩橘子
03-09 2697
1、相关资源导航 https://blog.csdn.net/zyj81092211/article/details/123068347 2、环境介绍 操作系统：centos 7.9 kubernetes版本：v1.23 kubelet kubeadm kubectl版本：1.23.4 containerd版本：1.4.13 master配置：2核心 4G内存 80G硬盘 worker配置：16核心 16G内存 500G硬盘 ip地址规划： k8s-master01:10.99.24.31 k8s-mast
【Kubeadm】环境搭建、配置、安装
meidongyan的博客
06-29 395
【代码】【Kubernetes】搭建工具Kubeadm安装
云原生|kubernetes|多集群管理之kubeconfig文件配置和使用（定义，使用方法，合并管理多集群）
zsk_john的技术分享专用博客
11-04 5122
kubeconfig文件的使用。
使用Kubeadm工具快速安装Kubernetes集群.pdf
10-20
在开始安装Kubernetes集群之前，需要对系统进行初始化和配置。首先，需要设置系统主机名和hosts文件的相互解析关系。这样可以确保集群中的每台服务器可以通过主机名相互通信。 其次，需要安装依赖包，包括conntrack...
pikube:我的本地Raspberry Pi Kubernetes集群的配置
04-07
在描述中，“皮库”可能是指这个项目的昵称或者特定的命名，它强调了这是一个用户的本地Raspberry Pi Kubernetes集群配置。这意味着用户已经将Kubernetes环境设置在了自己的Raspberry Pi设备上，这通常涉及到安装...
Kubernetes集群部署
zmq
11-14 347
kubernetes介绍与集群部署
初始化 Kubernetes 集群的必要步骤
AlphaFinance
07-04 114
通过以上步骤，你应该可以成功初始化并运行一个 Kubernetes 集群。
K8S集群上安装KubeSphere的详细过程
tigerhhzz的博客
12-26 1803
前提已经搭建好了k8s集群。
《Kubernetes部署篇：基于Kubernetes集群离线部署KubeSphere3.1》
东城绝神
05-11 2380
系列文章目录 提示：这里可以添加系列文章的所有文章的目录，目录需要自己手动添加 例如：第一章 Python 机器学习入门之pandas的使用 提示：写完文章后，目录可以自动生成，如何生成可参考右边的帮助文档 文章目录系列文章目录前言一、pandas是什么？二、使用步骤1.引入库2.读入数据总结 前言 提示：这里可以添加本文要记录的大概内容： 例如：随着人工智能的不断发展，机器学习这门技术也越来越重要，很多人都开启了学习机器学习，本文就介绍了机器学习的基础内容。 提示：以下是本篇文章正文内容，下面案例
Spring Boot Redis Cluster Configuration
pgig的专栏
03-29 7615
问题： 1、集群信息已变更(添加或停节点)，RedisTemplate无法访问节点 2、集群未读写分离，主读写压力大。 解决： 1、版本：spring boot 2.1.3.RELEASE、spring Cloud Greenwich.RELEASE 2、依赖：spring-boot-starter-data-redis、commons-pool2 ...
使用kubeadm部署k8s(2、k8s集群部署)
zhaikaiyun的博客
02-11 2154
1、kube-proxy开启ipvs的前置条件默认情况下，Kube-proxy将在kubeadm部署的集群中以iptables模式运行，需要注意的是，当内核版本大于4.19时，移除了nf_conntrack_ipv4模块，kubernetes官方建议使用nf_conntrack代替，否则报错无法找到nf_conntrack_ipv4模块，模式改为lvs调度的方式，kube-proxy主要解决的是s...
带你玩转kubernetes-k8s（第9篇：k8s-使用kubeadm安装,Kubectl命令补充）
坚持的道路注定孤独
07-08 2198
大家好，我们又见面了，现在说明一下哈，每周更新5篇哦。 kubeadm config kubeadm已经进入GA阶段，其控制面初始化和加入节点步骤都支持大量的可定制内容，因此kubeadm还提供了配置文件功能用于复杂定制。同时，kubeadm将配置文件以ConfigMap的形式保存到集群之中，便于后续的查询和升级工作。kubeadm config之命令提供了对这一组功能的支持：...
k8s在centos的安装
weixin_43323107的博客
01-02 327
记录下kubernetes的安装 环境准备 3台电脑 配置: cpu 核心2 node 内存4G master 内存2G IP: master : 192.168.10.82 node1:192.168.10.83 node2:192.168.10.84 安装前的准备 学习k8s，我相信这点linux基础还是有的，就不做演示了 1.配置静态ip 2.关闭swap分区 3.ssh免密...
Kubernetes集群安装与配置详解
这个文档详细阐述了在部署Kubernetes集群时的一些基础步骤，包括系统准备、环境调整以及内核模块的加载。对于初学者或者那些想要在本地环境中尝试k8s部署的人来说，这是一个很好的实践指南。遵循这些步骤，你应该...
评论
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

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

抵扣说明：

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

余额充值