K8S NodePort无法访问MySQL

最新推荐文章于 2024-08-20 10:22:03 发布

smokelee

最新推荐文章于 2024-08-20 10:22:03 发布

阅读量2.2k

点赞数 4

分类专栏： kubernetes 文章标签：分布式 kubernetes docker

本文链接：https://blog.csdn.net/smokelee/article/details/104431839

版权

本文记录了在K8s单机部署中遇到的Docker存储路径设置、Pod创建问题及NodePort无法访问MySQL的解决过程。在NodePort问题上，由于Service的selector与Pod的标签不匹配导致Service找不到对应的Pod作为Endpoint。修正selector后，问题得以解决。

摘要由CSDN通过智能技术生成

K8s单机部署填坑

1. 设置Docker存储路径

1.13.1 或者其它版本开始，要设置daemon.json的字段为“graph”，较早版本“data-root”

{
   
"registry-mirrors":["http://hub-mirror.c.163.com"],
"graph":"/data/docker"
}

2. kubectl create -f yaml后一直ContainerCreating

检查后发现如下错误

Error syncing pod 80f69868-53a8-11ea-aa0f-080027d3bf90, skipping: failed to “StartContainer” for “POD” with ErrImagePull: “image pull failed for registry.access.redhat.com/rhel7/pod-infrastructure:latest, this may be because there are no credentials on this request. details: (open /etc/docker/certs.d/registry.access.redhat.com/redhat-ca.crt: no such file or directory)”
诊断，

CentOS7的pytho-rhsm-certificates被替换成空包，需要自己解决证书的问题

解决

$ sudo -i && cd /tmp $ wget http://mirror.centos.org/centos/7/os/x86_64/Packages/python-rhsm-certificates-1.19.10-1.el7_4.x86_64.rpm
[root@vm-001]$ rpm2cpio python-rhsm-certificates-1.19.10-1.el7_4.x86_64.rpm | cpio -iv --to-stdout ./etc/rhsm/ca/redhat-uep.pem | tee /etc/rhsm/ca/redhat-uep.pem