Steven Powell
GitHub
commit
aafa5d585a
|
|
@ -1131,7 +1131,7 @@
|
|||
"loading profile": "加载配置文件",
|
||||
"max time to wait per Kubernetes core services to be healthy.": "每个 Kubernetes 核心服务保持健康所需的最长时间。",
|
||||
"max time to wait per Kubernetes or host to be healthy.": "Kubernetes 或主机正常运行前的最大等待时间。",
|
||||
"minikube addons list --output OUTPUT. json, list": "",
|
||||
"minikube addons list --output OUTPUT. json, list": "minikube addons list --output OUTPUT. json, list",
|
||||
"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 exiting due to an error. If the above message is not useful, open an issue:": "由于出错 minikube 正在退出。如果以上信息没有帮助，请提交问题反馈：",
|
||||
"minikube is missing files relating to your guest environment. This can be fixed by running 'minikube delete'": "Minikube 缺少与客户环境相关的文件。这可以通过运行 'minikube delete' 来修复。",
|
||||
|
|
@ -1146,11 +1146,11 @@
|
|||
"minikube service is not currently implemented with the builtin network on QEMU": "minikube 服务目前未在 QEMU 的内置网络上实现",
|
||||
"minikube skips various validations when --force is supplied; this may lead to unexpected behavior": "当提供 --force 参数时，minikube 将跳过各种验证，这可能会导致意外行为",
|
||||
"minikube status --output OUTPUT. json, text": "minikube status --output OUTPUT 可以使用 json 或 text 作为输出格式",
|
||||
"minikube tunnel is not currently implemented with the builtin network on QEMU": "",
|
||||
"minikube tunnel is not currently implemented with the builtin network on QEMU": "minikube tunnel 目前还未与QEMU上的内置网络一起实现",
|
||||
"minikube {{.version}} is available! Download it: {{.url}}": "minikube {{.version}} 现已发布！下载地址：{{.url}}",
|
||||
"mkcmp is used to compare performance of two minikube binaries": "mkcmp 用于对比两个 minikube 二进制的性能",
|
||||
"mount argument \"{{.value}}\" must be in form: \u003csource directory\u003e:\u003ctarget directory\u003e": "",
|
||||
"mount could not connect": "",
|
||||
"mount could not connect": "mount 无法连接",
|
||||
"mount failed": "挂载失败",
|
||||
"namespaces to pause": "需要暂停的命名空间",
|
||||
"namespaces to unpause": "需要取消暂停的命名空间",
|
||||
|
|
@ -1176,14 +1176,14 @@
|
|||
"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",
|
||||
"stat failed": "",
|
||||
"status json failure": "",
|
||||
"status text failure": "",
|
||||
"status json failure": "json 状态错误",
|
||||
"status text failure": "text 状态错误",
|
||||
"too many arguments ({{.ArgCount}}).\nusage: minikube config set PROPERTY_NAME PROPERTY_VALUE": "参数过多（{{.ArgCount}}）。\n用法：minikube config set PROPERTY_NAME PROPERTY_VALUE",
|
||||
"true": "true",
|
||||
"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",
|
||||
"tunnel makes services of type LoadBalancer accessible on localhost": "隧道使本地主机上可以访问 LoadBalancer 类型的服务",
|
||||
"unable to bind flags": "无法绑定标注",
|
||||
"unable to daemonize: {{.err}}": "",
|
||||
"unable to daemonize: {{.err}}": "无法进行后台处理: {{.err}}",
|
||||
"unable to delete minikube config folder": "无法删除 minikube 配置目录",
|
||||
"unpause Kubernetes": "恢复 Kubernetes",
|
||||
"unset failed": "设置失败",
|
||||
|
|
@ -1201,14 +1201,14 @@
|
|||
"usage: minikube config unset PROPERTY_NAME": "用法: minikube config unset PROPERTY_NAME",
|
||||
"usage: minikube delete": "用法: minikube delete",
|
||||
"usage: minikube profile [MINIKUBE_PROFILE_NAME]": "用法: minikube profile [MINIKUBE_PROFILE_NAME]",
|
||||
"version json failure": "",
|
||||
"version yaml failure": "",
|
||||
"version json failure": "json 版本错误",
|
||||
"version yaml failure": "yaml 版本错误",
|
||||
"yaml encoding failure": "yaml 编码失败",
|
||||
"zsh completion failed": "zsh 自动补全失败",
|
||||
"zsh completion.": "zsh 自动补全。",
|
||||
"{{ .name }}: Suggestion: {{ .suggestion}}": "{{ .name }}：建议：{{ .suggestion }}",
|
||||
"{{.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}} 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",
|
||||
|
|
@ -1228,7 +1228,7 @@
|
|||
"{{.name}} was successfully configured": "{{.name}} 成功配置",
|
||||
"{{.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' 参数跳过此检查。",
|
||||
"{{.ociBin}} rmi {{.images}}": "",
|
||||
"{{.ociBin}} rmi {{.images}}": "{{.ociBin}} rmi {{.images}}",
|
||||
"{{.ocibin}} is taking an unusually long time to respond, consider restarting {{.ocibin}}": "{{.ocibin}} 的响应时间过长，请考虑重新启动 {{.ocibin}}",
|
||||
"{{.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}} 不兼容。",
|
||||
|
|
@ -1236,4 +1236,4 @@
|
|||
"{{.profile}} profile is not valid: {{.err}}": "{{.profile}} 配置文件无效：{{.err}}",
|
||||
"{{.type}} is not yet a supported filesystem. We will try anyways!": "{{.type}} 还不是一个受支持的文件系统。无论如何我们都会尝试！",
|
||||
"{{.url}} is not accessible: {{.error}}": "{{.url}} 不可访问：{{.error}}"
|
||||
}
|
||||
}
|
||||
|
|
|
|||
Loading…
Reference in New Issue