export http_proxy=http://192.168.10.5:3128
export https_proxy=http://192.168.10.5:3128
export no_proxy=127.0.0.1,localhost,192.168.10.43,10.96.0.0/12,192.168.0.0/16
[Service]
Environment="HTTP_PROXY=http://192.168.10.5:3128" "NO_PROXY=localhost,127.0.0.1,192.168.10.43,10.96.0.0/12,192.168.0.0/16"
kubeadm init --apiserver-advertise-address 192.168.2.43 --pod-network-cidr=10.244.0.0/16
kubeadm init --pod-network-cidr=192.168.0.0/16 --kubernetes-version=v1.19.3
#终端proxy
export no_proxy=127.0.0.1,localhost,192.168.10.43,10.96.0.0/12,192.168.0.0/16
#docker 代理
$ cat /etc/systemd/system/docker.service.d/http-proxy.conf
[Service]
Environment="HTTP_PROXY=http://192.168.10.5:3128" "NO_PROXY=localhost,127.0.0.1,192.168.10.43,10.96.0.0/12,192.168.0.0/16"
:27:28.810079 18447 configset.go:348] WARNING: kubeadm cannot validate component configs for API groups [kubelet.config.k8s.io kubeproxy.config.k8s.io]
failed to pull image "registry.cn-beijing.aliyuncs.com/imcto/kube-apiserver:v1.19.3": output: Error response from daemon: manifest for registry.cn-beijing.aliyuncs.com/imcto/kube-apiserver:v1.19.3 not found
, error: exit status 1
To see the stack trace of this error execute with --v=5 or higher
ps -aux |grep czht-
kubectl get -A svc
kubectl apply -f person-center.yaml
kubectl logs -f -n czht person-center-7c665d5b45-nzcfw
kubectl delete po -n czht person-center-7c665d5b45-nzcfw
watch kubectl get -A po
kubectl get -A svc
delete svc -n czht smart-new-api-gateway
kubectl describe po -nczht czht-user-center-6f84944d5b-47z7c