Merge pull request #15828 from minikube-bot/gendocs
Update auto-generated docs and translationspull/15836/head
commit
eab6ae5f08
|
@ -23,7 +23,7 @@
|
|||
"--kvm-numa-count range is 1-8": "Der Wertebereich für --kvm-numa-count ist 1-8",
|
||||
"--network flag is only valid with the docker/podman and KVM drivers, it will be ignored": "Der Parameter --network kann nur mit dem docker/podman und den KVM Treibern verwendet werden, er wird ignoriert werden",
|
||||
"--network flag is only valid with the docker/podman, KVM and Qemu drivers, it will be ignored": "",
|
||||
"--network with QEMU must be 'user' or 'socket_vmnet'": "",
|
||||
"--network with QEMU must be 'builtin' or 'socket_vmnet'": "",
|
||||
"--static-ip is only implemented on Docker and Podman drivers, flag will be ignored": "",
|
||||
"--static-ip overrides --subnet, --subnet will be ignored": "",
|
||||
"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) Erstellen Sie den Cluster mit Kubernetes {{.new}} neu, indem Sie folgende Befehle ausführen:\n\t \n\t\t minikube delete{{.profile}}\n\t\t minikube start{{.profile}} --kubernetes-version={{.prefix}}{{.new}}\n\t \n\t\t2) Erstellen Sie einen zweiten Cluster mit Kubernetes {{.new}}, indem Sie folgende Befehle ausführen:\n\t \n\t\t minikube start -p {{.suggestedName}} --kubernetes-version={{.prefix}}{{.new}}\n\t \n\t\t3) Verwenden Sie den existierenden Cluster mit Version {{.old}} von Kubernetes, indem Sie folgende Befehle ausführen:\n\t \n\t\t minikube start{{.profile}} --kubernetes-version={{.prefix}}{{.old}}\n\t\t",
|
||||
|
@ -988,14 +988,14 @@
|
|||
"minikube is not meant for production use. You are opening non-local traffic": "Minikube ist nicht für die Verwendung in Produktion gedacht. Nicht lokaler Traffik wird zugelassen",
|
||||
"minikube is unable to access the Google Container Registry. You may need to configure it to use a HTTP proxy.": "Minikube ist nicht in der Lage auf die Google Container Registry zuzugreifen. Eventuell müssen Sie einen HTTP Proxy konfigurieren.",
|
||||
"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 kann nicht zur VM verbinden: {{.error}}\n\n\tDies ist wahrscheinlich aufgrund einem von zwei Gründen:\n\n\t- VPN oder Firewall Probleme\n\t- {{.hypervisor}} Netzwerk Konfiguration Issue\n\n\tVorgeschlagene Workarounds:\n\n\t- Deaktiviere die lokale VPN oder Firewall Software\n\t- Konfigure das lokale VPN oder die Firewall so, dass Zugriff auf die IP {{.ip}} erlaubt ist\n\t- Restarte oder Reinstalliere {{.hypervisor}}\n\t- Verwende einen alternativen --vm-dirver\n\t- Verwende --force um die Konnektivitäts-Prüfung zu überspringen\n\t",
|
||||
"minikube mount is not currently implemented with the user network on QEMU": "",
|
||||
"minikube mount is not currently implemented with the builtin network on QEMU": "",
|
||||
"minikube profile was successfully set to {{.profile_name}}": "Minikube Profil wurde erfolgreich gesetzt auf {{.profile_name}}",
|
||||
"minikube provisions and manages local Kubernetes clusters optimized for development workflows.": "Minikube provisioniert und managed lokale Kubernetes Cluster optimiert für Entwicklungs-Workflows.",
|
||||
"minikube quickly sets up a local Kubernetes cluster": "Minikube installiert schnell einen lokalen Kubernetes Cluster",
|
||||
"minikube service is not currently implemented with the user network on QEMU": "",
|
||||
"minikube service is not currently implemented with the builtin network on QEMU": "",
|
||||
"minikube skips various validations when --force is supplied; this may lead to unexpected behavior": "Minikube überspringt diverse Validierungen wenn --force angegeben ist; das könnte zu unerwartetem Verhalten führen",
|
||||
"minikube status --output OUTPUT. json, text": "",
|
||||
"minikube tunnel is not currently implemented with the user network on QEMU": "",
|
||||
"minikube tunnel is not currently implemented with the builtin network on QEMU": "",
|
||||
"minikube {{.version}} is available! Download it: {{.url}}": "Minikube {{.version}} ist verfügbar. Lade es herunter: {{.url}}",
|
||||
"mkcmp is used to compare performance of two minikube binaries": "mkcmp wird verwendet um die Performance von zwei Minikube Binaries zu vergleichen",
|
||||
"mount argument \"{{.value}}\" must be in form: \u003csource directory\u003e:\u003ctarget directory\u003e": "Das Argument \"{{.value}}\" für Mount muss in der Form \u003cQuell Verzeichnis\u003e:\u003cZiel Verzeichnis\u003e",
|
||||
|
|
|
@ -24,7 +24,7 @@
|
|||
"--kvm-numa-count range is 1-8": "--kvm-numa-count el rango es 1-8",
|
||||
"--network flag is only valid with the docker/podman and KVM drivers, it will be ignored": "el flag --network es válido solamente con docker/podman y KVM, será ignorado",
|
||||
"--network flag is only valid with the docker/podman, KVM and Qemu drivers, it will be ignored": "",
|
||||
"--network with QEMU must be 'user' or 'socket_vmnet'": "",
|
||||
"--network with QEMU must be 'builtin' or 'socket_vmnet'": "",
|
||||
"--static-ip is only implemented on Docker and Podman drivers, flag will be ignored": "",
|
||||
"--static-ip overrides --subnet, --subnet will be ignored": "",
|
||||
"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": "",
|
||||
|
@ -983,14 +983,14 @@
|
|||
"minikube is not meant for production use. You are opening non-local traffic": "",
|
||||
"minikube is unable to access the Google Container Registry. You may need to configure it to use a HTTP proxy.": "",
|
||||
"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 mount is not currently implemented with the user network on QEMU": "",
|
||||
"minikube mount is not currently implemented with the builtin network on QEMU": "",
|
||||
"minikube profile was successfully set to {{.profile_name}}": "",
|
||||
"minikube provisions and manages local Kubernetes clusters optimized for development workflows.": "",
|
||||
"minikube quickly sets up a local Kubernetes cluster": "",
|
||||
"minikube service is not currently implemented with the user network on QEMU": "",
|
||||
"minikube service is not currently implemented with the builtin network on QEMU": "",
|
||||
"minikube skips various validations when --force is supplied; this may lead to unexpected behavior": "",
|
||||
"minikube status --output OUTPUT. json, text": "",
|
||||
"minikube tunnel is not currently implemented with the user network on QEMU": "",
|
||||
"minikube tunnel is not currently implemented with the builtin network on QEMU": "",
|
||||
"minikube {{.version}} is available! Download it: {{.url}}": "",
|
||||
"mkcmp is used to compare performance of two minikube binaries": "",
|
||||
"mount argument \"{{.value}}\" must be in form: \u003csource directory\u003e:\u003ctarget directory\u003e": "",
|
||||
|
|
|
@ -24,6 +24,7 @@
|
|||
"--kvm-numa-count range is 1-8": "la tranche de --kvm-numa-count est 1 à 8",
|
||||
"--network flag is only valid with the docker/podman and KVM drivers, it will be ignored": "l'indicateur --network est valide uniquement avec les pilotes docker/podman et KVM, il va être ignoré",
|
||||
"--network flag is only valid with the docker/podman, KVM and Qemu drivers, it will be ignored": "L'indicateur --network n'est valide qu'avec les pilotes docker/podman, KVM et Qemu, il sera ignoré",
|
||||
"--network with QEMU must be 'builtin' or 'socket_vmnet'": "",
|
||||
"--network with QEMU must be 'user' or 'socket_vmnet'": "--network avec QEMU doit être 'user' ou 'socket_vmnet'",
|
||||
"--static-ip is only implemented on Docker and Podman drivers, flag will be ignored": "--static-ip n'est implémenté que sur les pilotes Docker et Podman, l'indicateur sera ignoré",
|
||||
"--static-ip overrides --subnet, --subnet will be ignored": "--static-ip remplace --subnet, --subnet sera ignoré",
|
||||
|
@ -965,14 +966,17 @@
|
|||
"minikube is not meant for production use. You are opening non-local traffic": "minikube n'est pas destiné à une utilisation en production. Vous ouvrez du trafic non local",
|
||||
"minikube is unable to access the Google Container Registry. You may need to configure it to use a HTTP proxy.": "minikube ne peut pas accéder à Google Container Registry. Vous devrez peut-être le configurer pour utiliser un proxy 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 ne parvient pas à se connecter à la VM : {{.error}}\n\n\tCela est probablement dû à l'une des deux raisons suivantes :\n\n\t- Interférence VPN ou pare-feu\n\t- {{.hypervisor}} problème de configuration réseau\n\n\tSolutions suggérées :\n\n\t- Désactivez votre logiciel VPN ou pare-feu local\n\t- Configurez votre VPN ou pare-feu local pour autoriser l'accès à {{.ip}}\n \t- Redémarrez ou réinstallez {{.hypervisor}}\n\t- Utilisez un autre --vm-driver\n\t- Utilisez --force pour annuler cette vérification de connectivité\n\t",
|
||||
"minikube mount is not currently implemented with the builtin network on QEMU": "",
|
||||
"minikube mount is not currently implemented with the user network on QEMU": "Le montage minikube n'est pas actuellement implémenté avec le réseau utilisateur sur QEMU",
|
||||
"minikube profile was successfully set to {{.profile_name}}": "Le profil de minikube a été défini avec succès sur {{.profile_name}}",
|
||||
"minikube provisions and manages local Kubernetes clusters optimized for development workflows.": "minikube provisionne et gère des clusters Kubernetes locaux optimisés pour les workflows de développement.",
|
||||
"minikube quickly sets up a local Kubernetes cluster": "minikube configure rapidement un cluster Kubernetes local",
|
||||
"minikube service is not currently implemented with the builtin network on QEMU": "",
|
||||
"minikube service is not currently implemented with the qemu2 driver. See https://github.com/kubernetes/minikube/issues/14146 for details.": "Le service minikube n'est actuellement pas implémenté avec le pilote qemu2. Voir https://github.com/kubernetes/minikube/issues/14146 pour plus de détails.",
|
||||
"minikube service is not currently implemented with the user network on QEMU": "Le service minikube n'est pas actuellement implémenté avec le réseau utilisateur sur QEMU",
|
||||
"minikube skips various validations when --force is supplied; this may lead to unexpected behavior": "minikube ignore diverses validations lorsque --force est fourni ; cela peut conduire à un comportement inattendu",
|
||||
"minikube status --output OUTPUT. json, text": "état minikube --sortie SORTIE. json, texte",
|
||||
"minikube tunnel is not currently implemented with the builtin network on QEMU": "",
|
||||
"minikube tunnel is not currently implemented with the qemu2 driver. See https://github.com/kubernetes/minikube/issues/14146 for details.": "Le tunnel minikube n'est actuellement pas implémenté avec le pilote qemu2. Voir https://github.com/kubernetes/minikube/issues/14146 pour plus de détails.",
|
||||
"minikube tunnel is not currently implemented with the user network on QEMU": "Le tunnel minikube n'est pas actuellement implémenté avec le réseau utilisateur sur QEMU",
|
||||
"minikube {{.version}} is available! Download it: {{.url}}": "minikube {{.version}} est disponible ! Téléchargez-le ici : {{.url}}",
|
||||
|
|
|
@ -23,6 +23,7 @@
|
|||
"--kvm-numa-count range is 1-8": "--kvm-numa-count の範囲は 1~8 です",
|
||||
"--network flag is only valid with the docker/podman and KVM drivers, it will be ignored": "--network フラグは、docker/podman および KVM ドライバーでのみ有効であるため、無視されます",
|
||||
"--network flag is only valid with the docker/podman, KVM and Qemu drivers, it will be ignored": "--network フラグは、docker/podman, KVM および Qemu ドライバーでのみ有効であるため、無視されます",
|
||||
"--network with QEMU must be 'builtin' or 'socket_vmnet'": "",
|
||||
"--network with QEMU must be 'user' or 'socket_vmnet'": "QEMU を用いる場合、--network は、'user' か 'socket_vmnet' でなければなりません",
|
||||
"--static-ip is only implemented on Docker and Podman drivers, flag will be ignored": "",
|
||||
"--static-ip overrides --subnet, --subnet will be ignored": "",
|
||||
|
@ -922,16 +923,17 @@
|
|||
"minikube is not meant for production use. You are opening non-local traffic": "minikube は本番適用を意図されたものではありません。あなたは非ローカルのトラフィックを開こうとしています",
|
||||
"minikube is unable to access the Google Container Registry. You may need to configure it to use a HTTP proxy.": "minikube が Google Container Registry に接続できません。 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 が VM に接続できません: {{.error}}\n\n\t考えられる理由は以下の 2 つです:\n\n\t- VPN またはファイアウォールによる干渉\n\t- {{.hypervisor}} のネットワーク設定の問題\n\n\t回避策には以下があります:\n\n\t- ローカルの VPN またはファイアウォールを無効化\n\t- {{.ip}} へのアクセスを許可するようにローカルの VPN またはファイアウォールを設定\n\t- {{.hypervisor}} を再起動または再インストール\n\t- 代わりの --vm-driver を使用\n\t- --force を使用してこの接続チェックを上書き\n\t",
|
||||
"minikube mount is not currently implemented with the builtin network on QEMU": "",
|
||||
"minikube mount is not currently implemented with the user network on QEMU": "minikube mount は、QEMU 上のユーザーネットワークでは実装されていません",
|
||||
"minikube profile was successfully set to {{.profile_name}}": "無事 minikube のプロファイルが {{.profile_name}} に設定されました",
|
||||
"minikube provisions and manages local Kubernetes clusters optimized for development workflows.": "minikube は、開発ワークフロー用に最適化されたローカル Kubernetes クラスターを構築・管理します。",
|
||||
"minikube quickly sets up a local Kubernetes cluster": "minikube はローカル Kubernetes クラスターを迅速にセットアップします",
|
||||
"minikube service is not currently implemented with the builtin network on QEMU": "",
|
||||
"minikube service is not currently implemented with the qemu2 driver. See https://github.com/kubernetes/minikube/issues/14146 for details.": "minikube サービスは現在、qemu2 ドライバーでは実装されていません。詳細については、https://github.com/kubernetes/minikube/issues/14146 を参照してください。",
|
||||
"minikube service is not currently implemented with the user network on QEMU": "",
|
||||
"minikube skips various validations when --force is supplied; this may lead to unexpected behavior": "minikube は --force が付与された場合、様々な検証をスキップします (これは予期せぬ挙動を引き起こすかも知れません)",
|
||||
"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 qemu2 driver. See https://github.com/kubernetes/minikube/issues/14146 for details.": "minikube トンネルは現在、qemu2 ドライバーでは実装されていません。 詳細については、https://github.com/kubernetes/minikube/issues/14146 を参照してください。",
|
||||
"minikube tunnel is not currently implemented with the user network on QEMU": "",
|
||||
"minikube {{.version}} is available! Download it: {{.url}}": "minikube {{.version}} が利用可能です!次の URL からダウンロードしてください: {{.url}}",
|
||||
"mkcmp is used to compare performance of two minikube binaries": "mkcmp で 2 つの minikube のバイナリーのパフォーマンスを比較できます",
|
||||
"mount argument \"{{.value}}\" must be in form: \u003csource directory\u003e:\u003ctarget directory\u003e": "マウント引数「{{.value}}」は次の形式でなければなりません: \u003cソースディレクトリー\u003e:\u003cターゲットディレクトリー\u003e",
|
||||
|
|
|
@ -28,7 +28,7 @@
|
|||
"--container-runtime must be set to \"containerd\" or \"cri-o\" for rootless": "",
|
||||
"--kvm-numa-count range is 1-8": "--kvm-numa-count 범위는 1부터 8입니다",
|
||||
"--network flag is only valid with the docker/podman, KVM and Qemu drivers, it will be ignored": "--network 는 docker나 podman 에서만 유효합니다. KVM이나 Qemu 드라이버에서는 인자가 무시됩니다",
|
||||
"--network with QEMU must be 'user' or 'socket_vmnet'": "",
|
||||
"--network with QEMU must be 'builtin' or 'socket_vmnet'": "",
|
||||
"--static-ip is only implemented on Docker and Podman drivers, flag will be ignored": "",
|
||||
"--static-ip overrides --subnet, --subnet will be ignored": "",
|
||||
"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": "",
|
||||
|
@ -991,14 +991,14 @@
|
|||
"minikube is not meant for production use. You are opening non-local traffic": "",
|
||||
"minikube is unable to access the Google Container Registry. You may need to configure it to use a HTTP proxy.": "",
|
||||
"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 mount is not currently implemented with the user network on QEMU": "",
|
||||
"minikube mount is not currently implemented with the builtin network on QEMU": "",
|
||||
"minikube profile was successfully set to {{.profile_name}}": "",
|
||||
"minikube provisions and manages local Kubernetes clusters optimized for development workflows.": "minikube는 개발 워크플로우에 최적화된 로컬 쿠버네티스를 제공하고 관리합니다.",
|
||||
"minikube quickly sets up a local Kubernetes cluster": "",
|
||||
"minikube service is not currently implemented with the user network on QEMU": "",
|
||||
"minikube service is not currently implemented with the builtin network on QEMU": "",
|
||||
"minikube skips various validations when --force is supplied; this may lead to unexpected behavior": "",
|
||||
"minikube status --output OUTPUT. json, text": "",
|
||||
"minikube tunnel is not currently implemented with the user network on QEMU": "",
|
||||
"minikube tunnel is not currently implemented with the builtin network on QEMU": "",
|
||||
"minikube {{.version}} is available! Download it: {{.url}}": "minikube {{.version}} 이 사용가능합니다! 다음 경로에서 다운받으세요: {{.url}}",
|
||||
"mkcmp is used to compare performance of two minikube binaries": "",
|
||||
"mount argument \"{{.value}}\" must be in form: \u003csource directory\u003e:\u003ctarget directory\u003e": "",
|
||||
|
|
|
@ -27,7 +27,7 @@
|
|||
"--container-runtime must be set to \"containerd\" or \"cri-o\" for rootless": "",
|
||||
"--kvm-numa-count range is 1-8": "",
|
||||
"--network flag is only valid with the docker/podman, KVM and Qemu drivers, it will be ignored": "",
|
||||
"--network with QEMU must be 'user' or 'socket_vmnet'": "",
|
||||
"--network with QEMU must be 'builtin' or 'socket_vmnet'": "",
|
||||
"--static-ip is only implemented on Docker and Podman drivers, flag will be ignored": "",
|
||||
"--static-ip overrides --subnet, --subnet will be ignored": "",
|
||||
"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": "",
|
||||
|
@ -996,14 +996,14 @@
|
|||
"minikube is not meant for production use. You are opening non-local traffic": "minikube nie jest przeznaczony do użycia w środowisku produkcyjnym. Otwierasz klaster na ruch nielokalny",
|
||||
"minikube is unable to access the Google Container Registry. You may need to configure it to use a HTTP proxy.": "uzyskanie dostępu do Google Container Registry poprzez minikube nie powiodło się. Możliwe, że musisz skonfigurować ustawienia proxy HTTP w minikube",
|
||||
"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 mount is not currently implemented with the user network on QEMU": "",
|
||||
"minikube mount is not currently implemented with the builtin network on QEMU": "",
|
||||
"minikube profile was successfully set to {{.profile_name}}": "profil minikube został z powodzeniem zmieniony na: {{.profile_name}}",
|
||||
"minikube provisions and manages local Kubernetes clusters optimized for development workflows.": "minikube dostarcza lokalne klastry Kubernetesa zoptymalizowane do celów rozwoju oprogramowania oraz zarządza nimi",
|
||||
"minikube quickly sets up a local Kubernetes cluster": "minikube szybko inicjalizuje lokalny klaster Kubernetesa",
|
||||
"minikube service is not currently implemented with the user network on QEMU": "",
|
||||
"minikube service is not currently implemented with the builtin network on QEMU": "",
|
||||
"minikube skips various validations when --force is supplied; this may lead to unexpected behavior": "użycie flagi --force sprawia, że minikube pomija pewne walidacje, co może skutkować niespodziewanym zachowaniem",
|
||||
"minikube status --output OUTPUT. json, text": "",
|
||||
"minikube tunnel is not currently implemented with the user network on QEMU": "",
|
||||
"minikube tunnel is not currently implemented with the builtin network on QEMU": "",
|
||||
"minikube {{.version}} is available! Download it: {{.url}}": "minikube {{.version}} jest dostępne! Pobierz je z: {{.url}}",
|
||||
"mkcmp is used to compare performance of two minikube binaries": "",
|
||||
"mount argument \"{{.value}}\" must be in form: \u003csource directory\u003e:\u003ctarget directory\u003e": "",
|
||||
|
|
|
@ -22,7 +22,7 @@
|
|||
"--container-runtime must be set to \"containerd\" or \"cri-o\" for rootless": "",
|
||||
"--kvm-numa-count range is 1-8": "",
|
||||
"--network flag is only valid with the docker/podman, KVM and Qemu drivers, it will be ignored": "",
|
||||
"--network with QEMU must be 'user' or 'socket_vmnet'": "",
|
||||
"--network with QEMU must be 'builtin' or 'socket_vmnet'": "",
|
||||
"--static-ip is only implemented on Docker and Podman drivers, flag will be ignored": "",
|
||||
"--static-ip overrides --subnet, --subnet will be ignored": "",
|
||||
"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}}\n\t\t",
|
||||
|
@ -915,14 +915,14 @@
|
|||
"minikube is not meant for production use. You are opening non-local traffic": "",
|
||||
"minikube is unable to access the Google Container Registry. You may need to configure it to use a HTTP proxy.": "",
|
||||
"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 mount is not currently implemented with the user network on QEMU": "",
|
||||
"minikube mount is not currently implemented with the builtin network on QEMU": "",
|
||||
"minikube profile was successfully set to {{.profile_name}}": "",
|
||||
"minikube provisions and manages local Kubernetes clusters optimized for development workflows.": "",
|
||||
"minikube quickly sets up a local Kubernetes cluster": "",
|
||||
"minikube service is not currently implemented with the user network on QEMU": "",
|
||||
"minikube service is not currently implemented with the builtin network on QEMU": "",
|
||||
"minikube skips various validations when --force is supplied; this may lead to unexpected behavior": "",
|
||||
"minikube status --output OUTPUT. json, text": "",
|
||||
"minikube tunnel is not currently implemented with the user network on QEMU": "",
|
||||
"minikube tunnel is not currently implemented with the builtin network on QEMU": "",
|
||||
"minikube {{.version}} is available! Download it: {{.url}}": "",
|
||||
"mkcmp is used to compare performance of two minikube binaries": "",
|
||||
"mount argument \"{{.value}}\" must be in form: \u003csource directory\u003e:\u003ctarget directory\u003e": "",
|
||||
|
|
|
@ -22,7 +22,7 @@
|
|||
"--container-runtime must be set to \"containerd\" or \"cri-o\" for rootless": "",
|
||||
"--kvm-numa-count range is 1-8": "",
|
||||
"--network flag is only valid with the docker/podman, KVM and Qemu drivers, it will be ignored": "",
|
||||
"--network with QEMU must be 'user' or 'socket_vmnet'": "",
|
||||
"--network with QEMU must be 'builtin' or 'socket_vmnet'": "",
|
||||
"--static-ip is only implemented on Docker and Podman drivers, flag will be ignored": "",
|
||||
"--static-ip overrides --subnet, --subnet will be ignored": "",
|
||||
"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": "",
|
||||
|
@ -915,14 +915,14 @@
|
|||
"minikube is not meant for production use. You are opening non-local traffic": "",
|
||||
"minikube is unable to access the Google Container Registry. You may need to configure it to use a HTTP proxy.": "",
|
||||
"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 mount is not currently implemented with the user network on QEMU": "",
|
||||
"minikube mount is not currently implemented with the builtin network on QEMU": "",
|
||||
"minikube profile was successfully set to {{.profile_name}}": "",
|
||||
"minikube provisions and manages local Kubernetes clusters optimized for development workflows.": "",
|
||||
"minikube quickly sets up a local Kubernetes cluster": "",
|
||||
"minikube service is not currently implemented with the user network on QEMU": "",
|
||||
"minikube service is not currently implemented with the builtin network on QEMU": "",
|
||||
"minikube skips various validations when --force is supplied; this may lead to unexpected behavior": "",
|
||||
"minikube status --output OUTPUT. json, text": "",
|
||||
"minikube tunnel is not currently implemented with the user network on QEMU": "",
|
||||
"minikube tunnel is not currently implemented with the builtin network on QEMU": "",
|
||||
"minikube {{.version}} is available! Download it: {{.url}}": "",
|
||||
"mkcmp is used to compare performance of two minikube binaries": "",
|
||||
"mount argument \"{{.value}}\" must be in form: \u003csource directory\u003e:\u003ctarget directory\u003e": "",
|
||||
|
|
|
@ -30,7 +30,7 @@
|
|||
"--kvm-numa-count range is 1-8": "--kvm-numa-count 取值范围为 1-8",
|
||||
"--network flag is only valid with the docker/podman and KVM drivers, it will be ignored": "--network 标识仅对 docker/podman 和 KVM 驱动程序有效,它将被忽略",
|
||||
"--network flag is only valid with the docker/podman, KVM and Qemu drivers, it will be ignored": "",
|
||||
"--network with QEMU must be 'user' or 'socket_vmnet'": "",
|
||||
"--network with QEMU must be 'builtin' or 'socket_vmnet'": "",
|
||||
"--static-ip is only implemented on Docker and Podman drivers, flag will be ignored": "",
|
||||
"--static-ip overrides --subnet, --subnet will be ignored": "",
|
||||
"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": "",
|
||||
|
@ -1106,14 +1106,14 @@
|
|||
"minikube is unable to access the Google Container Registry. You may need to configure it to use a HTTP proxy.": "",
|
||||
"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 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",
|
||||
"minikube mount is not currently implemented with the user network on QEMU": "",
|
||||
"minikube mount is not currently implemented with the builtin network on QEMU": "",
|
||||
"minikube profile was successfully set to {{.profile_name}}": "",
|
||||
"minikube provisions and manages local Kubernetes clusters optimized for development workflows.": "",
|
||||
"minikube quickly sets up a local Kubernetes cluster": "",
|
||||
"minikube service is not currently implemented with the user network on QEMU": "",
|
||||
"minikube service is not currently implemented with the builtin network on QEMU": "",
|
||||
"minikube skips various validations when --force is supplied; this may lead to unexpected behavior": "",
|
||||
"minikube status --output OUTPUT. json, text": "",
|
||||
"minikube tunnel is not currently implemented with the user network on QEMU": "",
|
||||
"minikube tunnel is not currently implemented with the builtin network on QEMU": "",
|
||||
"minikube {{.version}} is available! Download it: {{.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": "",
|
||||
|
|
Loading…
Reference in New Issue