Add Korean translation

translations/de.json

@@ -2,9 +2,9 @@
 	"\"The '{{.minikube_addon}}' addon is disabled": "",
 	"\"{{.name}}\" profile does not exist": "",
 	"\"{{.name}}\" profile does not exist, trying anyways.": "",
+	"\"{{.node_name}}\" stopped.": "",
 	"\"{{.profile_name}}\" does not exist, nothing to stop": "",
 	"\"{{.profile_name}}\" host does not exist, unable to show an IP": "",
-	"\"{{.profile_name}}\" stopped.": "",
 	"'none' driver does not support 'minikube docker-env' command": "",
 	"'none' driver does not support 'minikube mount' command": "",
 	"'none' driver does not support 'minikube podman-env' command": "",
@@ -32,14 +32,15 @@
 	"Adds a node to the given cluster config, and starts it.": "",
 	"Adds a node to the given cluster.": "",
 	"Advanced Commands:": "",
+	"After minikube restart the dockerd ports might have changed. To ensure docker-env works properly.\nPlease re-eval the docker-env command:\n\n\t'minikube -p {{.profile_name}} docker-env'": "",
 	"Aliases": "",
 	"Allow user prompts for more information": "",
 	"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": "Alternatives Bild-Repository zum Abrufen von Docker-Images. Dies ist hilfreich, wenn Sie nur eingeschränkten Zugriff auf gcr.io haben. Stellen Sie \\\"auto\\\" ein, dann wählt minikube eins für sie aus. Nutzer vom chinesischen Festland können einen lokalen gcr.io-Mirror wie registry.cn-hangzhou.aliyuncs.com/google_containers verwenden.",
 	"Amount of RAM allocated to the minikube VM (format: \u003cnumber\u003e[\u003cunit\u003e], where unit = b, k, m or g)": "Größe des der minikube-VM zugewiesenen Arbeitsspeichers (Format: \u003cNummer\u003e [\u003cEinheit\u003e], wobei Einheit = b, k, m oder g)",
 	"Amount of RAM allocated to the minikube VM (format: \u003cnumber\u003e[\u003cunit\u003e], where unit = b, k, m or g).": "",
 	"Amount of time to wait for a service in seconds": "",
 	"Amount of time to wait for service in seconds": "",
-	"Another hypervisor, such as VirtualBox, is conflicting with KVM. Please stop the other hypervisor, or use --vm-driver to switch to it.": "",
+	"Another hypervisor, such as VirtualBox, is conflicting with KVM. Please stop the other hypervisor, or use --driver to switch to it.": "",
 	"Automatically selected the {{.driver}} driver": "",
 	"Automatically selected the {{.driver}} driver. Other choices: {{.alternates}}": "",
 	"Available Commands": "",
@@ -54,9 +55,9 @@
 	"Check that minikube is running and that you have specified the correct namespace (-n flag) if required.": "",
 	"Check that the provided apiserver flags are valid": "",
 	"Check that your --kubernetes-version has a leading 'v'. For example: 'v1.1.14'": "",
-	"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": "",
+	"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": "",
 	"Configuration and Management Commands:": "",
-	"Configure a default route on this Linux host, or use another --vm-driver that does not require it": "",
+	"Configure a default route on this Linux host, or use another --driver that does not require it": "",
 	"Configure an external network switch following the official documentation, then add `--hyperv-virtual-switch=\u003cswitch-name\u003e` to `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": "",
 	"Configuring local host environment ...": "",
@@ -117,7 +118,7 @@
 	"Enabling addons: {{.addons}}": "",
 	"Enabling dashboard ...": "",
 	"Ensure that CRI-O is installed and healthy: Run 'sudo systemctl start crio' and 'journalctl -u crio'. Alternatively, use --container-runtime=docker": "",
-	"Ensure that Docker is installed and healthy: Run 'sudo systemctl start docker' and 'journalctl -u docker'. Alternatively, select another value for --vm-driver": "",
+	"Ensure that Docker is installed and healthy: Run 'sudo systemctl start docker' and 'journalctl -u docker'. Alternatively, select another value for --driver": "",
 	"Ensure that the user listed in /etc/libvirt/qemu.conf has access to your home directory": "",
 	"Ensure that your value for HTTPS_PROXY points to an HTTPS proxy rather than an HTTP proxy": "",
 	"Environment variables to pass to the Docker daemon. (format: key=value)": "Umgebungsvariablen, die an den Docker-Daemon übergeben werden. (Format: Schlüssel = Wert)",
@@ -135,12 +136,16 @@
 	"Error getting client: {{.error}}": "",
 	"Error getting cluster": "",
 	"Error getting cluster bootstrapper": "",
