JosephThatwho的博客

ingress-nginx日志iveness probe failed: Get http://10.0.0.4:10254/healthz: dial tcp 10.0.0.4:10254: connect: connection refusedReadiness probe failed: Get http://10.0.0.4:10254/healthz: dial tcp 10.0.0.4:10254: connect: connection refusedkube-proxy日志E012

从pod内部访问K8S api时，可能会遇到角色权限不能访问的情况，如下：root@curl:/# curl -H "Authorization: Bearer $TOKEN" https://kubernetes{ "kind": "Status", "apiVersion": "v1", "metadata": { }, "status": "Failure", "message": "forbidden: User \"system:serviceaccount:

使用rancher在azure 虚拟机部署k8s后，出现集群内服务彼此不能解析地址的错误。查询coredns组件日志如下：[test@master .kube]$ kubectl logs coredns-bdffbc666-msvff -n kube-system.:532020-12-21T05:48:06.365Z [INFO] CoreDNS-1.3.12020-12-21T05:48:06.365Z [INFO] linux/amd64, go1.11.4, 6b56a9cCoreDNS

1.安装gluster源yum install centos-release-gluster -y2.安装glusterfs组件yum install -y glusterfs glusterfs-server glusterfs-fuse glusterfs-rdma glusterfs-geo-replication glusterfs-devel可能出现的问题：Error: Problem 1: cannot install the best candidate for the jo

前端在切片上传文件时收到code为413的报错，是因为服务器任务上传的文件大小超出服务器期望处理的大小。使用chrome抓包可见：可以看到错误是由Nginx服务器报出的，当前传递的文件大小为Content-Length: 1049997超出服务器默认处理的1M大小。后端服务通过jenkins部署在k8s集群上，所以需要在配置声明中提高可以处理的文件大小:apiVersion: exten...