网站做引流,服装网站模板,广州安全教育平台入口登录处,亳州做网站哪家好文章目录 简介安装工具配置代理运行集群检查集群加入rancher 简介
模拟客户环境#xff0c;测试 kubernetes v1.18.x 是否可以被 rancher v2.9.1 纳管。
安装工具
docker 安装Install and Set Up kubectl on Linux 安装 minikube
配置代理
docker proxylinux proxy
运行… 文章目录 简介安装工具配置代理运行集群检查集群加入rancher 简介
模拟客户环境测试 kubernetes v1.18.x 是否可以被 rancher v2.9.1 纳管。
安装工具
docker 安装Install and Set Up kubectl on Linux 安装 minikube
配置代理
docker proxylinux proxy
运行集群
$ minikube start --drivernone --container-runtimedocker --kubernetes-versionv1.18.1输出 minikube v1.18.1 on Rocky 8.10Kubernetes 1.20.2 is now available. If you would like to upgrade, specify: --kubernetes-versionv1.20.2
✨ Using the none driver based on existing profileStarting control plane node minikube in cluster minikubeRestarting existing none bare metal machine for minikube ...
ℹ️ OS release is Rocky Linux 8.10 (Green Obsidian)Found network options:▪ HTTP_PROXYhttp://192.168.21.101:7890▪ HTTPS_PROXYhttp://192.168.21.101:7890▪ NO_PROXYproxyhost,localhost,*.vsphere.local,*.vm.demo,*.tanzu.demo,192.168.21.101,127.0.0.1/8,10.0.0.0/8,172.16.0.0/12,192.168.0.0/16▪ http_proxyhttp://192.168.21.101:7890▪ https_proxyhttp://192.168.21.101:7890▪ no_proxyproxyhost,localhost,*.vsphere.local,*.vm.demo,*.tanzu.demo,192.168.21.101,127.0.0.1/8,10.0.0.0/8,172.16.0.0/12,192.168.0.0/16Preparing Kubernetes v1.18.1 on Docker 19.03.15 ...▪ env HTTP_PROXYhttp://192.168.21.101:7890▪ env HTTPS_PROXYhttp://192.168.21.101:7890▪ env NO_PROXYproxyhost,localhost,*.vsphere.local,*.vm.demo,*.tanzu.demo,192.168.21.101,127.0.0.1/8,10.0.0.0/8,172.16.0.0/12,192.168.0.0/16 Configuring local host environment ...❗ The none driver is designed for experts who need to integrate with an existing VMMost users should use the newer docker driver instead, which does not require root!For more information, see: https://minikube.sigs.k8s.io/docs/reference/drivers/none/❗ kubectl and minikube configuration will be stored in /root
❗ To use kubectl or minikube commands as your own user, you may need to relocate them. For example, to overwrite your own settings, run:▪ sudo mv /root/.kube /root/.minikube $HOME▪ sudo chown -R $USER $HOME/.kube $HOME/.minikube This can also be done automatically by setting the env var CHANGE_MINIKUBE_NONE_USERtrueVerifying Kubernetes components...▪ Using image gcr.io/k8s-minikube/storage-provisioner:v4Enabled addons: storage-provisioner, default-storageclass
❗ The cluster minikube already exists which means the --nodes parameter will be ignored. Use minikube node add to add nodes to an existing cluster.Done! kubectl is now configured to use minikube cluster and default namespace by default检查集群
$ kubectl get node
NAME STATUS ROLES AGE VERSION
minikube01 Ready none 178m v1.18.1
$ kubectl get pod -A
NAMESPACE NAME READY STATUS RESTARTS AGE
kube-system coredns-66bff467f8-rszjx 1/1 Running 0 176m
kube-system etcd-minikube01 1/1 Running 1 177m
kube-system kube-apiserver-minikube01 1/1 Running 0 177m
kube-system kube-controller-manager-minikube01 1/1 Running 0 177m
kube-system kube-proxy-nthcz 1/1 Running 0 176m
kube-system kube-scheduler-minikube01 1/1 Running 0 177m
kube-system storage-provisioner 1/1 Running 1 176m加入rancher
curl --insecure -sfL https://rancheruat.demo.com.cn/v3/import/gnplffg5965h27mjv4dwbgpvk8qhhpssj896t8vrdnblljhfpx6dhc_c-m-9gpswkpp.yaml | kubectl apply -f -$ kubectl edit deploy cattle-cluster-agent -n cattle-system
…..dnsPolicy: ClusterFirsthostAliases:- hostnames:- rancheruat.demo.com.cnip: 192.168.23.79restartPolicy: AlwaysschedulerName: default-scheduler
…..$ kubectl edit sts fleet-agent -n cattle-fleet-system
…..dnsPolicy: ClusterFirsthostAliases:- hostnames:- rancheruat.demo.com.cnip: 192.168.23.79restartPolicy: AlwaysschedulerName: default-scheduler
