"\"{{.context}}\" context has been updated to point to {{.hostname}}:{{.port}}":"Контекст \"{{.context}}\" был обновлён и теперь указывает на {{.hostname}}:{{.port}}",
"\"{{.machineName}}\" does not exist, nothing to stop":"\"{{.machineName}}\" не существует, нечего останавливать",
"\"{{.name}}\" profile does not exist, trying anyways.":"Профиль \"{{.name}}\" не существует, но попробую.",
"'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":"",
"'none' driver does not support 'minikube ssh' command":"",
"'none' driver does not support 'minikube ssh-host' command":"",
"- \"minikube ssh\" to SSH into minikube's node.\n- \"minikube docker-env\" to point your docker-cli to the docker inside minikube.\n- \"minikube image\" to build images without docker.":"",
"- \"minikube ssh\" to SSH into minikube's node.\n- \"minikube image\" to build images without docker.":"",
"- \"minikube ssh\" to SSH into minikube's node.\n- \"minikube podman-env\" to point your podman-cli to the podman inside minikube.\n- \"minikube image\" to build images without docker.":"",
"- Delete and recreate minikube cluster\n\t\tminikube delete\n\t\tminikube start --driver={{.driver_name}}":"",
"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",
"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 Перезапуск\"",
"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. Увеличьте кол-во \"emory\" до {{.recommend}} или выше\n\t\t\t5. Нажмите \"Apply \u0026 Перезапуск\"",
"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. 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\"":"",
"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/":"",
"A firewall is blocking Docker the minikube VM from reaching the image repository. You may need to select --image-repository, or use a proxy.":"",
"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.":"",
"A firewall is likely blocking minikube from reaching the internet. You may need to configure minikube to use a proxy.":"",
"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":"",
"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":"",
"A set of key=value pairs that describe feature gates for alpha/experimental features.":"",
"Access the Kubernetes dashboard running within the minikube cluster":"",
"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":"",
"Add SSH identity key to SSH authentication agent":"",
"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":"",
"Because you are using a Docker driver on {{.operating_system}}, the terminal needs to be open to run it.":"",
"Bind Address: {{.Address}}":"",
"Booting up control plane ...":"",
"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":"",
"Bridge CNI is incompatible with multi-node clusters, use a different CNI":"",
"Build a container image in minikube":"",
"Build a container image, using the container runtime.":"",
"Build image on all nodes.":"",
"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 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":"",
"CNI plug-in to use. Valid options: auto, bridge, calico, cilium, flannel, kindnet, or path to a CNI manifest (default: auto)":"",
"Cache image from docker daemon":"",
"Cache image from remote registry":"",
"Cache image to docker daemon":"",
"Cache image to remote registry":"",
"Cannot find directory {{.path}} for copy":"",
"Cannot find directory {{.path}} for mount":"",
"Cannot use both --output and --format options":"",
"Cannot use the option --no-kubernetes on the {{.name}} driver":"",
"Certificate {{.certPath}} has expired. Generating a new one...":"",
"Check if you have unnecessary pods running by running 'kubectl get po -A":"",
"Check output of 'journalctl -xeu kubelet', try passing --extra-config=kubelet.cgroup-driver=systemd to minikube start":"",
"Check that libvirt is setup properly":"",
"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, and that SELinux is disabled":"",
"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":"",
"Choose a smaller value for --memory, such as 2000":"",
"ChromeOS is missing the kernel support necessary for running Kubernetes":"",
"Cluster was created without any CNI, adding a node to it might cause broken networking.":"",
"Configuration and Management Commands:":"",
"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`":"",
"Configure environment to use minikube's Podman service":"",
"Configures the addon w/ADDON_NAME within minikube (example: minikube addons configure registry-creds). For a list of available addons use: minikube addons list":"",
"Continuously listing/getting the status with optional interval duration.":"",
"Control Plane could not update, try minikube delete --all --purge":"",
"Copy the specified file into minikube":"",
"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\"":"",
"Could not determine a Google Cloud project, which might be ok.":"",
"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.":"",
"Could not process error from failed deletion":"",
"Could not process errors from failed deletion":"",
"Could not resolve IP address":"",
"Country code of the image mirror to be used. Leave empty to use the global one. For Chinese mainland users, set it to cn.":"",
"Disable checking for the availability of hardware virtualization before the vm is started (virtualbox driver only)":"",
"Disable dynamic memory in your VM manager, or pass in a larger --memory value":"",
"Disables the addon w/ADDON_NAME within minikube (example: minikube addons disable dashboard). For a list of available addons use: 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).":"",
"Display dashboard URL instead of opening a browser":"",
"Display the Kubernetes addons URL in the CLI instead of opening it in the default browser":"",
"Display the Kubernetes service URL in the CLI instead of opening it in the default browser":"",
"Display values currently set in the minikube config file":"",
"Display values currently set in the minikube config file.":"",
"Docker Desktop has less than 2 CPUs configured, but Kubernetes requires at least 2 to be available":"",
"Docker Desktop is configured for Windows containers, but Linux containers are required for minikube":"",
"Docker Desktop only has {{.size}}MiB available, less than the required {{.req}}MiB for Kubernetes":"",
"Docker Desktop only has {{.size}}MiB available, you may encounter application deployment failures.":"",
"Docker container exited prematurely after it was created, consider investigating Docker's performance/health.":"",
"Docker has less than 2 CPUs available, but Kubernetes requires at least 2 to be available":"",
"Docker inside the VM is unavailable. Try running 'minikube delete' to reset the VM.":"",
"Docs have been saved at - {{.path}}":"",
"Documentation: {{.url}}":"",
"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":"",
"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":"",
"Enables the addon w/ADDON_NAME within minikube. For a list of available addons use: minikube addons list ":"",
"Enabling '{{.name}}' returned an error: {{.error}}":"",
"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 --driver":"",
"Ensure that the required 'pids' cgroup is enabled on your host: grep pids /proc/cgroups":"",
"Ensure that the user listed in /etc/libvirt/qemu.conf has access to your home directory":"",
"Ensure that you are a member of the appropriate libvirt group (remember to relogin for group changes to take effect!)":"",
"Ensure that your value for HTTPS_PROXY points to an HTTPS proxy rather than an HTTP proxy":"",
"Ensure the tmp directory path is writable to the current user.":"",
"Ensure you have at least 20GB of free disk space.":"",
"Ensure your {{.driver_name}} is running and is healthy.":"",
"Environment variables to pass to the Docker daemon. (format: key=value)":"",
"Environment variables to pass to the build. (format: key=value)":"",
"Error code docs have been saved at - {{.path}}":"",
"Error creating minikube directory":"",
"Error creating view template":"",
"Error detecting shell":"",
"Error executing view template":"",
"Error finding port for mount":"",
"Error generating set output":"",
"Error generating unset output":"",
"Error getting cluster bootstrapper":"",
"Error getting cluster config":"",
"Error getting host":"",
"Error getting port binding for '{{.driver_name}} driver: {{.error}}":"",
"Error getting primary control plane":"",
"Error getting service with namespace: {{.namespace}} and labels {{.labelName}}:{{.addonName}}: {{.error}}":"",
"Error getting ssh client":"",
"Error getting the host IP address to use from within the VM":"",
"For an improved experience it's recommended to use Docker Engine instead of Docker Desktop.\nDocker Engine installation instructions: https://docs.docker.com/engine/install/#server":"",
"Found docker, but the docker service isn't running. Try restarting the docker service.":"",
"Found driver(s) but none were healthy. See above for suggestions how to fix installed drivers.":"",
"Found network options:":"",
"Found {{.number}} invalid profile(s) ! ":"",
"Generate command completion for a shell":"",
"Generate command completion for bash.":"",
"Generate command completion for fish .":"",
"Generate command completion for zsh.":"",
"Generate unable to parse disk size '{{.diskSize}}': {{.error}}":"",
"Generate unable to parse memory '{{.memory}}': {{.error}}":"",
"Generating certificates and keys ...":"",
"Get or list the current profiles (clusters)":"",
"Gets the logs of the running instance, used for debugging minikube, not user code.":"",
"Gets the status of a local Kubernetes cluster":"",
"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)":"",
"Gets the value of PROPERTY_NAME from the minikube config file":"",
"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 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 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":"",
"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":"",
"Hide the hypervisor signature from the guest in minikube (kvm2 driver only)":"",
"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. 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.":"",
"IP Address to use to expose ports (docker and podman driver only)":"",
"IP address (ssh driver only)":"",
"If present, writes to the provided file instead of stdout.":"",
"If set, automatically updates drivers to the latest version. Defaults to true.":"",
"If set, delete the current cluster if start fails and try again. Defaults to false.":"",
"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\"":"",
"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}}":"",
"Images used by this addon. Separated by commas.":"",
"In order to use the fall back image, you need to log in to the github packages registry":"",
"Insecure Docker registries to pass to the Docker daemon. The default service CIDR range will automatically be added.":"",
"Install VirtualBox and ensure it is in the path, or select an alternative value for --driver":"",
"Install the latest hyperkit binary, and run 'minikube delete'":"",
"Invalid port":"",
"Istio needs {{.minCPUs}} CPUs -- your configuration only allocates {{.cpus}} CPUs":"",
"Istio needs {{.minMem}}MB of memory -- your configuration only allocates {{.memory}}MB":"",
"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.":"",
"Kill the mount process spawned by minikube start":"",
"Kubernetes requires at least 2 CPU's to start":"",
"Kubernetes {{.new}} is now available. If you would like to upgrade, specify: --kubernetes-version={{.prefix}}{{.new}}":"Доступен Kubernetes {{.new}}. Для обновления, укажите: --kubernetes-version={{.prefix}}{{.new}}",
"Kubernetes {{.version}} is not supported by this release of minikube":"",
"Local folders to share with Guest via NFS mounts (hyperkit driver only)":"",
"Local proxy ignored: not passing {{.name}}={{.value}} to docker env.":"",
"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)":"",
"Opening Kubernetes service {{.namespace_name}}/{{.service_name}} in default browser...":"",
"Opening service {{.namespace_name}}/{{.service_name}} in default browser...":"",
"Opening {{.url}} in your default browser...":"",
"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 or fish)\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\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":"",
"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 provide a path or url to build":"",
"Please provide an image in the container runtime to save from minikube via \u003cminikube image save IMAGE_NAME\u003e":"",
"Please provide an image in your local daemon to load into minikube via \u003cminikube image load IMAGE_NAME\u003e":"",
"Please provide source and target image":"",
"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":"",
"Please re-eval your podman-env, To ensure your environment variables have updated ports:\n\n\t'minikube -p {{.profile_name}} podman-env'\n\n\t":"",
"Please run `minikube logs --file=logs.txt` and attach logs.txt to the GitHub issue.":"",
"Please see {{.documentation_url}} for more details":"",
"Please specify the directory to be mounted: \n\tminikube mount \u003csource directory\u003e:\u003ctarget directory\u003e (example: \"/host-home:/vm-home\")":"",
"Please specify the path to copy: \n\tminikube cp \u003csource file path\u003e \u003ctarget file absolute path\u003e (example: \"minikube cp a/b.txt /copied.txt\")":"",
"Please try purging minikube using `minikube delete --all --purge`":"",
"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":"",
"Populates the specified folder with documentation in markdown about minikube":"",
"PowerShell is running in constrained mode, which is incompatible with Hyper-V scripting.":"",
"Powering off \"{{.profile_name}}\" via SSH ...":"Выключается \"{{.profile_name}}\" через SSH ...",
"Preparing Kubernetes {{.k8sVersion}} on {{.runtime}} {{.runtimeVersion}} ...":"Подготавливается Kubernetes {{.k8sVersion}} на {{.runtime}} {{.runtimeVersion}} ...",
"Provides instructions to point your terminal's docker-cli to the Docker Engine inside minikube. (Useful for building docker images directly inside minikube)":"",
"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":"",
"Registries used by this addon. Separated by commas.":"",
"Registry addon with {{.driver}} driver uses port {{.port}} please use that instead of default port 5000":"",
"Registry mirrors to pass to the Docker daemon":"",
"Reinstall VirtualBox and reboot. Alternatively, try the kvm2 driver: https://minikube.sigs.k8s.io/docs/reference/drivers/kvm2/":"",
"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":"",
"Related issue: {{.url}}":"",
"Related issues:":"",
"Remove one or more images":"",
"Remove the invalid --docker-opt or --insecure-registry flag if one was provided":"",
"Removed all traces of the \"{{.name}}\" cluster.":"",
"Removing {{.directory}} ...":"",
"Requested cpu count {{.requested_cpus}} is greater than the available cpus of {{.avail_cpus}}":"",
"Requested cpu count {{.requested_cpus}} is less than the minimum allowed of {{.minimum_cpus}}":"",
"Requested memory allocation ({{.requested}}MB) is less than the recommended minimum {{.recommend}}MB. Deployments may fail.":"",
"Requested memory allocation {{.requested}}MB is more than your system limit {{.system_limit}}MB.":"",
"Requested memory allocation {{.requested}}MiB is less than the usable minimum of {{.minimum_memory}}MB":"",
"Reset Docker to factory defaults":"",
"Restart Docker":"",
"Restart Docker, Ensure docker is running and then run: 'minikube delete' and then 'minikube start' again":"",
"Restarting existing {{.driver_name}} {{.machine_type}} for \"{{.cluster}}\" ...":"Перезагружается существующий {{.driver_name}} {{.machine_type}} для \"{{.cluster}}\" ...",
"Restarting the {{.name}} service may improve performance.":"",
"Retrieve the ssh host key of the specified node":"",
"Retrieve the ssh host key of the specified node.":"",
"Retrieve the ssh identity key path of the specified node":"",
"Retrieve the ssh identity key path of the specified node, and writes it to STDOUT.":"",
"Retrieves the IP address of the running cluster, checks it\n\t\t\twith IP in kubeconfig, and corrects kubeconfig if incorrect.":"",
"Retrieves the IP address of the specified node":"",
"Retrieves the IP address of the specified node, and writes it to STDOUT.":"",
"Returns a URL to connect to a service":"",
"Returns logs to debug a local Kubernetes cluster":"",
"Returns the value of PROPERTY_NAME from the minikube config file. Can be overwritten at runtime by flags or environmental variables.":"",
"Right-click the PowerShell icon and select Run as Administrator to open PowerShell in elevated mode.":"",
"Run 'kubectl describe pod coredns -n kube-system' and check for a firewall or DNS conflict":"",
"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":"",
"Run 'sudo sysctl fs.protected_regular=0', or try a driver which does not require root, such as '--driver=docker'":"",
"Run a kubectl binary matching the cluster version":"",
"Run minikube from the C: drive.":"",
"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'":"",
"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)":"",
"Show only the most recent journal entries, and continuously print new entries as they are appended to the journal.":"",
"Simulate numa node count in minikube, supported numa node count range is 1-8 (kvm2 driver only)":"",
"Skipped switching kubectl context for {{.profile_name}} because --keep-context was set.":"",
"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":"",
"Sorry, Kubernetes {{.k8sVersion}} requires conntrack to be installed in root's path":"",
"Sorry, completion support is not yet implemented for {{.name}}":"",
"Sorry, please set the --output flag to one of the following valid options: [text,json]":"",
"Sorry, the IP provided with the --listen-address flag is invalid: {{.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":"",
"Sorry, the kubeadm.{{.parameter_name}} parameter is currently not supported by --extra-config":"",
"Sorry, the url provided with the --registry-mirror flag is invalid: {{.url}}":"",
"Sorry, {{.driver}} does not allow mounts to be changed after container creation (previous mount: '{{.old}}', new mount: '{{.new}})'":"",
"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.":"",
"Specify --kubernetes-version in v\u003cmajor\u003e.\u003cminor.\u003cbuild\u003e form. example: 'v1.1.14'":"",
"Specify an alternate --host-only-cidr value, such as 172.16.0.1/24":"",
"Specify arbitrary flags to pass to the Docker daemon. (format: key=value)":"",
"Specify arbitrary flags to pass to the build. (format: key=value)":"",
"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.":"",
"StartHost failed, but will try again: {{.error}}":"",
"Starting control plane node {{.name}} in cluster {{.cluster}}":"Запускается control plane узел {{.name}} в кластере {{.cluster}}",
"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.":"",
"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)":"",
"The VM driver crashed. Run 'minikube start --alsologtostderr -v=8' to see the VM driver error message":"",
"The VM driver exited with an error, and may be corrupt. Run 'minikube start' with --alsologtostderr -v=8 to see the error":"",
"The VM that minikube is configured for no longer exists. Run 'minikube delete'":"",
"The ambassador addon has stopped working as of v1.23.0, for more details visit: https://github.com/datawire/ambassador-operator/issues/73":"",
"The apiserver listening port":"",
"The argument to pass the minikube mount command on start.":"",
"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":"",
"The base image to use for docker/podman drivers. Intended for local development.":"",
"The certificate hostname provided appears to be invalid (may be a minikube bug, try 'minikube delete')":"",
"The cluster dns domain name used in the Kubernetes cluster":"",
"The cluster {{.cluster}} already exists which means the --nodes parameter will be ignored. Use \"minikube node add\" to add nodes to an existing cluster.":"",
"The control plane for \"{{.name}}\" is paused!":"",
"The control plane node \"{{.name}}\" does not exist.":"",
"The control plane node is not running (state={{.state}})":"",
"The control plane node must be running for this command":"",
"The cri socket path to be used.":"",
"The docker-env command is incompatible with multi-node clusters. Use the 'registry' add-on: https://minikube.sigs.k8s.io/docs/handbook/registry/":"",
"The docker-env command is only compatible with the \"docker\" runtime, but this cluster was configured to use the \"{{.runtime}}\" runtime.":"",
"The driver '{{.driver}}' is not supported on {{.os}}/{{.arch}}":"",
"The existing \"{{.name}}\" cluster was created using the \"{{.old}}\" driver, which is incompatible with requested \"{{.new}}\" driver.":"",
"The existing node configuration appears to be corrupt. Run 'minikube delete'":"",
"The heapster addon is depreciated. please try to disable metrics-server instead":"",
"The hyperv virtual switch name. Defaults to first found. (hyperv driver only)":"",
"The hypervisor does not appear to be configured properly. Run 'minikube start --alsologtostderr -v=1' and inspect the error code":"",
"The image '{{.imageName}}' was not found; unable to add it to cache.":"",
"The initial time interval for each check that wait performs in seconds":"",
"The kubeadm binary within the Docker container is not executable":"",
"The machine-driver specified is failing to start. Try running 'docker-machine-driver-\u003ctype\u003e version'":"",
"The minikube VM is offline. Please run 'minikube start' to start it again.":"",
"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.":"",
"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.":"",
"The node to ssh into. Defaults to the primary control plane.":"",
"The node {{.name}} has ran out of available PIDs.":"",
"The node {{.name}} has ran out of disk space.":"",
"The node {{.name}} has ran out of memory.":"",
"The node {{.name}} network is not available. Please verify network settings.":"",
"The none driver is not compatible with multi-node clusters.":"",
"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":"",
"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/":"",
"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.":"",
"The service namespace":"",
"The service/ingress {{.resource}} requires privileged ports to be exposed: {{.ports}}":"",
"The time interval for each check that wait performs in seconds":"",
"The value passed to --format is invalid":"",
"The value passed to --format is invalid: {{.error}}":"",
"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":"",
"These --extra-config parameters are invalid: {{.invalid_extra_opts}}":"",
"These changes will take effect upon a minikube delete and then a minikube start":"",
"Things to try without Kubernetes ...":"",
"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}}":"",
"This can also be done automatically by setting the env var CHANGE_MINIKUBE_NONE_USER=true":"",
"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":"",
"To pull new external images, you may need to configure a proxy: https://minikube.sigs.k8s.io/docs/reference/networking/proxy/":"",
"To see addons list for other profiles use: `minikube addons -p name list`":"",
"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 start a cluster, run: \"{{.command}}\"":"",
"To start minikube with Hyper-V, Powershell must be in your PATH`":"",
"To use kubectl or minikube commands as your own user, you may need to relocate them. For example, to overwrite your own settings, run:":"",
"Troubleshooting Commands:":"",
"Try 'minikube delete' to force new SSL certificates to be installed":"",
"Try 'minikube delete', and disable any conflicting VPN or firewall software":"",
"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":"",
"Use SSH connection instead of HTTPS (port 2376)":"",
"Use SSH for running kubernetes client on the node":"",
"Use VirtualBox to remove the conflicting VM and/or network interfaces":"",
"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'.":"",
"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 '--driver=docker'. Otherwise, consult your systems BIOS manual for how to enable virtualization.":"",
"Wait failed: {{.error}}":"",
"Want kubectl {{.version}}? Try 'minikube kubectl -- get pods -A'":"",
"Where to root the NFS Shares, defaults to /nfsshares (hyperkit driver only)":"",
"Whether to use external switch over Default Switch if virtual switch not explicitly specified. (hyperv driver only)":"",
"With --network-plugin=cni, you will need to provide your own CNI. See --cni flag as a user-friendly alternative":"",
"You appear to be using a proxy, but your NO_PROXY environment does not include the minikube IP ({{.ip_address}}).":"",
"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":"",
"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.":"",
"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 may need to manually remove the \"{{.name}}\" VM from your hypervisor":"",
"You may need to stop the Hyper-V Manager and run `minikube delete` again.":"",
"You might be using an amd64 version of minikube on a M1 Mac, use the arm64 version of minikube instead":"",
"Your GCP credentials will now be mounted into every pod created in the {{.name}} cluster.":"",
"Your cgroup does not allow setting memory.":"",
"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 '--driver=docker'. 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.":"",
"[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":"",
"addon '{{.name}}' is currently not enabled.\nTo enable this addon run:\nminikube addons enable {{.name}}":"",
"addon '{{.name}}' is not a valid addon packaged with minikube.\nTo see the list of available addons run:\nminikube addons list":"",
"addons modifies minikube addons files using subcommands like \"minikube addons enable dashboard\"":"",
"keep the kube-context active after cluster is stopped. Defaults to false.":"",
"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":"",
"kubectl and minikube configuration will be stored in {{.home_folder}}":"",
"kubectl not found. If you need it, try: 'minikube kubectl -- get pods -A'":"",
"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 is missing files relating to your guest environment. This can be fixed by running 'minikube delete'":"",
"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":"",
"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`":"",
"provisioning host for node":"",
"reload cached images.":"",
"reloads images previously added using the 'cache add' subcommand":"",
"retrieving node":"",
"scheduled stop is not supported on the none driver, skipping scheduling":"",
"service {{.namespace_name}}/{{.service_name}} has no node port":"",
"socket_vmnet was installed with an incorrect group, delete this cluster 'minikube delete' and update the group 'sudo chown root:$(stat -f \"%Sg\" ~) /var/run/socket_vmnet' and try again.":"",
"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":"",
"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":"",
"unable to bind flags":"",
"unable to daemonize: {{.err}}":"",
"unable to delete minikube config folder":"",
"unpause Kubernetes":"",
"unset failed":"",
"unsets PROPERTY_NAME from the minikube config file. Can be overwritten by flags or environmental variables":"",
"unsets an individual value in a minikube config file":"",
"{{.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}} is maintained by {{.maintainer}} for any concerns contact {{.verifiedMaintainer}} on GitHub.":"",
"{{.driver_name}} \"{{.cluster}}\" {{.machine_type}} is missing, will recreate.":"",
"{{.driver_name}} couldn't proceed because {{.driver_name}} service is not healthy.":"",
"{{.driver_name}} has less than 2 CPUs available, but Kubernetes requires at least 2 to be available":"",
"{{.driver_name}} has only {{.container_limit}}MB memory but you specified {{.specified_memory}}MB":"",
"{{.driver}} only has {{.size}}MiB available, less than the required {{.req}}MiB for Kubernetes":"",
"{{.name}} doesn't have images.":"",
"{{.name}} has following images:":"",
"{{.name}} has no available configuration options":"",
"{{.name}} is already running":"",
"{{.name}} was successfully configured":"",
"{{.n}} is nearly out of disk space, which may cause deployments to fail! ({{.p}}% of capacity)":"В {{.n}} заканчивается место на диске, что может привести к проблемам в работе! ({{.p}}% занято)",