+	"Error getting cluster config": "",
 	"Error getting config": "",
+	"Error getting control plane": "",
 	"Error getting host": "",
 	"Error getting host IP": "",
 	"Error getting host status": "",
 	"Error getting machine logs": "",
 	"Error getting port binding for '{{.driver_name}} driver: {{.error}}": "",
+	"Error getting primary control plane": "",
+	"Error getting primary cp": "",
 	"Error getting service status": "",
 	"Error getting service with namespace: {{.namespace}} and labels {{.labelName}}:{{.addonName}}: {{.error}}": "",
 	"Error getting ssh client": "",
@@ -155,6 +160,7 @@
 	"Error parsing Driver version: {{.error}}": "Fehler beim Parsen der Driver-Version: {{.error}}",
 	"Error parsing minikube version: {{.error}}": "Fehler beim Parsen der minikube-Version: {{.error}}",
 	"Error reading {{.path}}: {{.error}}": "",
+	"Error retrieving node": "",
 	"Error starting cluster": "",
 	"Error starting mount": "",
 	"Error starting node": "",
@@ -226,8 +232,8 @@
 	"Group ID:     {{.groupID}}": "",
 	"Have you set up libvirt correctly?": "",
 	"Hide the hypervisor signature from the guest in minikube (kvm2 driver only)": "Hypervisor-Signatur vor dem Gast in minikube verbergen (nur kvm2-Treiber)",
-	"Hyperkit is broken. Upgrade to the latest hyperkit version and/or Docker for Desktop. Alternatively, you may choose an alternate --vm-driver": "",
-	"Hyperkit networking is broken. Upgrade to the latest hyperkit version and/or Docker for Desktop. Alternatively, you may choose an alternate --vm-driver": "",
+	"Hyperkit is broken. Upgrade to the latest hyperkit version and/or Docker for Desktop. Alternatively, you may choose an alternate --driver": "",
+	"Hyperkit networking is broken. Upgrade to the latest hyperkit version and/or Docker for Desktop. Alternatively, you may choose an alternate --driver": "",
 	"If set, automatically updates drivers to the latest version. Defaults to true.": "",
 	"If set, install addons. Defaults to true.": "",
 	"If set, pause all namespaces": "",
@@ -243,7 +249,7 @@
 	"Images Commands:": "",
 	"Insecure Docker registries to pass to the Docker daemon.  The default service CIDR range will automatically be added.": "",
 	"Insecure Docker registries to pass to the Docker daemon. The default service CIDR range will automatically be added.": "Unsichere Docker-Registrys, die an den Docker-Daemon übergeben werden. Der CIDR-Bereich des Standarddienstes wird automatisch hinzugefügt.",
-	"Install VirtualBox, or select an alternative value for --vm-driver": "",
+	"Install VirtualBox, or select an alternative value for --driver": "",
 	"Install the latest hyperkit binary, and run 'minikube delete'": "",
 	"Invalid size passed in argument: {{.error}}": "",
 	"IsEnabled failed": "",
@@ -285,6 +291,7 @@
 	"None of the known repositories in your location are accessible. Using {{.image_repository_name}} as fallback.": "Keines der bekannten Repositories an Ihrem Standort ist zugänglich. {{.image_repository_name}} wird als Fallback verwendet.",
 	"None of the known repositories is accessible. Consider specifying an alternative image repository with --image-repository flag": "Keines der bekannten Repositories ist zugänglich. Erwägen Sie, ein alternatives Image-Repository mit der Kennzeichnung --image-repository anzugeben",
 	"Not passing {{.name}}={{.value}} to docker env.": "",
+	"Noticed that you are using minikube docker-env:": "",
 	"Number of CPUs allocated to the minikube VM": "Anzahl der CPUs, die der minikube-VM zugeordnet sind",
 	"Number of CPUs allocated to the minikube VM.": "",
 	"Number of lines back to go within the log": "",
@@ -304,8 +311,8 @@
 	"Paused kubelet and {{.count}} containers in: {{.namespaces}}": "",
 	"Permissions:  {{.octalMode}} ({{.writtenMode}})": "",
 	"Please enter a value:": "",
