还想做MAD

K8S 部署 Kubesphere pod minio 部署失败K8S 部署 Kubesphere pod minio 访问失败Unable to initialize new config from the provided credentials. i/o timeout.

关于K8S各资源Terminating状态如何快速删除，namespace status Terminating、pod status Terminating 亲测有效！！！

K8S network is not ready: container runtime network not ready: NetworkReady=false reason:NetworkPluginNotReady message:Network plugin returns error: cni plugin not initialized

K8S子节点join主节点访问Mater API报错：：{"message":"Unauthorized","reason":"Unauthorized","code":401}

K8S 卸载旧版本安装其他版本；K8S卸载失败；K8S yum 安装失败

K8S join节点报错：configmaps xxx is forbidden: User "system:bootstrap:xxx" cannot get resource "configmaps" in API group "" in the namespace "kube-system"

certificate has expired or is not yet valid: current time 2024-04-27T15:33:56+08:00 is before 2024-04-27T12:26:15Z

[ERROR FileAvailable--etc-kubernetes-kubelet.conf]: /etc/kubernetes/kubelet.conf already exists [ERROR Port-10250]: Port 10250 is in use [ERROR FileAvailable--etc-kubernetes-pki-ca.crt]: /etc/kubernetes/pki/ca.crt already exists

[ERROR CRI]: container runtime is not running: output: time="2023-09-21T11:15:47+08:00" level=fatal msg="validate service connection: CRI v1 runtime API is not implemented for endpoint \"unix:///var/run/containerd/containerd.sock\": rpc error: code = Unimp

今天部署了K8S主节点，Master节点安装了Calico网络插件，在运行node列表结果是NotReady，问题解决

Kubernetes K8S使用IPVS代理模式，当Service的类型为ClusterIP时，如何处理访问service却不能访问后端pod的情况。

​ Kubernetes作为一个分布式集群的管理工具，保证集群的安全性是其一个重要的任务。所谓的安全性其实就是保证对Kubernetes的各种客户端进行认证和鉴权操作。客户端：一般是独立于kubernetes之外的其他服务管理的用户账号。：kubernetes管理的账号，用于为Pod中的服务进程在访问Kubernetes时提供身份标识。认证、授权与准入控制ApiServer是访问及管理资源对象的唯一入口。Authentication（认证）：身份鉴别，只有正确的账号才能够通过认证。

k8s部署Mysql连接断断续续一会连接成功，一会连接失败