"\"minikube cache\" will be deprecated in upcoming versions, please switch to \"minikube image load\"":"\"minikube cache\" 将在即将发布的版本中弃用，请切换至 \"minikube image load\"",
"--network flag is only valid with the docker/podman, KVM and Qemu drivers, it will be ignored":"--network 标识仅对 docker/podman KVM 和 Qemu 驱动程序有效，它将被忽略",
"1) Recreate the cluster with Kubernetes {{.new}}, by running:\n\t \n\t\t minikube delete{{.profile}}\n\t\t minikube start{{.profile}} --kubernetes-version={{.prefix}}{{.new}}\n\t \n\t\t2) Create a second cluster with Kubernetes {{.new}}, by running:\n\t \n\t\t minikube start -p {{.suggestedName}} --kubernetes-version={{.prefix}}{{.new}}\n\t \n\t\t3) Use the existing cluster at version Kubernetes {{.old}}, by running:\n\t \n\t\t minikube start{{.profile}} --kubernetes-version={{.prefix}}{{.old}}\n\t\t":"1) 使用以下命令使用 Kubernetes {{.new}} 重新创建集群：\n\t \n\t\t minikube delete{{.profile}}\n\t\t minikube start{{.profile}} --kubernetes-version={{.prefix}}{{.new}}\n\t \n\t\t2) 使用以下命令创建第二个具有 Kubernetes {{.new}} 的集群：\n\t \n\t\t minikube start -p {{.suggestedName}} --kubernetes-version={{.prefix}}{{.new}}\n\t \n\t\t3) 使用以下命令使用现有的 Kubernetes {{.old}} 版本的集群：\n\t \n\t\t minikube start{{.profile}} --kubernetes-version={{.prefix}}{{.old}}",
"1. Click on \"Docker for Desktop\" menu icon\n\t\t\t2. Click \"Preferences\"\n\t\t\t3. Click \"Resources\"\n\t\t\t4. Increase \"CPUs\" slider bar to 2 or higher\n\t\t\t5. Click \"Apply \u0026 Restart\"":"1. 点击 \"Docker for Desktop\" 菜单图标\n\t\t\t2. 点击 \"Preferences\"\n\t\t\t3. 点击 \"Resources\"\n\t\t\t4. 将 \"CPUs\" 滑动条调整到 2 或更高\n\t\t\t5. 点击 \"Apply \u0026 Restart\"",
"1. Click on \"Docker for Desktop\" menu icon\n\t\t\t2. Click \"Preferences\"\n\t\t\t3. Click \"Resources\"\n\t\t\t4. Increase \"Memory\" slider bar to {{.recommend}} or higher\n\t\t\t5. Click \"Apply \u0026 Restart\"":"1. 点击 \"Docker for Desktop\" 菜单图标\n\t\t\t2. 点击 \"Preferences\"\n\t\t\t3. 点击 \"Resources\"\n\t\t\t4. 将 \"Memory\" 滑动条调整到 {{.recommend}} 或更高\n\t\t\t5. 点击 \"Apply \u0026 Restart\"",
"1. Open the \"Docker Desktop\" menu by clicking the Docker icon in the system tray\n\t\t2. Click \"Settings\"\n\t\t3. Click \"Resources\"\n\t\t4. Increase \"CPUs\" slider bar to 2 or higher\n\t\t5. Click \"Apply \u0026 Restart\"":"1. 通过点击系统托盘中的 Docker 图标打开 \"Docker Desktop\" 菜单\n\t\t2. 点击 \"Settings\"\n\t\t3. 点击 \"Resources\"\n\t\t4. 将 \"CPUs\" 滑动条调整到 2 或更高\n\t\t5. 点击 \"Apply \u0026 Restart\"",
"1. Open the \"Docker Desktop\" menu by clicking the Docker icon in the system tray\n\t\t2. Click \"Settings\"\n\t\t3. Click \"Resources\"\n\t\t4. Increase \"Memory\" slider bar to {{.recommend}} or higher\n\t\t5. Click \"Apply \u0026 Restart\"":"1. 通过点击系统托盘中的 Docker 图标打开 \"Docker Desktop\" 菜单\n\t\t2. 点击 \"Settings\"\n\t\t3. 点击 \"Resources\"\n\t\t4. 将 \"Memory\" 滑动条调整到 {{.recommend}} 或更高\n\t\t5. 点击 \"Apply \u0026 Restart\"",
"A VPN or firewall is interfering with HTTP access to the minikube VM. Alternatively, try a different VM driver: https://minikube.sigs.k8s.io/docs/start/":"VPN 或者防火墙正在干扰对 minikube 虚拟机的 HTTP 访问。或者，您可以使用其它的虚拟机驱动：https://minikube.sigs.k8s.io/docs/start/",
"A firewall is blocking Docker the minikube VM from reaching the image repository. You may need to select --image-repository, or use a proxy.":"防火墙正在阻止 minikube 虚拟机中的 Docker 访问镜像仓库。您可能需要选择 --image-repository 或使用代理",
"A firewall is blocking Docker the minikube VM from reaching the internet. You may need to configure it to use a proxy.":"防火墙正在阻止 minikube 虚拟机中的 Docker 访问互联网。您可能需要对其进行配置为使用代理",
"A firewall is blocking Docker within the minikube VM from reaching the internet. You may need to configure it to use a proxy.":"防火墙正在阻止 minikube 虚拟机中的 Docker 访问互联网。您可能需要对其进行配置为使用代理",
"A firewall is interfering with minikube's ability to make outgoing HTTPS requests. You may need to change the value of the HTTPS_PROXY environment variable.":"防火墙正在干扰 minikube 发送 HTTPS 请求的能力，您可能需要改变 HTTPS_PROXY 环境变量的值",
"A firewall is likely blocking minikube from reaching the internet. You may need to configure minikube to use a proxy.":"防火墙可能会阻止 minikube 访问互联网。您可能需要将 minikube 配置为使用",
"A set of apiserver IP Addresses which are used in the generated certificate for kubernetes. This can be used if you want to make the apiserver available from outside the machine":"一组在为 kubernetes 生成的证书中使用的 apiserver IP 地址。如果您希望将此 apiserver 设置为可从机器外部访问，则可以使用这组 apiserver IP 地址",
"A set of apiserver IP Addresses which are used in the generated certificate for kubernetes. This can be used if you want to make the apiserver available from outside the machine":"一组在为 kubernetes 生成的证书中使用的 apiserver IP 地址。如果您希望将此 apiserver 设置为可从机器外部访问，则可以使用这组 apiserver IP 地址",
"A set of apiserver names which are used in the generated certificate for kubernetes. This can be used if you want to make the apiserver available from outside the machine":"一组在为 kubernetes 生成的证书中使用的 apiserver 名称。如果您希望将此 apiserver 设置为可从机器外部访问，则可以使用这组 apiserver 名称",
"A set of apiserver names which are used in the generated certificate for kubernetes. This can be used if you want to make the apiserver available from outside the machine":"一组在为 kubernetes 生成的证书中使用的 apiserver 名称。如果您希望将此 apiserver 设置为可从机器外部访问，则可以使用这组 apiserver 名称",
"A set of key=value pairs that describe configuration that may be passed to different components.\nThe key should be '.' separated, and the first part before the dot is the component to apply the configuration to.\nValid components are: kubelet, kubeadm, apiserver, controller-manager, etcd, proxy, scheduler\nValid kubeadm parameters:":"一组用于描述可传递给不同组件的配置的键值对。\n其中键应以英文句点“.”分隔，英文句点前面的第一个部分是应用该配置的组件。\n有效组件包括：kubelet、kubeadm、apiserver、controller-manager、etcd、proxy、scheduler\n有效 kubeadm 参数包括：",
"A set of key=value pairs that describe feature gates for alpha/experimental features.":"一组用于描述 alpha 版功能/实验性功能的功能限制的键值对。",
"Access to ports below 1024 may fail on Windows with OpenSSH clients older than v8.1. For more information, see: https://minikube.sigs.k8s.io/docs/handbook/accessing/#access-to-ports-1024-on-windows-requires-root-permission":"在 Windows 上使用 v8.1以上版本的OpenSSH客户端，访问 1024 以下端口可能会失败。更多信息请参阅：https://minikube.sigs.k8s.io/docs/handbook/accessing/#access-to-ports-1024-on-windows-requires-root-permission",
"Adding a control-plane node to a non-HA (non-multi-control plane) cluster is not currently supported. Please first delete the cluster and use 'minikube start --ha' to create new one.":"",
"After the addon is enabled, please run \"minikube tunnel\" and your ingress resources would be available at \"127.0.0.1\"":"插件启用后，请运行 \"minikube tunnel\" 您的 ingress 资源将在 \"127.0.0.1\"",
"Allow pods to use your NVIDIA GPUs. Options include: [all,nvidia] (Docker driver with Docker container-runtime only)":"所有 pods 使用您的英伟达 GPUs。选项包括:[all,nvidia](仅支持Docker容器运行时的Docker驱动程序)",
"Alternative image repository to pull docker images from. This can be used when you have limited access to gcr.io. Set it to \"auto\" to let minikube decide one for you. For Chinese mainland users, you may use local gcr.io mirrors such as registry.cn-hangzhou.aliyuncs.com/google_containers":"用于从中拉取 docker 镜像的备选镜像存储库。如果您对 gcr.io 的访问受到限制，则可以使用该镜像存储库。将镜像存储库设置为“auto”可让 minikube 为您选择一个存储库。对于中国大陆用户，您可以使用本地 gcr.io 镜像，例如 registry.cn-hangzhou.aliyuncs.com/google_containers",
"Amount of RAM allocated to the minikube VM (format: \u003cnumber\u003e[\u003cunit\u003e], where unit = b, k, m or g)":"为 minikube 虚拟机分配的 RAM 容量（格式：\u003c数字\u003e[\u003c单位\u003e]，其中单位 = b、k、m 或 g）",
"Amount of RAM allocated to the minikube VM (format: \u003cnumber\u003e[\u003cunit\u003e], where unit = b, k, m or g).":"为 minikube 虚拟机分配的 RAM 容量（格式：\u003c数字\u003e[\u003c单位\u003e]，其中单位 = b、k、m 或 g）。",
"Amount of RAM to allocate to Kubernetes (format: \u003cnumber\u003e[\u003cunit\u003e], where unit = b, k, m or g).":"为 Kubernetes 分配的 RAM 容量（格式：\u003c数字\u003e[\u003c单位\u003e]，其中单位 = b、k、m 或 g）。",
"Another hypervisor, such as VirtualBox, is conflicting with KVM. Please stop the other hypervisor, or use --driver to switch to it.":"另外一个管理程序与 KVM 产生了冲突，如 VirtualBox。请停止其他的管理程序,或者使用 --driver 切换到其他程序。",
"Another hypervisor, such as VirtualBox, is conflicting with KVM. Please stop the other hypervisor, or use --vm-driver to switch to it.":"另外一个管理程序与 KVM 产生了冲突，如 VirtualBox。请停止其他的管理程序，或者使用 --vm-driver 切换到其他程序。",
"Another program is using a file required by minikube. If you are using Hyper-V, try stopping the minikube VM from within the Hyper-V manager":"另一个程序正在使用 minikube 所需的文件。如果您正在使用 Hyper-V，请尝试从 Hyper-V 管理器中停止 minikube VM",
"Because you are using a Docker driver on {{.operating_system}}, the terminal needs to be open to run it.":"因为你正在使用 {{.operating_system}} 上的 Docker 驱动程序，所以需要打开终端才能运行它。",
"Both driver={{.driver}} and vm-driver={{.vmd}} have been set.\n\n Since vm-driver is deprecated, minikube will default to driver={{.driver}}.\n\n If vm-driver is set in the global config, please run \"minikube config unset vm-driver\" to resolve this warning.\n\t\t\t":"已设置 driver={{.driver}} 和 vm-driver={{.vmd}}。\n\n 由于 vm-driver 已弃用，minikube 将默认使用 driver={{.driver}}。\n\n 如果在全局配置中设置了 vm-driver，请运行 \"minikube config unset vm-driver\" 以解决此警告。",
"CGroup allocation is not available in your environment, You might be running minikube in a nested container. Try running:\n\t\t\t\n\tminikube start --extra-config=kubelet.cgroups-per-qos=false --extra-config=kubelet.enforce-node-allocatable=\"\"\n\n\t\t\t\n\t\t\t":"您的环境中没有 CGroup 分配，您可能在嵌套容器中运行 minikube。尝试运行:\n\t\t\t\n\tminikube start --extra-config=kubelet.cgroups-per-qos=false --extra-config=kubelet.enforce-node-allocatable=\"\"\n\n\t\t\t\n\t\t\t",
"CGroup allocation is not available in your environment. You might be running minikube in a nested container. Try running:\n\t\t\t\n\tminikube start --extra-config=kubelet.cgroups-per-qos=false --extra-config=kubelet.enforce-node-allocatable=\"\"\n\n\t\t\t\n\t\t\t":"你的环境中不支持 CGroup 分配。可能是因为你在嵌套容器中运行 minikube。尝试运行以下命令：\n\t\t\t\n\tminikube start --extra-config=kubelet.cgroups-per-qos=false --extra-config=kubelet.enforce-node-allocatable=\"\"\n\n\t\t\t\n\t\t\t",
"Changing the API server port of an existing minikube HA (multi-control plane) cluster is not currently supported. Please first delete the cluster.":"",
"Changing the HA (multi-control plane) mode of an existing minikube cluster is not currently supported. Please first delete the cluster and use 'minikube start --ha' to create new one.":"",
"Check that minikube is running and that you have specified the correct namespace (-n flag) if required.":"检测 minikube 是否正在运行，以及是否根据需要指定了正确的 namespace （-n 标志）",
"Check your firewall rules for interference, and run 'virt-host-validate' to check for KVM configuration issues. If you are running minikube within a VM, consider using --driver=none":"检查防火墙规则是否有干扰，并运行 'virt-host-validate' 检查 KVM 配置问题。如果你在虚拟机中运行 minikube，请考虑使用 --driver=none",
"Check your firewall rules for interference, and run 'virt-host-validate' to check for KVM configuration issues. If you are running minikube within a VM, consider using --vm-driver=none":"检查您的防火墙规则是否存在干扰，然后运行 'virt-host-validate' 以检查 KVM 配置问题，如果在虚拟机中运行minikube，请考虑使用 --vm-driver=none",
"Configure an external network switch following the official documentation, then add `--hyperv-virtual-switch=\u003cswitch-name\u003e` to `minikube start`":"根据官方文档配置外部网络交换机，然后添加 `--hyperv-virtual-switch=\u003cswitch-name\u003e` 到 `minikube start`",
"Configures the addon w/ADDON_NAME within minikube (example: minikube addons configure registry-creds). For a list of available addons use: minikube addons list":"在 minikube 中配置插件 w/ADDON_NAME（例如：minikube addons configure registry-creds）。查看相关可用的插件列表，请使用：minikube addons list",
"Confirm that you have a working internet connection and that your VM has not run out of resources by using: 'minikube logs'":"使用 'minikube logs' 确认您的互联网连接正常，并且您的虚拟机没有耗尽资源",
"Confirm that you have supplied the correct value to --hyperv-virtual-switch using the 'Get-VMSwitch' command":"使用 'Get-VMSwitch' 命令确认已经为 --hyperv-virtual-switch 提供了正确的值",
"Copy the specified file into minikube, it will be saved at path \u003ctarget file absolute path\u003e in your minikube.\nDefault target node controlplane and If \u003csource node name\u003e is omitted, It will trying to copy from host.\n\nExample Command : \"minikube cp a.txt /home/docker/b.txt\" +\n \"minikube cp a.txt minikube-m02:/home/docker/b.txt\"\n \"minikube cp minikube-m01:a.txt minikube-m02:/home/docker/b.txt\"":"将指定文件复制到 minikube，它将保存在 minikube 中的路径 \u003ctarget file absolute path\u003e。\n默认目标节点为 controlplane，如果省略 \u003csource node name\u003e，则会尝试从主机复制。\n\n示例命令：\"minikube cp a.txt /home/docker/b.txt\" +\n \"minikube cp a.txt minikube-m02:/home/docker/b.txt\"\n \"minikube cp minikube-m01:a.txt minikube-m02:/home/docker/b.txt\"",
"Could not determine a Google Cloud project, which might be ok.":"无法确定 Google Cloud 项目，这可能是可以接受的。",
"Could not find any GCP credentials. Either run `gcloud auth application-default login` or set the GOOGLE_APPLICATION_CREDENTIALS environment variable to the path of your credentials file.":"找不到任何 GCP 凭据。要么运行 `gcloud auth application-default login` 命令，要么将 GOOGLE_APPLICATION_CREDENTIALS 环境变量设置为凭据文件的路径。",
"Country code of the image mirror to be used. Leave empty to use the global one. For Chinese mainland users, set it to cn.":"需要使用的镜像镜像的国家/地区代码。留空以使用全球代码。对于中国大陆用户，请将其设置为 cn。",
"Creating {{.driver_name}} {{.machine_type}} (CPUs={{if not .number_of_cpus}}no-limit{{else}}{{.number_of_cpus}}{{end}}, Memory={{if not .memory_size}}no-limit{{else}}{{.memory_size}}MB{{end}}) ...":"",
"Deleting existing cluster {{.name}} with different driver {{.driver_name}} due to --delete-on-failure flag set by the user. ":"由于用户设置了 --delete-on-failure 标志，正在删除具有不同驱动程序 {{.driver_name}} 的现有集群 {{.name}}。",
"Disable checking for the availability of hardware virtualization before the vm is started (virtualbox driver only)":"禁用在启动虚拟机之前检查硬件虚拟化的可用性（仅限 virtualbox 驱动程序）",
"Disable dynamic memory in your VM manager, or pass in a larger --memory value":"禁用虚拟机管理器中的动态内存，或者使用 --memory 传入更大的值",
"Disables the addon w/ADDON_NAME within minikube (example: minikube addons disable dashboard). For a list of available addons use: minikube addons list":"在 minikube 中禁用插件 w/ADDON_NAME（例如：minikube addons disable dashboard）。查看相关可用的插件列表，请使用：minikube addons list",
"Disables the addon w/ADDON_NAME within minikube (example: minikube addons disable dashboard). For a list of available addons use: minikube addons list ":"禁用 minikube 中的 ADDON_NAME 插件（示例：minikube addons disable dashboard）。要获取可用插件的列表，请使用 minikube addons list",
"Disables the filesystem mounts provided by the hypervisors":"停用由管理程序提供的文件系统装载",
"Disk size allocated to the minikube VM (format: \u003cnumber\u003e[\u003cunit\u003e], where unit = b, k, m or g)":"分配给 minikube 虚拟机的磁盘大小（格式：\u003c数字\u003e[\u003c单位\u003e]，其中单位 = b、k、m 或 g）",
"Disk size allocated to the minikube VM (format: \u003cnumber\u003e[\u003cunit\u003e], where unit = b, k, m or g).":"分配给 minikube 虚拟机的磁盘大小（格式：\u003c数字\u003e[\u003c单位\u003e]，其中单位 = b、k、m 或 g）。",
"Display dashboard URL instead of opening a browser":"显示 dashboard URL，而不是打开浏览器",
"Docker Desktop has less than 2 CPUs configured, but Kubernetes requires at least 2 to be available":"Docker Desktop 少于 2 个 CPUs 可用, 但是 Kubernetes 需要至少 2 个 CPUs 可用",
"Docker Desktop is configured for Windows containers, but Linux containers are required for minikube":"Docker Desktop 配置为 Windows 容器，但 minikube 需要 Linux 容器",
"Docker Desktop only has {{.size}}MiB available, less than the required {{.req}}MiB for Kubernetes":"Docker Desktop 仅有 {{.size}}MiB 存储可用, 少于 Kubernetes 要求的 {{.req}}MiB",
"Docker Desktop only has {{.size}}MiB available, you may encounter application deployment failures.":"Docker Desktop 只有 {{.size}}MiB 可用空间，你可能会遇到应用部署失败的问题。",
"Docker container exited prematurely after it was created, consider investigating Docker's performance/health.":"Docker 容器在创建后过早退出，请考虑调查 Docker 的性能/健康状况。",
"Docker has less than 2 CPUs available, but Kubernetes requires at least 2 to be available":"Docker 可用的 CPU 少于 2 个，但 Kubernetes 至少需要 2 个可用的 CPU",
"Done! kubectl is now configured to use \"{{.name}}\" cluster and \"{{.ns}}\" namespace by default":"完成！kubectl 现在已配置，默认使用\"{{.name}}\"集群和\"{{.ns}}\"命名空间",
"Due to DNS issues your cluster may have problems starting and you may not be able to pull images\nMore details available at: https://minikube.sigs.k8s.io/docs/drivers/qemu/#known-issues":"由于 DNS 问题，你的集群可能在启动时遇到问题，你可能无法拉取镜像\n更多详细信息请参阅：https://minikube.sigs.k8s.io/docs/drivers/qemu/#known-issues",
"Due to changes in macOS 13+ minikube doesn't currently support VirtualBox. You can use alternative drivers such as docker or {{.driver}}.\n https://minikube.sigs.k8s.io/docs/drivers/docker/\n https://minikube.sigs.k8s.io/docs/drivers/{{.driver}}/\n\n For more details on the issue see: https://github.com/kubernetes/minikube/issues/15274\n":"由于 macOS 13+ 的变化，minikube 目前不支持 VirtualBox。你可以使用 docker 或 {{.driver}} 等替代驱动程序。\n https://minikube.sigs.k8s.io/docs/drivers/docker/\n https://minikube.sigs.k8s.io/docs/drivers/{{.driver}}/\n\n 有关此问题的更多详细信息，请参阅：https://github.com/kubernetes/minikube/issues/15274\n",
"Either systemctl is not installed, or Docker is broken. Run 'sudo systemctl start docker' and 'journalctl -u docker'":"未安装 systemctl 或者 Docker 损坏。请运行 'sudo systemctl start docker' 和 'journalctl -u docker'",
"Enable proxy for NAT DNS requests (virtualbox driver only)":"为 NAT DNS 请求启用代理（仅限 virtualbox 驱动程序）",
"Enable the default CNI plugin (/etc/cni/net.d/k8s.conf). Used in conjunction with \\\"--network-plugin=cni\\":"启用默认 CNI 插件 (/etc/cni/net.d/k8s.conf)。与“--network-plugin=cni”结合使用",
"Enable the default CNI plugin (/etc/cni/net.d/k8s.conf). Used in conjunction with \\\"--network-plugin=cni\\\".":"启用默认 CNI 插件 (/etc/cni/net.d/k8s.conf)。与“--network-plugin=cni”结合使用。",
"Enables the addon w/ADDON_NAME within minikube (example: minikube addons enable dashboard). For a list of available addons use: minikube addons list":"启动 minikube 插件 w/ADDON_NAME（例如：minikube addons enable dashboard）。查看相关可用的插件列表，请使用：minikube addons list",
"Enables the addon w/ADDON_NAME within minikube. For a list of available addons use: minikube addons list ":"在 minikube 中启用 ADDON_NAME 插件。要获取可用插件的列表，请使用 minikube addons list",
"Ensure that CRI-O is installed and healthy: Run 'sudo systemctl start crio' and 'journalctl -u crio'. Alternatively, use --container-runtime=docker":"确保 CRI-O 已安装且正常运行：执行 'sudo systemctl start crio' and 'journalctl -u crio'。或者使用 --container-runtime=docker",
"Ensure that Docker is installed and healthy: Run 'sudo systemctl start docker' and 'journalctl -u docker'. Alternatively, select another value for --driver":"确保 Docker 已安装并处于健康状态：运行 'sudo systemctl start docker' 和 'journalctl -u docker'。或者，选择另一个 --driver 的值",
"Ensure that Docker is installed and healthy: Run 'sudo systemctl start docker' and 'journalctl -u docker'. Alternatively, select another value for --vm-driver":"确保 Docker 已安装且正常运行： 执行 'sudo systemctl start docker' and 'journalctl -u docker'。或者为 --vm-driver 指定另外的值",
"Ensure that you are a member of the appropriate libvirt group (remember to relogin for group changes to take effect!)":"确保你是适当的 libvirt 组的成员（记得重新登录以使组更改生效！）",
"Error getting service status":"获取 service status 时出错",
"Error getting service with namespace: {{.namespace}} and labels {{.labelName}}:{{.addonName}}: {{.error}}":"使用 namespace: {{.namespace}} 和 labels {{.labelName}}:{{.addonName}} 获取 service 时出错：{{.error}}",
"Error: You have selected Kubernetes v{{.new}}, but the existing cluster for your profile is running Kubernetes v{{.old}}. Non-destructive downgrades are not supported, but you can proceed by performing one of the following options:\n\n* Recreate the cluster using Kubernetes v{{.new}}: Run \"minikube delete {{.profile}}\", then \"minikube start {{.profile}} --kubernetes-version={{.new}}\"\n* Create a second cluster with Kubernetes v{{.new}}: Run \"minikube start -p \u003cnew name\u003e --kubernetes-version={{.new}}\"\n* Reuse the existing cluster with Kubernetes v{{.old}} or newer: Run \"minikube start {{.profile}} --kubernetes-version={{.old}}\"":"错误：您已选择 Kubernetes v{{.new}}，但您的配置文件的现有集群正在运行 Kubernetes v{{.old}}。非破坏性降级不受支持，但若要继续操作，您可以执行以下选项之一：\n\n* 使用 Kubernetes v{{.new}} 重新创建现有集群：运行“minikube delete {{.profile}}”，然后运行“minikube start {{.profile}} --kubernetes-version={{.new}}”\n* 使用 Kubernetes v{{.new}} 再创建一个集群：运行“minikube start -p \u003cnew name\u003e --kubernetes-version={{.new}}”\n* 通过 Kubernetes v{{.old}} 或更高版本重复使用现有集群：运行“minikube start {{.profile}} --kubernetes-version={{.old}}”",
"Error: You have selected Kubernetes v{{.new}}, but the existing cluster for your profile is running Kubernetes v{{.old}}. Non-destructive downgrades are not supported, but you can proceed by performing one of the following options:\n* Recreate the cluster using Kubernetes v{{.new}}: Run \"minikube delete {{.profile}}\", then \"minikube start {{.profile}} --kubernetes-version={{.new}}\"\n* Create a second cluster with Kubernetes v{{.new}}: Run \"minikube start -p \u003cnew name\u003e --kubernetes-version={{.new}}\"\n* Reuse the existing cluster with Kubernetes v{{.old}} or newer: Run \"minikube start {{.profile}} --kubernetes-version={{.old}}":"错误：您已选择 Kubernetes v{{.new}}，但您的配置文件的现有集群正在运行 Kubernetes v{{.old}}。非破坏性降级不受支持，但若要继续操作，您可以执行以下选项之一：\n* 使用 Kubernetes v{{.new}} 重新创建现有集群：运行“minikube delete {{.profile}}”，然后运行“minikube start {{.profile}} --kubernetes-version={{.new}}”\n* 使用 Kubernetes v{{.new}} 再创建一个集群：运行“minikube start -p \u003cnew name\u003e --kubernetes-version={{.new}}”\n* 通过 Kubernetes v{{.old}} 或更高版本重复使用现有集群：运行“minikube start {{.profile}} --kubernetes-version={{.old}}”",
"External Adapter on which external switch will be created if no external switch is found. (hyperv driver only)":"如果找不到外部交换机，将在外部适配器上创建外部交换机。（仅适用于 hyperv 驱动程序）",
"Failed to get service URL - check that minikube is running and that you have specified the correct namespace (-n flag) if required: {{.error}}":"获取服务 URL 失败 - 请检查 minikube 是否正在运行，并确保已经指定了正确的命名空间（如果需要，请使用 -n 标志）：{{.error}}",
"For more information see: https://minikube.sigs.k8s.io/docs/drivers/{{.driver}}":"更多信息，请参阅 https://minikube.sigs.k8s.io/docs/drivers/{{.driver}}",
"For more information, see:":"更多信息，请参阅：",
"For more information, see: https://minikube.sigs.k8s.io/docs/reference/drivers/none/":"更多信息，请参阅：https://minikube.sigs.k8s.io/docs/reference/drivers/none/",
"For more information, see: {{.url}}":"更多信息，请参阅：{{.url}}",
"Gets the kubernetes URL(s) for the specified service in your local cluster":"获取本地集群中指定服务的 kubernetes URL",
"Gets the kubernetes URL(s) for the specified service in your local cluster. In the case of multiple URLs they will be printed one at a time.":"获取本地集群中指定服务的 kubernetes URL。如果有多个 URL，他们将一次打印一个",
"Gets the logs of the running instance, used for debugging minikube, not user code.":"获取正在运行的实例日志，用于调试 minikube，不是用户代码",
"Gets the status of a local Kubernetes cluster.\n\tExit status contains the status of minikube's VM, cluster and Kubernetes encoded on it's bits in this order from right to left.\n\tEg: 7 meaning: 1 (for minikube NOK) + 2 (for cluster NOK) + 4 (for Kubernetes NOK)":"获取本地 Kubernetes 集群的状态。\n\t退出状态包含了 minikube 的虚拟机、集群和 Kubernetes 状态的编码，从右到左依次表示。\n\t例如：7 表示：1（表示 minikube 不正常）+ 2（表示集群不正常）+ 4（表示 Kubernetes 不正常）",
"Go template format string for the cache list output. The format for Go templates can be found here: https://pkg.go.dev/text/template\nFor the list of accessible variables for the template, see the struct values here: https://pkg.go.dev/k8s.io/minikube/cmd/minikube/cmd#CacheListTemplate":"用于缓存列表输出的 Go 模板格式字符串。Go 模板的格式可以在此处找到：https://pkg.go.dev/text/template\n有关模板中可访问的变量列表，请参见此处的结构值：https://pkg.go.dev/k8s.io/minikube/cmd/minikube/cmd#CacheListTemplate",
"Go template format string for the config view output. The format for Go templates can be found here: https://pkg.go.dev/text/template\nFor the list of accessible variables for the template, see the struct values here: https://pkg.go.dev/k8s.io/minikube/cmd/minikube/cmd/config#ConfigViewTemplate":"Go模板格式字符串，用于配置视图输出。Go模板的格式可以在此链接找到：https://pkg.go.dev/text/template\n要查看模板中可访问的变量列表，请参见此链接中的结构值：https://pkg.go.dev/k8s.io/minikube/cmd/minikube/cmd/config#ConfigViewTemplate",
"Go template format string for the status output. The format for Go templates can be found here: https://pkg.go.dev/text/template\nFor the list accessible variables for the template, see the struct values here: https://pkg.go.dev/k8s.io/minikube/cmd/minikube/cmd#Status":"状态输出的 Go 模板格式字符串。Go 模板的格式可以在此处找到：https://pkg.go.dev/text/template\n关于模板中可访问的变量列表，请参阅此处的定义：https://pkg.go.dev/k8s.io/minikube/cmd/minikube/cmd#Status",
"HA (multi-control plane) clusters require 3 or more control-plane nodes":"HA（多控制平面）集群需要 3 个或更多控制平面节点",
"Headlamp can display more detailed information when metrics-server is installed. To install it, run:\n\n\tminikube{{.profileArg}} addons enable metrics-server\n":"Headlamp 在安装了 metrics-server 后可以显示更详细的信息。要安装它，请运行：\n\n\tminikube{{.profileArg}} addons enable metrics-server\n\n",
"Headlamp can display more detailed information when metrics-server is installed. To install it, run:\n\nminikube{{.profileArg}} addons enable metrics-server\t\n\n":"安装metrics-server后，Headlamp可以显示更详细的信息。 要安装它，请运行：\n\nminikube{{.profileArg}} addons enable metrics-server\t\n\n",
"Hyper-V requires that memory MB be an even number, {{.memory}}MB was specified, try passing `--memory {{.suggestMemory}}`":"Hyper-V 要求内存的 MB 值是偶数，{{.memory}}MB 被指定，尝试传递 `--memory {{.suggestMemory}}`",
"Hyperkit is broken. Upgrade to the latest hyperkit version and/or Docker for Desktop. Alternatively, you may choose an alternate --driver":"Hyperkit 已损坏。升级到最新的 hyperkit 版本以及/或者 Docker 桌面版。或者，你可以通过 --driver 切换其他选项",
"Hyperkit is broken. Upgrade to the latest hyperkit version and/or Docker for Desktop. Alternatively, you may choose an alternate --vm-driver":"Hyperkit 已损坏。升级到最新的 hyperkit 版本以及/或者 Docker 桌面版。或者，你可以通过 --vm-driver 切换其他选项",
"Hyperkit networking is broken. Try disabling Internet Sharing: System Preference \u003e Sharing \u003e Internet Sharing. \nAlternatively, you can try upgrading to the latest hyperkit version, or using an alternate driver.":"Hyperkit 网络已损坏。 尝试禁用 Internet 共享：系统偏好设置 \u003e 共享 \u003e Internet 共享。\n 或者，您可以尝试升级到最新的 hyperkit 版本，或使用备用驱动程序。",
"Hyperkit networking is broken. Upgrade to the latest hyperkit version and/or Docker for Desktop. Alternatively, you may choose an alternate --vm-driver":"Hyperkit 网络已损坏。升级到最新的 hyperkit 版本以及/或者 Docker 桌面版。或者，你可以通过 --vm-driver 切换其他选项",
"If set, added node will be available as worker. Defaults to true.":"如果设置，则添加的节点将作为 worker 可用。默认值为 true。",
"If set, added node will become a control-plane. Defaults to false. Currently only supported for existing HA (multi-control plane) clusters.":"如果设置，则添加的节点将成为控制平面。默认值为 false。目前仅支持现有的 HA（多控制平面）集群。",
"If set, automatically updates drivers to the latest version. Defaults to true.":"如果设置为 true，将自动更新驱动到最新版本。默认为 true。",
"If set, delete the current cluster if start fails and try again. Defaults to false.":"如果设置为 true，则在启动失败时删除当前群集，然后重试。默认为 false。",
"If set, disables metrics reporting (CPU and memory usage), this can improve CPU usage. Defaults to false.":"如果设置为 true，则禁用指标报告（CPU和内存使用率），这可以提高 CPU 利用率。默认为 false。",
"If set, disables optimizations that are set for local Kubernetes. Including decreasing CoreDNS replicas from 2 to 1. Defaults to false.":"如果设置为 true，则禁用为本地 Kubernetes 做设置的优化，包括将 CoreDNS 副本数从2减少到1。默认值为false。",
"If set, download tarball of preloaded images if available to improve start time. Defaults to true.":"如果设置为true，则在可用时下载预加载映像的tarball，以提高启动时间。默认为true。",
"If set, minikube VM/container will start without starting or configuring Kubernetes. (only works on new clusters)":"如果设置为 true，minikube虚拟机/容器将在不启动或配置Kubernetes的情况下启动。(只适用于新集群)",
"If the host has a firewall:\n\t\t\n\t\t1. Allow a port through the firewall\n\t\t2. Specify \"--port=\u003cport_number\u003e\" for \"minikube mount\"":"如果主机有防火墙：\n\n1. 允许防火墙通过一个端口\n2. 对于 'minikube mount'，指定 '--port=\u003c端口号\u003e'",
"If true, cache docker images for the current bootstrapper and load them into the machine. Always false with --driver=none.":"如果设置为 true，则缓存当前引导程序的 docker 镜像并加载到机器中。当使用--driver=none时，始终为false。",
"If true, cache docker images for the current bootstrapper and load them into the machine. Always false with --vm-driver=none.":"如果为 true，请缓存当前引导程序的 docker 镜像并将其加载到机器中。在 --vm-driver=none 情况下始终为 false。",
"If you are still interested to make {{.driver_name}} driver work. The following suggestions might help you get passed this issue:":"如果您仍然有兴趣使 {{.driver_name}} 驱动工作。以下建议可能会帮助您解决此问题：",
"If you don't want your credentials mounted into a specific pod, add a label with the `gcp-auth-skip-secret` key to your pod configuration.":"如果您不希望将凭据挂载到特定的 Pod 中，请在 Pod 配置中添加带有 `gcp-auth-skip-secret` 键的标签。",
"If you want existing pods to be mounted with credentials, either recreate them or rerun addons enable with --refresh.":"如果您希望现有的 Pod 使用凭据挂载，请重新创建它们或使用 --refresh 重新运行 addons enable。",
"Image was not built for the current minikube version. To resolve this you can delete and recreate your minikube cluster using the latest images. Expected minikube version: {{.imageMinikubeVersion}} -\u003e Actual minikube version: {{.minikubeVersion}}":"此镜像不适用于当前的 minikube 版本。要解决此问题，您可以删除并重新创建您的 minikube 集群，使用最新的镜像。预期的 minikube 版本：{{.imageMinikubeVersion}} -\u003e 实际的 minikube 版本：{{.minikubeVersion}}",
"Insecure Docker registries to pass to the Docker daemon. The default service CIDR range will automatically be added.":"传递给 Docker 守护进程的不安全 Docker Registry。 系统会自动添加默认 service CIDR 范围。",
"Insecure Docker registries to pass to the Docker daemon. The default service CIDR range will automatically be added.":"传递给 Docker 守护进程的不安全 Docker 注册表。系统会自动添加默认服务 CIDR 范围。",
"It seems that you are running in GCE, which means authentication should work without the GCP Auth addon. If you would still like to authenticate using a credentials file, use the --force flag.":"看起来您正在 GCE 中运行，这意味着身份验证应该可以在没有 GCP Auth 插件的情况下工作。如果您仍然想使用凭据文件进行身份验证，请使用 --force 标志。",
"Kubernetes requires at least 2 CPU's to start":"Kubernetes至少需要2个CPU才能启动",
"Kubernetes version not found in GitHub version list. You can force a Kubernetes version via the --force flag":"在GitHub版本列表中找不到Kubernetes版本。您可以通过--force标志强制使用Kubernetes版本",
"Kubernetes {{.new}} is now available. If you would like to upgrade, specify: --kubernetes-version={{.new}}":"Kubernetes {{.new}} 现在可用了。如果您想升级，请指定 --kubernetes-version={{.new}}",
"Kubernetes {{.new}} is now available. If you would like to upgrade, specify: --kubernetes-version={{.prefix}}{{.new}}":"Kubernetes {{.new}} 现在可用。如果您想要升级，请指定：--kubernetes-version={{.prefix}}{{.new}}",
"List image names the addon w/ADDON_NAME used. For a list of available addons use: minikube addons list":"列出使用 w/ADDON_NAME 插件的镜像名称。有关可用插件的列表，请使用: minikube addons list",
"Listening to {{.listenAddr}}. This is not recommended and can cause a security vulnerability. Use at your own risk":"监听 {{.listenAddr}}。不建议这样做，可能会造成安全漏洞。请自行决定是否使用",
"Location of the VPNKit socket used for networking. If empty, disables Hyperkit VPNKitSock, if 'auto' uses Docker for Mac VPNKit connection, otherwise uses the specified VSock (hyperkit driver only)":"用于网络连接的 VPNKit 套接字的位置。如果为空，则停用 Hyperkit VPNKitSock；如果为“auto”，则将 Docker 用于 Mac VPNKit 连接；否则使用指定的 VSock（仅限 hyperkit 驱动程序）",
"Location of the minikube iso":"minikube iso 的位置",
"Minikube is a CLI tool that provisions and manages single-node Kubernetes clusters optimized for development workflows.":"Minikube 是一个命令行工具，它提供和管理针对开发工作流程优化的单节点 Kubernetes 集群。",
"NIC Type used for host only network. One of Am79C970A, Am79C973, 82540EM, 82543GC, 82545EM, or virtio (virtualbox driver only)":"网卡类型仅用于主机网络。Am79C970A, Am79C973, 82540EM, 82543GC, 82545EM 之一，或 virtio(仅限 VirtualBox 驱动程序)",
"NIC Type used for nat network. One of Am79C970A, Am79C973, 82540EM, 82543GC, 82545EM, or virtio (virtualbox driver only)":"用于 nat 网络的 NIC 类型。 Am79C970A、Am79C973、82540EM、82543GC、82545EM 或 virtio 之一（仅限 virtualbox 驱动程序）",
"NOTE: Please do not close this terminal as this process must stay alive for the tunnel to be accessible ...":"注意：请不要关闭此终端，因为此进程必须保持活动状态才能访问隧道......",
"NOTE: This process must stay alive for the mount to be accessible ...":"注意：此进程必须保持活动状态才能访问安装......",
"No IP address provided. Try specifying --ssh-ip-address, or see https://minikube.sigs.k8s.io/docs/drivers/ssh/":"未提供 IP 地址。尝试指定 --ssh-ip-address，或参见 https://minikube.sigs.k8s.io/docs/drivers/ssh/",
"No possible driver was detected. Try specifying --driver, or see https://minikube.sigs.k8s.io/docs/start/":"未检测到可用的驱动程序。尝试指定 --driver，或查看 https://minikube.sigs.k8s.io/docs/start/",
"None of the known repositories in your location are accessible. Using {{.image_repository_name}} as fallback.":"您所在位置的已知存储库都无法访问。正在将 {{.image_repository_name}} 用作后备存储库。",
"None of the known repositories is accessible. Consider specifying an alternative image repository with --image-repository flag":"已知存储库都无法访问。请考虑使用 --image-repository 标志指定备选镜像存储库",
"Opens the addon w/ADDON_NAME within minikube (example: minikube addons open dashboard). For a list of available addons use: minikube addons list ":"",
"Outputs minikube shell completion for the given shell (bash, zsh, fish or powershell)\n\n\tThis depends on the bash-completion binary. Example installation instructions:\n\tOS X:\n\t\t$ brew install bash-completion\n\t\t$ source $(brew --prefix)/etc/bash_completion\n\t\t$ minikube completion bash \u003e ~/.minikube-completion # for bash users\n\t\t$ minikube completion zsh \u003e ~/.minikube-completion # for zsh users\n\t\t$ source ~/.minikube-completion\n\t\t$ minikube completion fish \u003e ~/.config/fish/completions/minikube.fish # for fish users\n\tUbuntu:\n\t\t$ apt-get install bash-completion\n\t\t$ source /etc/bash_completion\n\t\t$ source \u003c(minikube completion bash) # for bash users\n\t\t$ source \u003c(minikube completion zsh) # for zsh users\n\t\t$ minikube completion fish \u003e ~/.config/fish/completions/minikube.fish # for fish users\n\n\tAdditionally, you may want to output the completion to a file and source in your .bashrc\n\n\tWindows:\n\t\t## Save completion code to a script and execute in the profile\n\t\tPS\u003e minikube completion powershell \u003e $HOME\\.minikube-completion.ps1\n\t\tPS\u003e Add-Content $PROFILE '. $HOME\\.minikube-completion.ps1'\n\n\t\t## Execute completion code in the profile\n\t\tPS\u003e Add-Content $PROFILE 'if (Get-Command minikube -ErrorAction SilentlyContinue) {\n\t\t minikube completion powershell | Out-String | Invoke-Expression\n\t\t }'\n\n\tNote for zsh users: [1] zsh completions are only supported in versions of zsh \u003e= 5.2\n\tNote for fish users: [2] please refer to this docs for more details https://fishshell.com/docs/current/#tab-completion\n":"",
"Path to the qemu firmware file. Defaults: For Linux, the default firmware location. For macOS, the brew installation location. For Windows, C:\\Program Files\\qemu\\share":"qemu 固件文件的路径。默认值：对于 Linux，使用默认固件位置。对于 macOS，使用 brew 安装位置。对于 Windows，使用 C:\\Program Files\\qemu\\share",
"Please provide an image in your local daemon to load into minikube via \u003cminikube image load IMAGE_NAME\u003e":"请在本地 Docker 守护程序中提供一个镜像，以通过 \u003cminikube image load IMAGE_NAME\u003e 加载到 minikube 中",
"Please re-eval your docker-env, To ensure your environment variables have updated ports:\n\n\t'minikube -p {{.profile_name}} docker-env'\n\n\t":"请重新评估您的 docker-env，以确保您的环境变量已更新端口：\n\n\t'minikube -p {{.profile_name}} docker-env'\n\n\t",
"Please run `minikube logs --file=logs.txt` and attach logs.txt to the GitHub issue.":"请运行 minikube logs --file=logs.txt 命令，并将生成的 logs.txt 文件附加到 GitHub 问题中。",
"Please specify the directory to be mounted: \n\tminikube mount \u003csource directory\u003e:\u003ctarget directory\u003e (example: \"/host-home:/vm-home\")":"请指定要挂载的目录：\n\tminikube mount \u003csource directory\u003e:\u003ctarget directory\u003e （示例：\"/host-home:/vm-home\"）",
"Please visit the following link for documentation around this: \n\thttps://help.github.com/en/packages/using-github-packages-with-your-projects-ecosystem/configuring-docker-for-use-with-github-packages#authenticating-to-github-packages\n":"请查看以下链接以获取相关文档：\nhttps://help.github.com/en/packages/using-github-packages-with-your-projects-ecosystem/configuring-docker-for-use-with-github-packages#authenticating-to-github-packages",
"Profile \"{{.cluster}}\" not found. Run \"minikube profile list\" to view all profiles.":"未找到配置文件 \"{{.cluster}}\"。运行 \"minikube profile list\" 命令查看所有配置文件。",
"Profile name \"{{.profilename}}\" is reserved keyword. To delete this profile, run: \"{{.cmd}}\"":"配置文件名称 \"{{.profilename}}\" 是保留关键字。要删除该配置文件，请执行命令：\"{{.cmd}}\"",
"Profile name '{{.name}}' is duplicated with machine name '{{.machine}}' in profile '{{.profile}}'":"配置文件名称 '{{.name}}' 与机器名称 '{{.machine}}' 在 '{{.profile}}' 配置文件中重复",
"Profile name '{{.name}}' is not valid":"配置文件名称 '{{.name}}' 无效",
"Profile name '{{.profilename}}' is not valid":"配置文件名称 '{{.profilename}}' 无效",
"Provides instructions to point your terminal's docker-cli to the Docker Engine inside minikube. (Useful for building docker images directly inside minikube)":"提供将终端的 docker-cli 指向 minikube 内部 Docker Engine 的说明。（用于直接在 minikube 内构建 docker 镜像）",
"Provides instructions to point your terminal's docker-cli to the Docker Engine inside minikube. (Useful for building docker images directly inside minikube)\n\nFor example, you can do all docker operations such as docker build, docker run, and docker ps directly on the docker inside minikube.\n\nNote: You need the docker-cli to be installed on your machine.\ndocker-cli install instructions: https://minikube.sigs.k8s.io/docs/tutorials/docker_desktop_replacement/#steps":"提供将终端的 docker-cli 指向 minikube 内部 Docker Engine 的说明。（用于直接在 minikube 内构建 docker 镜像）\n\n例如，您可以在 minikube 内的 docker 上执行所有 docker 操作，如 docker build、docker run 和 docker ps。\n\n注意：您需要在计算机上安装 docker-cli。\n\ndocker-cli 安装指南：https://minikube.sigs.k8s.io/docs/tutorials/docker_desktop_replacement/#steps",
"Reboot to complete VirtualBox installation, verify that VirtualBox is not blocked by your system, and/or use another hypervisor":"重启以完成 VirtualBox 安装，检查 VirtualBox 未被您的操作系统禁用，或者使用其他的管理程序。",
"Recreate the cluster by running:\n\t\tminikube delete {{.profileArg}}\n\t\tminikube start {{.profileArg}}":"运行以下命令重新创建集群:n\t\tminikube delete {{.profileArg}}\n\t\tminikube start {{.profileArg}}",
"Registries used by this addon. Separated by commas.":"此插件使用的注册表。以逗号分隔。",
"Registry addon with {{.driver}} driver uses port {{.port}} please use that instead of default port 5000":"注册表插件 {{.driver}} Driver 使用端口 {{.port}} 代替默认端口 5000",
"Reinstall VirtualBox and verify that it is not blocked: System Preferences -\u003e Security \u0026 Privacy -\u003e General -\u003e Some system software was blocked from loading":"",
"Requested cpu count {{.requested_cpus}} is greater than the available cpus of {{.avail_cpus}}":"请求的 CPU 数量 {{.requested_cpus}} 大于可用的 CPU 值 {{.avail_cpus}}",
"Requested cpu count {{.requested_cpus}} is less than the minimum allowed of {{.minimum_cpus}}":"请求的 CPU 数量 {{.requested_cpus}} 小于允许的最小值 {{.minimum_cpus}}",
"Requested disk size {{.requested_size}} is less than minimum of {{.minimum_size}}":"请求的磁盘大小 {{.requested_size}} 小于最小值 {{.minimum_size}}",
"Requested memory allocation ({{.memory}}MB) is less than the default memory allocation of {{.default_memorysize}}MB. Beware that minikube might not work correctly or crash unexpectedly.":"请求的内存分配 ({{.memory}}MB) 小于默认内存分配 {{.default_memorysize}}MB。请注意 minikube 可能无法正常运行或可能会意外崩溃。",
"Requested memory allocation ({{.requested}}MB) is less than the recommended minimum {{.recommend}}MB. Deployments may fail.":"请求的内存分配（{{.requested}}MB）小于推荐的最小值 {{.recommend}}MB。部署可能失败。",
"Requested memory allocation {{.requested_size}} is less than the minimum allowed of {{.minimum_size}}":"请求的内存分配 {{.requested_size}} 小于允许的 {{.minimum_size}} 最小值",
"Requested memory allocation {{.requested}}MB is more than your system limit {{.system_limit}}MB.":"请求的内存分配 {{.requested}}MB 超过了系统限制 {{.system_limit}}MB。",
"Restart Docker, Ensure docker is running and then run: 'minikube delete' and then 'minikube start' again":"重启 Docker，确保 Docker 正在运行，然后运行：'minikube delete'，然后再次运行：'minikube start'",
"Retrieves the IP address of the running cluster, checks it\n\t\t\twith IP in kubeconfig, and corrects kubeconfig if incorrect.":"检索运行集群的 IP 地址，将其与 kubeconfig 中的 IP 进行比较，并在有误时纠正 kubeconfig。",
"Returns the Kubernetes URL(s) for service(s) in your local cluster. In the case of multiple URLs they will be printed one at a time.":"返回本地集群中服务的 Kubernetes URL。如果存在多个 URL，则每次将打印一个 URL。",
"Returns the value of PROPERTY_NAME from the minikube config file. Can be overwritten at runtime by flags or environmental variables.":"从 minikube 配置文件返回 PROPERTY_NAME 的值。可以在运行时通过标志或环境变量进行覆盖。",
"Run 'kubectl describe pod coredns -n kube-system' and check for a firewall or DNS conflict":"运行 'kubectl describe pod coredns -n kube-system' 并检查防火墙或 DNS 冲突",
"Run 'minikube delete' to delete the stale VM, or and ensure that minikube is running as the same user you are issuing this command with":"执行 'minikube delete' 以删除过时的虚拟机，或者确保 minikube 以与您发出此命令的用户相同的用户身份运行",
"Run the Kubernetes client, download it if necessary. Remember -- after kubectl!\n\nThis will run the Kubernetes client (kubectl) with the same version as the cluster\n\nNormally it will download a binary matching the host operating system and architecture,\nbut optionally you can also run it directly on the control plane over the ssh connection.\nThis can be useful if you cannot run kubectl locally for some reason, like unsupported\nhost. Please be aware that when using --ssh all paths will apply to the remote machine.":"",
"Service '{{.service}}' was not found in '{{.namespace}}' namespace.\nYou may select another namespace by using 'minikube service {{.service}} -n \u003cnamespace\u003e'. Or list out all the services using 'minikube service list'":"在 '{{.namespace}}' 命名空间中未找到服务 '{{.service}}'。\n您可以通过使用 'minikube service {{.service}} -n \u003cnamespace\u003e' 选择另一个命名空间。或使用 'minikube service list' 列出所有服务",
"Services {{.svc_names}} have type \"ClusterIP\" . Minikube allows you to access them only for testing":"{{.svc_names}} 均为ClusterIP类型,正常情况仅供集群内访问。Minikube提供的外部访问手段仅可供测试使用",
"Set a static IP for the minikube cluster, the IP must be: private, IPv4, and the last octet must be between 2 and 254, for example 192.168.200.200 (Docker and Podman drivers only)":"为 minikube 集群设置静态IP，该IP必须是私有IPv4地址，最后一位必须介于2和254之间，例如：192.168.200.200（仅适用于 Docker 和 Podman 驱动程序）",
"Sets the PROPERTY_NAME config value to PROPERTY_VALUE\n\tThese values can be overwritten by flags or environment variables at runtime.":"设置 PROPERTY_NAME 配置值为 PROPERTY_VALUE。这些值可以在运行时被标志或环境变量覆盖。",
"Simulate numa node count in minikube, supported numa node count range is 1-8 (kvm2 driver only)":"在 minikube 中模拟 numa 节点数量，支持的 numa 节点数量范围为 1-8 (仅支持 kvm2 驱动程序)",
"Some dashboard features require the metrics-server addon. To enable all features please run:\n\n\tminikube{{.profileArg}} addons enable metrics-server\t\n\n":"某些 dashboard 功能需要启用 metrics-server 插件。为了启用所有功能，请运行以下命令：\n\n\tminikube{{.profileArg}} addons enable metrics-server\t\n\n",
"Some dashboard features require the metrics-server addon. To enable all features please run:\n\n\tminikube{{.profileArg}} addons enable metrics-server\n":"",
"Sorry, the IP provided with the --listen-address flag is invalid: {{.listenAddr}}.":"抱歉，使用 --listen-address 标志提供的 IP 无效：{{.listenAddr}}。",
"Sorry, the address provided with the --insecure-registry flag is invalid: {{.addr}}. Expected formats are: \u003cip\u003e[:\u003cport\u003e], \u003chostname\u003e[:\u003cport\u003e] or \u003cnetwork\u003e/\u003cnetmask\u003e":"抱歉，使用 --insecure-registry 标志提供的地址无效：{{.addr}}。预期格式为：\u003cip\u003e[:\u003cport\u003e]、\u003chostname\u003e[:\u003cport\u003e] 或 \u003cnetwork\u003e/\u003cnetmask\u003e",
"Sorry, the kubeadm.{{.parameter_name}} parameter is currently not supported by --extra-config":"抱歉，--extra-config 目前不支持 kubeadm.{{.parameter_name}} 参数",
"Sorry, the url provided with the --registry-mirror flag is invalid: {{.url}}":"抱歉，通过 --registry-mirror 标志提供的网址无效：{{.url}}",
"Sorry, {{.driver}} does not allow mounts to be changed after container creation (previous mount: '{{.old}}', new mount: '{{.new}})'":"抱歉，{{.driver}} 不允许在容器创建后更改挂载（之前的挂载：'{{.old}}'，新挂载：'{{.new}}'）",
"Source {{.path}} can not be empty":"源路径 {{.path}} 不能为空",
"Specified Kubernetes version {{.specified}} is less than the oldest supported version: {{.oldest}}. Use `minikube config defaults kubernetes-version` for details.":"",
"Specified Kubernetes version {{.specified}} is newer than the newest supported version: {{.newest}}. Use `minikube config defaults kubernetes-version` for details.":"指定的 Kubernetes 版本 {{.specified}} 较新，比支持的最新版本 {{.newest}} 还要新。请使用 `minikube config defaults kubernetes-version` 查看详情。",
"Specifying extra disks is currently only supported for the following drivers: {{.supported_drivers}}. If you can contribute to add this feature, please create a PR.":"",
"Stops a local Kubernetes cluster. This command stops the underlying VM or container, but keeps user data intact. The cluster can be started again with the \"start\" command.":"停止本地 Kubernetes 集群。此命令会停止底层的虚拟机或容器，但会保留用户数据。可以使用 \"start\" 命令重新启动集群。",
"Subnet to be used on kic cluster. If left empty, minikube will choose subnet address, beginning from 192.168.49.0. (docker and podman driver only)":"在 kic 集群上使用的子网。如果留空，minikube 将从 192.168.49.0 开始选择子网地址。（仅适用于 docker 和 podman 驱动程序）",
"The '{{.driver}}' driver requires elevated permissions. The following commands will be executed:\n\n{{ .example }}\n":"'{{.driver}}' 驱动程序需要提升权限，将执行以下命令：\n\n{{ .example }}\n",
"The --image-repository flag you provided contains Scheme: {{.scheme}}, which will be removed automatically":"您提供的 --image-repository 标志包含方案：{{.scheme}}，这将自动移除",
"The --image-repository flag your provided ended with a trailing / that could cause conflict in kubernetes, removed automatically":"您提供的 --image-repository 标志以尾随 / 结束，可能会在 Kubernetes 中引起冲突，已自动移除",
"The KVM driver is unable to resurrect this old VM. Please run `minikube delete` to delete it and try again.":"KVM 驱动程序无法恢复此旧 VM。请运行 `minikube delete` 来删除它，然后重试。",
"The VM driver crashed. Run 'minikube start --alsologtostderr -v=8' to see the VM driver error message":"VM 驱动程序崩溃。运行 'minikube start --alsologtostderr -v=8' 来查看 VM 驱动程序的错误消息",
"The ambassador addon has stopped working as of v1.23.0, for more details visit: https://github.com/datawire/ambassador-operator/issues/73":"ambassador 插件自 v1.23.0 起停止工作，更多详情请访问：https://github.com/datawire/ambassador-operator/issues/73",
"The apiserver name which is used in the generated certificate for kubernetes. This can be used if you want to make the apiserver available from outside the machine":"在为 kubernetes 生成的证书中使用的 apiserver 名称。如果您希望将此 apiserver 设置为可从机器外部访问，则可以使用这组 apiserver 名称",
"The argument to pass the minikube mount command on start":"用于在启动时传递 minikube 装载命令的参数",
"The authoritative apiserver hostname for apiserver certificates and connectivity. This can be used if you want to make the apiserver available from outside the machine":"用于 apiserver 证书和连接的权威 apiserver 主机名。如果您希望使 apiserver 从计算机外部可用，可以使用此选项",
"The base image to use for docker/podman drivers. Intended for local development.":"Docker/Podman 驱动程序使用的基础映像。用于本地部署。",
"The certificate hostname provided appears to be invalid (may be a minikube bug, try 'minikube delete')":"提供的证书主机名似乎无效（可能是 minikube 的 bug，请尝试 'minikube delete'）",
"The docker-env command is only compatible with the \"docker\" runtime, but this cluster was configured to use the \"{{.runtime}}\" runtime.":"docker-env 命令仅兼容 \"docker\" 运行时，但该集群被配置为使用 \"{{.runtime}}\" 运行时。",
"The following services are clusterIP services: {{.svc_names}}, which are supposed to be accessable inside the cluster only. Minikube allows you to access them by opening an SSH tunnel, which is only for test purpose and must not be used in production environment":"以下服务为ClusterIP类型:{{.svc_names}}. 这些服务正常情况下只能从集群内部访问。Minikube通过ssh隧道的方式使你可以从本机访问这些服务,但此功能仅供测试用途严禁生产环境中使用",
"The hypervisor does not appear to be configured properly. Run 'minikube start --alsologtostderr -v=1' and inspect the error code":"管理程序似乎配置的不正确。执行 'minikube start --alsologtostderr -v=1' 并且检查错误代码",
"The machine-driver specified is failing to start. Try running 'docker-machine-driver-\u003ctype\u003e version'":"指定的设备驱动启动失败。尝试执行 'docker-machine-driver-\u003ctype\u003e version'",
"The minikube {{.driver_name}} container exited unexpectedly.":"",
"The minimum required version for podman is \"{{.minVersion}}\". your version is \"{{.currentVersion}}\". minikube might not work. use at your own risk. To install latest version please see https://podman.io/getting-started/installation.html":"",
"The named space to activate after start":"启动后要激活的命名空间",
"The node to build on. Defaults to the primary control plane.":"要构建的节点，默认为主控制平面",
"The node to check status for. Defaults to control plane. Leave blank with default format for status on all nodes.":"要检查状态的节点，默认为控制平面。默认格式为所有节点上的状态保留为空",
"The node to get IP. Defaults to the primary control plane.":"要获取IP的节点，默认为主控制平面",
"The node to get logs from. Defaults to the primary control plane.":"要从中获取日志的节点，默认为主控制平面",
"The node to get ssh-key path. Defaults to the primary control plane.":"获取ssh密钥路径的节点，默认为主控制平面",
"The node to ssh into. Defaults to the primary control plane.":"要ssh访问的节点，默认为主控制平面",
"The node {{.name}} has ran out of available PIDs.":"节点 {{.name}} 已用完可用PID",
"The node {{.name}} has ran out of disk space.":"节点 {{.name}} 磁盘空间不足",
"The node {{.name}} has ran out of memory.":"节点 {{.name}} 内存不足",
"The node {{.name}} network is not available. Please verify network settings.":"节点 {{.name}} 网络不可用，请检查网络设置",
"The none driver with Kubernetes v1.24+ and the docker container-runtime requires cri-dockerd.\n\t\t\n\t\tPlease install cri-dockerd using these instructions:\n\n\t\thttps://github.com/Mirantis/cri-dockerd":"Kubernetes v1.24+ 和 docker 容器运行时的 none 驱动需要 cri-dockerd。\n\n请使用以下说明安装 cri-dockerd：\n\n\thttps://github.com/Mirantis/cri-dockerd",
"The none driver with Kubernetes v1.24+ and the docker container-runtime requires dockerd.\n\t\t\n\t\tPlease install dockerd using these instructions:\n\n\t\thttps://docs.docker.com/engine/install/":"Kubernetes v1.24+ 和 docker 容器运行时的 none 驱动需要 dockerd。\n\n请使用以下说明安装 dockerd：\n\n\thttps://docs.docker.com/engine/install/",
"The none driver with Kubernetes v1.24+ requires containernetworking-plugins.\n\n\t\tPlease install containernetworking-plugins using these instructions:\n\n\t\thttps://minikube.sigs.k8s.io/docs/faq/#how-do-i-install-containernetworking-plugins-for-none-driver":"",
"The podman service within '{{.cluster}}' is not active":"'{{.cluster}}' 中的 Podman 服务未激活。",
"The podman-env command is incompatible with multi-node clusters. Use the 'registry' add-on: https://minikube.sigs.k8s.io/docs/handbook/registry/":"podman-env 命令与多节点集群不兼容。请使用 'registry' 插件：https://minikube.sigs.k8s.io/docs/handbook/registry/",
"The podman-env command is only compatible with the \"crio\" runtime, but this cluster was configured to use the \"{{.runtime}}\" runtime.":"podman-env 命令仅兼容 \"crio\" 运行时，但该集群被配置为使用 \"{{.runtime}}\" 运行时。",
"The requested memory allocation of {{.requested}}MiB does not leave room for system overhead (total system memory: {{.system_limit}}MiB). You may face stability issues.":"请求的内存分配 {{.requested}}MiB 不足以留出系统开销的空间（总系统内存：{{.system_limit}}MiB）。可能会遇到稳定性问题。",
"The service namespace":"service的命名空间",
"The service/ingress {{.resource}} requires privileged ports to be exposed: {{.ports}}":"service/ingress 的{{.resource}}）需要暴露特权端口：{{.ports}}。",
"There are a couple ways to enable the required file sharing:\n1. Enable \"Use the WSL 2 based engine\" in Docker Desktop\nor\n2. Enable file sharing in Docker Desktop for the %s%s directory":"",
"There's a new version for '{{.driver_executable}}'. Please consider upgrading. {{.documentation_url}}":"“{{.driver_executable}}”有一个新版本。请考虑升级。{{.documentation_url}}",
"This addon does not have an endpoint defined for the 'addons open' command.\nYou can add one by annotating a service with the label {{.labelName}}:{{.addonName}}":"此插件没有为 'addons open' 命令定义端点。\n你可以通过在服务上添加标签 {{.labelName}}:{{.addonName}} 来添加一个端点。",
"This cluster was created before minikube v1.26.0 and doesn't have cri-docker installed. Please run 'minikube delete' and then start minikube again":"此集群是在 minikube v1.26.0 之前创建的，并且未安装 cri-docker。请运行 'minikube delete' 然后重新启动 minikube",
"To access Headlamp, use the following command:\n\n\tminikube{{.profileArg}} service headlamp -n headlamp\n":"",
"To access YAKD - Kubernetes Dashboard, wait for Pod to be ready and run the following command:\n\n\tminikube{{.profileArg}} service yakd-dashboard -n yakd-dashboard\n":"",
"To set your Google Cloud project, run:\n\n\t\tgcloud config set project \u003cproject name\u003e\n\nor set the GOOGLE_CLOUD_PROJECT environment variable.":"",
"To use kubectl or minikube commands as your own user, you may need to relocate them. For example, to overwrite your own settings, run:":"如需以您自己的用户身份使用 kubectl 或 minikube 命令，您可能需要重新定位该命令。例如，如需覆盖您的自定义设置，请运行：",
"Try one or more of the following to free up space on the device:\n\t\n\t\t\t1. Run \"docker system prune\" to remove unused Docker data (optionally with \"-a\")\n\t\t\t2. Increase the storage allocated to Docker for Desktop by clicking on:\n\t\t\t\tDocker icon \u003e Preferences \u003e Resources \u003e Disk Image Size\n\t\t\t3. Run \"minikube ssh -- docker system prune\" if using the Docker container runtime":"",
"Try one or more of the following to free up space on the device:\n\t\n\t\t\t1. Run \"sudo podman system prune\" to remove unused podman data\n\t\t\t2. Run \"minikube ssh -- docker system prune\" if using the Docker container runtime":"",
"Unable to determine a default driver to use. Try specifying --vm-driver, or see https://minikube.sigs.k8s.io/docs/start/":"无法确定要使用的默认驱动。尝试通过 --vm-dirver 指定，或者查阅 https://minikube.sigs.k8s.io/docs/start/",
"Unset the KUBECONFIG environment variable, or verify that it does not point to an empty or otherwise invalid path":"取消 KUBECONFIG 环境变量的设置，或者验证它没有指向空路径或无效路径",
"Upgrade to QEMU v3.1.0+, run 'virt-host-validate', or ensure that you are not running in a nested VM environment.":"升级到 QEMU v3.1.0+，运行 'virt-host-validate'，或者确保您不是在嵌套的 VM 环境中运行",
"Use native Golang SSH client (default true). Set to 'false' to use the command line 'ssh' command when accessing the docker machine. Useful for the machine drivers when they will not start with 'Waiting for SSH'.":"使用原生的Golang SSH客户端（默认为true）。将其设置为 'false' 以在访问 Docker 机器时使用命令行的 'ssh' 命令。对于那些不以 'Waiting for SSH' 开头的机器驱动程序来说非常有用。",
"Using rootless Docker driver was required, but the current Docker does not seem rootless. Try 'docker context use rootless' .":"使用 rootless Docker 驱动是必需的，但当前的 Docker 似乎不是 rootless 的。尝试 'docker context use rootless' 。",
"Using the docker-env command with the containerd runtime is a highly experimental feature, please provide feedback or contribute to make it better":"",
"VM is unable to access {{.repository}}, you may need to configure a proxy or set --image-repository":"虚拟机无权访问 {{.repository}}，或许您需要配置代理或者设置 --image-repository",
"VM may be unable to resolve external DNS records":"虚拟机可能无法解析外部 DNS 记录",
"VirtualBox and Hyper-V are having a conflict. Use '--driver=hyperv' or disable Hyper-V using: 'bcdedit /set hypervisorlaunchtype off'":"VirtualBox 和 Hyper-V 存在冲突。 使用 '--driver=hyperv' 参数或者使用一下命令禁用 Hyper-V : 'bcdedit /set hypervisorlaunchtype off'",
"VirtualBox cannot create a network, probably because it conflicts with an existing network that minikube no longer knows about. Try running 'minikube delete'":"VirtualBox 无法创建网络，可能是因为该网络与现有网络冲突，而 Minikube 不知道该网络的存在。请运行以下命令以删除冲突的网络：'minikube delete'",
"VirtualBox is broken. Disable real-time anti-virus software, reboot, and reinstall VirtualBox if the problem continues.":"VirtualBox 出现问题。禁用实时防病毒软件，重新启动，并在问题继续时重新安装 VirtualBox。",
"Virtualization support is disabled on your computer. If you are running minikube within a VM, try '--driver=docker'. Otherwise, consult your systems BIOS manual for how to enable virtualization.":"您的计算机禁用了虚拟化支持。如果您正在虚拟机内运行 minikube, 尝试 '--driver=docker'。否则，请参阅系统BIOS手册了解如何启用虚拟化。",
"Virtualization support is disabled on your computer. If you are running minikube within a VM, try '--vm-driver=none'. Otherwise, consult your systems BIOS manual for how to enable virtualization.":"您的计算机禁用了虚拟化支持。如果您正在虚拟机内运行 minikube, 尝试 '--vm-driver=none'。否则，请参阅系统BIOS手册了解如何启用虚拟化。",
"Warning: Your kubectl is pointing to stale minikube-vm.\\nTo fix the kubectl context, run `minikube update-context`":"警告：您的 kubectl 指向了过时的 minikube-vm。执行 `minikube update-context` 来修复 kubectl 上下文。",
"Whether to use external switch over Default Switch if virtual switch not explicitly specified. (hyperv driver only)":"是否在未显式指定虚拟开关时使用外部开关而不是默认开关。仅适用于 hyperv 驱动程序。",
"With --network-plugin=cni, you will need to provide your own CNI. See --cni flag as a user-friendly alternative":"使用 --network-plugin=cni，您需要提供自己的 CNI。查看 --cni 标志作为用户友好的替代方法",
"You appear to be using a proxy, but your NO_PROXY environment does not include the minikube IP ({{.ip_address}}). Please see {{.documentation_url}} for more details":"您似乎正在使用代理，但您的 NO_PROXY 环境不包含 minikube IP ({{.ip_address}})。如需了解详情，请参阅 {{.documentation_url}}",
"You are trying to run a windows .exe binary inside WSL. For better integration please use a Linux binary instead (Download at https://minikube.sigs.k8s.io/docs/start/.). Otherwise if you still want to do this, you can do it using --force":"您正在尝试在 WSL 中运行 Windows .exe 二进制文件。为了更好的集成，请改为使用 Linux 二进制文件（在 https://minikube.sigs.k8s.io/docs/start/ 下载）。如果仍然想要执行此操作，您可以使用 --force。",
"You are trying to run the amd64 binary on an M1 system.\nPlease consider running the darwin/arm64 binary instead.\nDownload at {{.url}}":"你正在尝试在 M1 系统上运行 amd64 二进制文件。\n请考虑改用 darwin/arm64 二进制文件。\n下载地址：{{.url}}",
"You cannot change the number of nodes for an existing minikube cluster. Please use 'minikube node add' to add nodes to an existing cluster.":"您不能更改现有 minikube 集群的节点数。请使用 'minikube node add' 向现有集群添加节点。",
"You cannot enable addons on a cluster without Kubernetes, to enable Kubernetes on your cluster, run: minikube start --kubernetes-version=stable":"您不能在没有 Kubernetes 的集群上启用插件，要在你的集群上启用 Kubernetes，运行:minikube start --kubernetes-version=stable",
"You have authenticated with a service account that does not have an associated JSON file. The GCP Auth addon requires credentials with a JSON file in order to continue.":"您已经使用一个没有关联 JSON 文件的服务帐户进行了身份验证。GCP 认证插件需要凭据和 JSON 文件才能继续。",
"You have chosen to disable the CNI but the \"{{.name}}\" container runtime requires CNI":"您已选择禁用 CNI，但是 {{.name}} 容器运行时需要 CNI",
"You have selected \"virtualbox\" driver, but there are better options !\nFor better performance and support consider using a different driver: {{.drivers}}\n\nTo turn off this warning run:\n\n\t$ minikube config set WantVirtualBoxDriverWarning false\n\n\nTo learn more about on minikube drivers checkout https://minikube.sigs.k8s.io/docs/drivers/\nTo see benchmarks checkout https://minikube.sigs.k8s.io/docs/benchmarks/cpuusage/\n\n":"",
"You might be using an amd64 version of minikube on a Apple Silicon Mac, use the arm64 version of minikube instead":"您可能在 Apple Silicon Mac 上使用了 amd64 版本的 minikube，请使用 arm64 版本的 minikube",
"Your firewall is blocking bootpd which is required for socket_vmnet. The following commands will be executed to unblock bootpd:\n\n{{.commands}}\n":"您的防火墙正在阻止 socket_vmnet 所需的 bootpd。将执行以下命令来解除对 bootpd 的阻塞：\n\n{{.commands}}\n",
"Your host does not support KVM virtualization. Ensure that qemu-kvm is installed, and run 'virt-host-validate' to debug the problem":"您的主机不支持 KVM 虚拟化。确保已安装 qemu-kvm，并运行 'virt-host-validate' 来调试问题",
"Your host does not support virtualization. If you are running minikube within a VM, try '--driver=docker'. Otherwise, enable virtualization in your BIOS":"你的主机不支持虚拟化。如果你在虚拟机内运行 minikube，请尝试使用 '--driver=docker'。否则，请在 BIOS 中启用虚拟化",
"Your host is failing to route packets to the minikube VM. If you have VPN software, try turning it off or configuring it so that it does not re-route traffic to the VM IP. If not, check your VM environment routing options.":"",
"[WARNING] For full functionality, the 'csi-hostpath-driver' addon requires the 'volumesnapshots' addon to be enabled.\n\nYou can enable 'volumesnapshots' addon by running: 'minikube addons enable volumesnapshots'\n":"[警告] 为了实现完整功能，'csi-hostpath-driver' 插件需要启用 'volumesnapshots' 插件。\n\n您可以通过运行 'minikube addons enable volumesnapshots' 来启用 'volumesnapshots' 插件。",
"addon '{{.name}}' is currently not enabled.\nTo enable this addon run:\nminikube addons enable {{.name}}":"插件 '{{.name}}' 当前未启用。\n要启用此插件，请运行：minikube addons enable {{.name}}",
"addon '{{.name}}' is not a valid addon packaged with minikube.\nTo see the list of available addons run:\nminikube addons list":"插件 '{{.name}}' 不是 minikube 打包的有效插件。\n要查看可用插件列表，请运行：minikube addons list",
"auto-pause addon is an alpha feature and still in early development. Please file issues to help us make it better.":"auto-pause 插件是一个 Alpha 版功能，仍处于早期开发阶段。请提交问题以帮助我们改进它。",
"if you want to create a profile you can by this command: minikube start -p {{.profile_name}}":"如果你想创建一个配置文件，你可以执行此命令：minikube start -p {{.profile_name}}",
"initialization failed, will try again: {{.error}}":"初始化失败，将再次重试：{{.error}}",
"kubeadm detected a TCP port conflict with another process: probably another local Kubernetes installation. Run lsof -p\u003cport\u003e to find the process and kill it":"kubeadm 检测一个到与其他进程的 TCP 端口冲突：或许是另外的本地安装的 Kubernetes 导致。执行 lsof -p\u003cport\u003e 查找并杀死这些进程",
"minikube does not support the BTRFS storage driver yet, there is a workaround, add the following flag to your start command `--feature-gates=\"LocalStorageCapacityIsolation=false\"`":"minikube 尚不支持 BTRFS 存储驱动程序，有一个解决方法，将以下标志添加到你的启动命令 `--feature-gates=\"LocalStorageCapacityIsolation=false\"`",
"minikube is missing files relating to your guest environment. This can be fixed by running 'minikube delete'":"Minikube 缺少与客户环境相关的文件。这可以通过运行 'minikube delete' 来修复。",
"minikube is unable to access the Google Container Registry. You may need to configure it to use a HTTP proxy.":"minikube 无法访问 Google 容器仓库。您可能需要将其配置为使用 HTTP 代理。",
"minikube is unable to connect to the VM: {{.error}}\n\n\tThis is likely due to one of two reasons:\n\n\t- VPN or firewall interference\n\t- {{.hypervisor}} network configuration issue\n\n\tSuggested workarounds:\n\n\t- Disable your local VPN or firewall software\n\t- Configure your local VPN or firewall to allow access to {{.ip}}\n\t- Restart or reinstall {{.hypervisor}}\n\t- Use an alternative --vm-driver\n\t- Use --force to override this connectivity check\n\t":"minikube 无法连接到虚拟机：{{.error}}\n\n\t可能是以下两个原因之一：\n\n\t- VPN 或防火墙干扰\n\t- {{.hypervisor}} 网络配置问题\n\n\t建议解决方法：\n\n\t- 禁用本地 VPN 或防火墙软件\n\t- 配置本地 VPN 或防火墙以允许访问 {{.ip}}\n\t- 重新启动或重新安装 {{.hypervisor}}\n\t- 使用替代 --vm-driver\n\t- 使用 --force 覆盖此连接性检查\n\t",
"minikube is unable to connect to the VM: {{.error}}\n\nThis is likely due to one of two reasons:\n\n- VPN or firewall interference\n- {{.hypervisor}} network configuration issue\n\nSuggested workarounds:\n\n- Disable your local VPN or firewall software\n- Configure your local VPN or firewall to allow access to {{.ip}}\n- Restart or reinstall {{.hypervisor}}\n- Use an alternative --vm-driver":"minikube 无法连接到虚拟机：{{.error}}\n\n可能是由于以下两个原因之一导致：\n\n-VPN 或防火墙冲突\n- {{.hypervisor}} 网络配置问题\n建议的方案：\n\n- 禁用本地的 VPN 或者防火墙软件\n- 配置本地 VPN 或防火墙软件，放行 {{.ip}}\n- 重启或者重装 {{.hypervisor}}\n- 使用另外的 --vm-driver",
"network to run minikube with. Now it is used by docker/podman and KVM drivers. If left empty, minikube will create a new network.":"运行 minikube 的网络。现在它被 docker/podman 和 KVM 驱动程序使用。如果留空，minikube 将创建一个新的网络。",
"profile sets the current minikube profile, or gets the current profile if no arguments are provided. This is used to run and manage multiple minikube instance. You can return to the default minikube profile by running `minikube profile default`":"profile 命令用于设置当前的 minikube 配置文件，如果没有提供参数，则获取当前配置文件。这用于运行和管理多个 minikube 实例。你可以通过运行 `minikube profile default` 返回默认 minikube 配置文件",
"socket_vmnet was installed with an incorrect group, delete this cluster 'minikube delete' and update the group 'sudo chown root:$(id -ng) /var/run/socket_vmnet' and try again.":"socket_vmnet 安装时使用了错误的组，请删除此集群 'minikube delete' 并更新组 'sudo chown root:$(id -ng) /var/run/socket_vmnet'，然后重试。",
"socket_vmnet was not found on the system, resolve by:\n\n\t\tOption 1) Installing socket_vmnet:\n\n\t\t https://minikube.sigs.k8s.io/docs/drivers/qemu/#networking\n\n\t\tOption 2) Using the user network:\n\n\t\t minikube start{{.profile}} --driver qemu --network user":"在系统上找不到 socket_vmnet，请通过以下方法解决：\n\n\t\t选项 1) 安装 socket_vmnet：\n\n\t\t https://minikube.sigs.k8s.io/docs/drivers/qemu/#networking\n\n\t\t选项 2) 使用用户网络：\n\n\t\t minikube start{{.profile}} --driver qemu --network user",
"too many arguments ({{.ArgCount}}).\nusage: minikube config set PROPERTY_NAME PROPERTY_VALUE":"参数过多（{{.ArgCount}}）。\n用法：minikube config set PROPERTY_NAME PROPERTY_VALUE",
"tunnel creates a route to services deployed with type LoadBalancer and sets their Ingress to their ClusterIP. for a detailed example see https://minikube.sigs.k8s.io/docs/tasks/loadbalancer":"tunnel 创建到以 LoadBalancer 类型部署的服务的路由中，并将其入口设置为其 ClusterIP。有关详细示例，请参阅 https://minikube.sigs.k8s.io/docs/tasks/loadbalancer",
"unsets PROPERTY_NAME from the minikube config file. Can be overwritten by flags or environmental variables":"从 minikube 配置文件中取消设置 PROPERTY_NAME。可以通过标志或环境变量进行覆盖",
"unsets an individual value in a minikube config file":"从 minikube 配置文件中取消设置单个值",
"{{.Driver}} is currently using the {{.StorageDriver}} storage driver, consider switching to overlay2 for better performance":"{{.Driver}} 当前正在使用 {{.StorageDriver}} 存储驱动程序，请考虑切换到 overlay2 以获得更好的性能",
"{{.Driver}} is currently using the {{.StorageDriver}} storage driver, setting preload=false":"{{.Driver}} 当前正在使用 {{.StorageDriver}} 存储驱动, 设置 preload=false",
"{{.addon}} does not currently have an associated maintainer.":"{{.addon}} 目前没有相关的维护者。",
"{{.addon}} is a 3rd party addon and is not maintained or verified by minikube maintainers, enable at your own risk.":"{{.addon}} 是第三方插件，不由 minikube 维护者进行维护或验证，启用需自担风险。",
"{{.addon}} is an addon maintained by {{.maintainer}}. For any concerns contact minikube on GitHub.\nYou can view the list of minikube maintainers at: https://github.com/kubernetes/minikube/blob/master/OWNERS":"{{.addon}} 是由 {{.maintainer}} 维护的插件。如有任何问题，请在 GitHub 上联系 minikube。\n您可以在以下链接查看 minikube 的维护者列表：https://github.com/kubernetes/minikube/blob/master/OWNERS",
"{{.addon}} is maintained by {{.maintainer}} for any concerns contact {{.verifiedMaintainer}} on GitHub.":"{{.addon}} 由 {{.maintainer}} 维护，如有任何问题，请在 GitHub 上联系 {{.verifiedMaintainer}}。",
"{{.driver_name}} \"{{.cluster}}\" {{.machine_type}} is missing, will recreate.":"{{.driver_name}} \"{{.cluster}}\" 缺失 {{.machine_type}}，将重新创建。",
"{{.driver_name}} couldn't proceed because {{.driver_name}} service is not healthy.":"由于 {{.driver_name}} 服务不健康，{{.driver_name}} 无法继续进行。",
"{{.driver_name}} has less than 2 CPUs available, but Kubernetes requires at least 2 to be available":"{{.driver_name}} 可用 CPU 数量不足 2 个，但 Kubernetes 要求至少有 2 个可用 CPU",
"{{.driver_name}} has only {{.container_limit}}MB memory but you specified {{.specified_memory}}MB":"{{.driver_name}} 只有 {{.container_limit}}MB 内存可用，但您指定了 {{.specified_memory}}MB",
"{{.driver}} does not appear to be installed":"似乎并未安装 {{.driver}}",
"{{.driver}} does not appear to be installed, but is specified by an existing profile. Please run 'minikube delete' or install {{.driver}}":"似乎并未安装 {{.driver}}，但已被当前的配置文件指定。请执行 'minikube delete' 或者安装 {{.driver}}",
"{{.driver}} only has {{.size}}MiB available, less than the required {{.req}}MiB for Kubernetes":"{{.driver}} 仅有 {{.size}}MiB 可用，少于 Kubernetes 所需的 {{.req}}MiB",
"{{.n}} is nearly out of disk space, which may cause deployments to fail! ({{.p}}% of capacity). You can pass '--force' to skip this check.":"{{.n}} 的磁盘空间即将耗尽，可能导致部署失败！（已使用容量的{{.p}}%）。您可以传递 '--force' 参数来跳过此检查。",
"{{.n}} is out of disk space! (/var is at {{.p}}% of capacity). You can pass '--force' to skip this check.":"{{.n}} 的磁盘空间已满！（/var 目录已使用 {{.p}}% 的容量）。您可以传递 '--force' 参数跳过此检查。",
"{{.path}} is version {{.client_version}}, and is incompatible with Kubernetes {{.cluster_version}}. You will need to update {{.path}} or use 'minikube kubectl' to connect with this cluster":"{{.path}} 的版本是 {{.client_version}}，且与 Kubernetes {{.cluster_version}} 不兼容。您需要更新 {{.path}} 或者使用 'minikube kubectl' 连接到这个集群",
"{{.path}} is version {{.client_version}}, which may have incompatibilities with Kubernetes {{.cluster_version}}.":"{{.path}} 的版本为 {{.client_version}}，可能与 Kubernetes {{.cluster_version}} 不兼容。",