-	"Please install the minikube hyperkit VM driver, or select an alternative --vm-driver": "",
-	"Please install the minikube kvm2 VM driver, or select an alternative --vm-driver": "",
+	"Please install the minikube hyperkit VM driver, or select an alternative --driver": "",
+	"Please install the minikube kvm2 VM driver, or select an alternative --driver": "",
 	"Please make sure the service you are looking for is deployed or is in the correct namespace.": "",
 	"Please specify the directory to be mounted: \n\tminikube mount \u003csource directory\u003e:\u003ctarget directory\u003e   (example: \"/host-home:/vm-home\")": "",
 	"Please upgrade the '{{.driver_executable}}'. {{.documentation_url}}": "Aktualisieren Sie '{{.driver_executable}}'. {{.documentation_url}}",
@@ -434,9 +441,9 @@
 	"The minikube VM is offline. Please run 'minikube start' to start it again.": "",
 	"The name of the network plugin": "Der Name des Netzwerk-Plugins",
 	"The name of the network plugin.": "",
-	"The name of the node to add.": "",
 	"The name of the node to delete": "",
 	"The name of the node to start": "",
+	"The node to get logs from. Defaults to the primary control plane.": "",
 	"The number of bytes to use for 9p packet payload": "",
 	"The output format. One of 'json', 'table'": "",
 	"The path on the file system where the docs in markdown need to be saved": "",
@@ -529,12 +536,12 @@
 	"Verifying dashboard health ...": "",
 	"Verifying proxy health ...": "",
 	"Version:      {{.version}}": "",
-	"VirtualBox and Hyper-V are having a conflict. Use '--vm-driver=hyperv' or disable Hyper-V using: 'bcdedit /set hypervisorlaunchtype off'": "",
+	"VirtualBox and Hyper-V are having a conflict. Use '--driver=hyperv' or disable Hyper-V using: '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 is broken. Disable real-time anti-virus software, reboot, and reinstall VirtualBox if the problem continues.": "",
 	"VirtualBox is broken. Reinstall VirtualBox, reboot, and run 'minikube delete'.": "",
 	"VirtualBox is unable to find its network interface. Try upgrading to the latest release and rebooting.": "",
-	"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.": "",
+	"Virtualization support is disabled on your computer. If you are running minikube within a VM, try '--driver=none'. Otherwise, consult your systems BIOS manual for how to enable virtualization.": "",
 	"Wait failed": "",
 	"Wait failed: {{.error}}": "",
 	"Wait until Kubernetes core services are healthy before exiting": "Warten Sie vor dem Beenden, bis die Kerndienste von Kubernetes fehlerfrei arbeiten",
@@ -544,9 +551,10 @@
 	"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": "Sie scheinen einen Proxy zu verwenden, aber Ihre NO_PROXY-Umgebung enthält keine minikube-IP ({{.ip_address}}). Weitere Informationen finden Sie unter {{.documentation_url}}",
 	"You can delete them using the following command(s):": "",
 	"You may need to manually remove the \"{{.name}}\" VM from your hypervisor": "Möglicherweise müssen Sie die VM \"{{.name}}\" manuell von Ihrem Hypervisor entfernen",
+	"You may need to stop the Hyper-V Manager and run `minikube delete` again.": "",
 	"You must specify a service name": "",
 	"Your host does not support KVM virtualization. Ensure that qemu-kvm is installed, and run 'virt-host-validate' to debug the problem": "",
-	"Your host does not support virtualization. If you are running minikube within a VM, try '--vm-driver=none'. Otherwise, enable virtualization in your BIOS": "",
+	"Your host does not support virtualization. If you are running minikube within a VM, try '--driver=none'. Otherwise, enable virtualization in your 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.": "",
 	"Your minikube config refers to an unsupported driver. Erase ~/.minikube, and try again.": "",
 	"Your minikube vm is not running, try minikube start.": "",
@@ -567,11 +575,14 @@
 	"enable failed": "",
 	"error creating clientset": "",
 	"error creating machine client": "",
+	"error getting primary control plane": "",
 	"error getting ssh port": "",
 	"error parsing the input ip address for mount": "",
 	"error starting tunnel": "",
 	"error stopping tunnel": "",
 	"failed to open browser: {{.error}}": "",
+	"getting config": "",
+	"getting primary control plane": "",
 	"if true, will embed the certs in kubeconfig.": "",
 	"if you want to create a profile you can by this command: minikube start -p {{.profile_name}}": "",
 	"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": "",
@@ -585,7 +596,7 @@
 	"minikube addons list --output OUTPUT. json, list": "",
 	"minikube is exiting due to an error. If the above message is not useful, open an issue:": "",
 	"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": "",
+	"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 --driver\n\t- Use --force to override this connectivity check": "",
 	"minikube profile was successfully set to {{.profile_name}}": "",
 	"minikube status --output OUTPUT. json, text": "",
 	"minikube {{.version}} is available! Download it: {{.url}}": "",