首页 » Web前端 » phpmysqlinotfound技巧_Windows 下运用 Minikube 搭建Kubernetes

phpmysqlinotfound技巧_Windows 下运用 Minikube 搭建Kubernetes

访客 2024-11-03 0

扫一扫用手机浏览

文章目录 [+]

#硬件哀求:2核CPU或更高配置2GB内存或更高配置20GB磁盘空间或更多连接互联网容器或虚拟机管理器,例如:Docker、Hyperkit、Hyper-V、KVM、Parallels、Podman、VirtualBox 或 VMware Fusion/Workstation#Windows下利用PowerShell安装

New-Item -Path 'd:\' -Name 'minikube' -ItemType Directory -ForceInvoke-WebRequest -OutFile 'd:\minikube\minikube.exe' -Uri 'https://github.com/kubernetes/minikube/releases/latest/download/minikube-windows-amd64.exe' -UseBasicParsing

个中路径可以自定义

【——全网最全的网络安全学习资料包分享给爱学习的你,关注我,私信回答“领取”获取——】

phpmysqlinotfound技巧_Windows 下运用 Minikube 搭建Kubernetes

1.网络安全多个方向学习路线

phpmysqlinotfound技巧_Windows 下运用 Minikube 搭建Kubernetes
(图片来自网络侵删)

2.全网最全的CTF入门学习资料

3.一线大佬实战履历分享条记

4.网安大厂口试题合集

5.红蓝对抗实战技能秘籍

6.网络安全根本入门、Linux、web安全、渗透测试方面视频

设置环境变量

$oldPath = [Environment]::GetEnvironmentVariable('Path', [EnvironmentVariableTarget]::Machine)if ($oldPath.Split(';') -inotcontains 'd:\minikube'){ ` [Environment]::SetEnvironmentVariable('Path', $('{0};d:\minikube' -f $oldPath), [EnvironmentVariableTarget]::Machine) `}#启动集群

minikube start

默认情形下会利用Hyperv作为驱动

如果要利用Vmware或者其他,启动的时候须要指定

minikube start --driver vmware

如果报Exiting due to PROVIDER_VMWARE_NOT_FOUND: The 'vmware' provider was not found: exec: "vmrun": executable file not found in $PATH信息,把vmware的安装路径加入系统环境变量就行。

下载安装docker-machine-driver-vmware

https://github.com/machine-drivers/docker-machine-driver-vmware/releases/latest

下载然后放到系统中的任何位置都可以,但要把路径配置到环境变量中

再次启动

海内指定海内源:

--image-mirror-country=cn --image-repository=registry.cn-hangzhou.aliyuncs.com/google_containers

启动成功

#支配运用

创建运用YAML描述文件,这里以Nginx为例

apiVersion: apps/v1kind: Deploymentmetadata: name: nginx-deploymentspec: selector: matchLabels: app: nginx replicas: 2 # tells deployment to run 2 pods matching the template template: metadata: labels: app: nginx spec: containers: - name: nginx image: nginx:1.14.2 ports: - containerPort: 80

基于YAML文件创建支配

E:\>minikube kubectl -- apply -f nginx-deployment.yamldeployment.apps/nginx-deployment created

查看支配信息:

minikube kubectl -- describe deployment nginx-deployment

#暴露运用访问

查看 ReplicaSet 工具的信息:

E:\>minikube kubectl -- get replicasetsNAME DESIRED CURRENT READY AGEnginx-deployment-9456bbbf9 2 2 2 17mE:\>minikube kubectl -- describe replicasets

创建公开 Deployment 的 Service 工具:

minikube kubectl -- expose deployment nginx-deployment --type=NodePort --name=web-serviceviceservice/web-servicevice exposed

查看Service信息:

E:\>minikube kubectl -- get service web-serviceviceNAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGEweb-servicevice NodePort 10.98.221.134 <none> 80:30074/TCP 30s

查看 Service详情:

minikube kubectl -- describe services web-serviceviceName: web-serviceviceNamespace: defaultLabels: <none>Annotations: <none>Selector: app=nginxType: NodePortIP Family Policy: SingleStackIP Families: IPv4IP: 10.98.221.134IPs: 10.98.221.134Port: <unset> 80/TCPTargetPort: 80/TCPNodePort: <unset> 30074/TCPEndpoints: 172.17.0.5:80,172.17.0.6:80Session Affinity: NoneExternal Traffic Policy: ClusterEvents: <none>

这里由于用了NodePort的办法暴露外部做事,记住这个端口

查看IP列表:

E:\>minikube kubectl -- get nodes -o wideNAME STATUS ROLES AGE VERSION INTERNAL-IP EXTERNAL-IP OS-IMAGE KERNEL-VERSION CONTAINER-RUNTIMEminikube Ready control-plane,master 77m v1.23.3 192.168.91.140 <none> Buildroot 2021.02.4 4.19.202 docker://20.10.12

利用INTERNAL-IP加上NodePort的端口就可以访问运用了

curl http://http://<internal-ip>:<port>

相关文章