文档：https://kubernetes.io/docs/reference/
https://kubernetes.io/docs/reference/kubectl/overview/#resource-types
https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#objectmeta-v1-meta
Clusterip是集群内部的私有ip，在集群内部访问服务非常方便
安装ingress-nginx-controller
kubectl apply -f https://raw.githubusercontent.com/kubernetes/ingress-nginx/master/deploy/static/provider/cloud/deploy.yaml
kubectl apply -f https://raw.githubusercontent.com/kubernetes/ingress-nginx/controller-v0.41.2/deploy/static/provider/baremetal/
https://kubernetes.github.io/ingress-nginx/user-guide/basic-usage/
https://kubernetes.io/docs/concepts/services-networking/ingress/
让master节点可以运行pod，清除node上的污点
So... one quick kubectl taint nodes --all node-role.kubernetes.io/master- command later, and my single-node K8s cluster was now actually useful for running pods!
kubectl taint nodes k8s-master node-role.kubernetes.io/master:NoSchedule
https://stackoverflow.com/questions/62170018/unable-to-access-volume-content-using-initcontainers