- 博客(62)
- 收藏
- 关注
RSS订阅原创 K8s集群prometheus镜像配置非root用户执行导致监控页面targets无相关node信息监控
K8s集群prometheus镜像配置非root用户执行导致监控页面targets无相关node信息监控
2024-07-26 18:04:51
335
原创 虚机磁盘根目录占用满导致root用户无法登录，提示authorzitation error报错问题
虚机磁盘根目录占用满导致root用户无法登录，提示authorzitation error报错问题
2024-03-27 23:16:27
517
原创 虚机无法进入系统一直轮转在内核启动页面处理
在日常处理虚机过程中会出现，虚机无法进入系统，一直轮转在内核启动页面的情况。【步骤一】登录原先内核系统，设置默认新内核启动。【步骤四】重启后查询内核版本。【步骤二】进入系统后设置。【步骤三】重启操作系统。查看下次启动默认内核。
2024-03-27 23:06:31
463
原创 docker容器启动异常containerd.service: main process exited, code=exited, status=2/INVALIDARGUMENT
docker容器启动异常containerd.service: main process exited, code=exited, status=2/INVALIDARGUMENT
2024-01-22 17:07:38
2775
9
原创 虚拟机/etc/fstab 变更只读模式ready-only处理
虚拟机误操作将/etc/fstab中的根目录注释掉了，重启虚机后虚机可以正常启动，但无法进行修改。2、修改内核所在那行参数，将ro 修改为rw ，并且在该行之后添加 init=/bin/bash。# vi /etc/fstab 提示文件只读。3、修改完成后按ctrl +x 启动。4、重启虚机 reboot后查询配置。1、重启虚机，按e进入单用户模式。修改/etc/fstab配置。
2023-12-13 23:46:05
2856
原创 VMware虚机启动报Internal error xfs_want_corrupted_goto 和Internal error xfs_want_corrupted_return报错
VMware虚机启动报dm0 internal error xfs_want_corrupted_goto at line 1727 报错，虚机进入救援模式
2023-12-11 23:06:31
1170
原创 K8s v1.21.5版本报错Unable to connect to the server: x509: certificate signed by unknown authority
K8s v1.21.5 版本Unable to connect to the server: x509: certificate signed by unknown authority (possibly because of "crypto/rsa: verification error" while trying to verify candidate authority certificate "kubernetes")
2023-06-28 14:46:20
975
原创 k8s集群添加master节点 certificate etcd/peer is invalid: x509: certificate is valid for xxx,localhost,not x
k8s集群初始化配置后添加第二个master节点提示error execution phase control-plane-prepare/certs: error creating PKI assets: failed to write or validate certificate "etcd-peer": certificate etcd/peer is invalid: x509: certificate is valid for k8s-master01, localhost, not k8s
2023-05-14 09:57:47
1841
原创 helm部署相关服务过程中问题记录
【问题5】使用helm 创建tiller-deploy 异常，Pod提示NetworkPlugin cni failed to set up .. network:open/run/flannel/subnet.env:nosuchfileordirectory。在通过wget https://storage.googleapis.com/kubernetes-helm/helm-v2.13.1-linux-amd64.tar.gz文件过程发现无法获取，提示403 ：Forbidden。
2023-04-23 22:03:16
896
原创 K8s 配置高可用提示Configuration file ‘/etc/keepalived/keepalived.conf‘ is not a regular non-executable file
！！！！并非是所有文件都需要可执行权限-K8s 配置keepalived高可用提示Configuration file '/etc/keepalived/keepalived.conf' is not a regular non-executable file
2023-04-22 21:44:08
591
1
原创 双master节点+keepalived方式部署K8s 1.18.20
双master节点+keepalived方式部署K8s 1.18.20
2023-04-02 17:10:48
1625
5
原创 Centos7 XFS（dm-0）:Internal error XFS_WANT_CORRUPTED_GOTO
在k8s的道路上我们都是小白，每天启动虚机都会遇到各种各样的问题，这不。部署的k8s虚机启动发现操作系统启动异常，提示如下报错信息。进入/dev/mapper目录下，查询目录下路径信息。可以通过对文件系统进行修复操作，操作如下。重启完成后虚机恢复正常登录。
2023-03-22 20:48:22
3956
5
原创 k8s 1.18.20版本部署
该状态其实不影响整个集群使用，是因为默认的kube-scheduler.yaml和kube-controller-manager.yaml 中默认使用了10251和10252的端口。可以将对应的配置文件中- --port=0 给注释掉。可以自行去github,找到 flannel/Documentation/kube-flannel.yml 路径，拷贝出代码，新建文件上传，然后修改为.yml。服务器初始化配置可以参考原先我写的1.15.0版本部署方案。5.1 、生成初始化配置。5.2 、执行初始化配置。
2023-03-19 20:58:04
1511
2
原创 openssh 登录报错所走过的坑~~~Password authentication failed
openssh 登录报错所走过的坑~~~Password authentication failed
2023-03-19 10:15:09
2387
原创 Pod提示NetworkPlugin cni failed to set up .. network:open/run/flannel/subnet.env:nosuchfileordirectory
k8s创建Pod提示NetworkPlugin cni failed to set up .. network:open/ run/flannel/subnet.env: no such file or directory
2023-02-15 17:25:22
5701
4
原创 Openssh-8.5p1版本升级导致sshd.service重启提示22端口被占用总结
Openssh-8.5p1版本升级导致sshd.service重启提示22端口被占用总结
2022-09-25 17:35:06
2967
原创 error execution phase kubelet-start: error uploading crisocket: timed out waiting for the condition
k8s 1.15.0版本添加node节点报错，error execution phase kubelet-start: error uploading crisocket: timed out waiting for the condition
2022-09-18 23:16:18
2436
原创 linux virsh console无法登入虚拟机，宿主机virsh console 登录异常
linux virsh console无法登入虚拟机，宿主机virsh console 登录异常
2022-08-21 10:12:21
7790
2
原创 虚机创建异常报错No valid host was found，There are not enough hosts available
虚机创建异常报错No valid host was found，There are not enough hosts available
2022-08-21 10:02:58
3357
原创 k8s 1.15.0 外部etcd 服务状态异常member 5edae4a37f25086 has already been bootstrapped
k8s 1.15.0 外部etcd 服务状态异常member 5edae4a37f25086 has already been bootstrapped
2022-08-15 17:16:45
1553
原创 k8s集群添加master节点提示control plane instance a cluster that doesn‘t have a stable controlPlaneEndpoint ad
k8s集群添加master节点提示unable to add a new control plane instance a cluster that doesn't have a stable controlPlaneEndpoint address
2022-08-15 11:25:25
3929
原创 k8s 部署外部etcd集群（v3.4.13）etcd状态cannot unmarshal event: proto: wrong wireType = 0 for field Key异常处理
k8s 部署外部etcd集群（v3.4.13）etcd状态cannot unmarshal event: proto: wrong wireType = 0 for field Key异常处理
2022-08-09 16:52:19
799
原创 k8s 重启kubelet服务后message日志提示level=error msg=“copy shim log“ error=“read /proc/self/fd/22: file alread
k8s 重启kubelet服务后message日志提示level=error msg="copy shim log" error="read /proc/self/fd/12: file already closed"
2022-07-26 14:35:55
5004
原创 k8s 检查集群状态提示Get http://127.0.0.1:10251/healthz: dial tcp 127.0.0.1:10251: connect: connection refuse
k8s 检查集群状态提示Get http://127.0.0.1:10251/healthz: dial tcp 127.0.0.1:10251: connect: connection refuse
2022-07-26 14:20:36
4778
空空如也
空空如也
TA创建的收藏夹 TA关注的收藏夹
TA关注的人