k8s

文档：https://kubernetes.io/docs/reference/

资源类型：

https://kubernetes.io/docs/reference/kubectl/overview/#resource-types

reference：

https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#objectmeta-v1-meta

例子：https://matthewpalmer.net/kubernetes-app-developer/articles/php-fpm-nginx-kubernetes.html

kubectl apply

应用配置

https://kubernetes.io/docs/reference/generated/kubectl/kubectl-commands#apply

Clusterip是集群内部的私有ip，在集群内部访问服务非常方便

安装ingress-nginx-controller

mac:

kubectl apply -f https://raw.githubusercontent.com/kubernetes/ingress-nginx/master/deploy/static/provider/cloud/deploy.yaml

centos:

https://kubernetes.github.io/ingress-nginx/deploy/#bare-metal

kubectl apply -f https://raw.githubusercontent.com/kubernetes/ingress-nginx/controller-v0.41.2/deploy/static/provider/baremetal/

ingress 配置

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

查看k8s的版本

k version

获得集群信息

k cluster-info

挂载的目录，内容无法访问

https://stackoverflow.com/questions/62170018/unable-to-access-volume-content-using-initcontainers