"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":"Dostęp do dashboardu uruchomionego w klastrze kubernetesa w minikube",
"Add an image to local cache.":"",
"Add machine IP to NO_PROXY environment variable":"",
"Add, delete, or push a local image into minikube":"",
"Add, remove, or list additional nodes":"",
"Adding node {{.name}} to cluster {{.cluster}}":"",
"Additional help topics":"Dodatkowe tematy pomocy",
"Additional mount options, such as cache=fscache":"Dodatkowe opcje montowania, jak na przykład cache=fscache",
"Adds a node to the given cluster config, and starts it.":"",
"Adds a node to the given cluster.":"",
"Advanced Commands:":"Zaawansowane komendy",
"Aliases":"Aliasy",
"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":"",
"Amount of RAM allocated to the minikube VM (format: \u003cnumber\u003e[\u003cunit\u003e], where unit = b, k, m or g)":"Ilość zarezerwowanej pamięci RAM dla maszyny wirtualnej minikube (format: \u003cnumber\u003e[\u003cunit\u003e], where unit = b, k, m or )",
"Amount of RAM allocated to the minikube VM (format: \u003cnumber\u003e[\u003cunit\u003e], where unit = b, k, m or g).":"Ilość zarezerwowanej pamięci RAM dla maszyny wirtualnej minikube (format: \u003cnumber\u003e[\u003cunit\u003e], where unit = b, k, m or )",
"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":"",
"Check that minikube is running and that you have specified the correct namespace (-n flag) if required.":"Upewnij się, że minikube zostało uruchomione i że podano poprawną przestrzeń nazw (flaga -n) celem zamontowania",
"Check that your --kubernetes-version has a leading 'v'. For example: 'v1.1.14'":"Upewnij się, że --kubernetes-version ma 'v' z przodu. Na przykład `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 --driver=none":"",
"Choose a smaller value for --memory, such as 2000":"",
"Configuration and Management Commands:":"Polecenia konfiguracji i zarządzania",
"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 Docker daemon":"",
"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":"",
"Configuring environment for Kubernetes {{.k8sVersion}} on {{.runtime}} {{.runtimeVersion}}":"Konfigurowanie środowiska dla Kubernetesa w wersji {{.k8sVersion}} na {{.runtime}} {{.runtimeVersion}}",
"Configuring local host environment ...":"Konfigurowanie lokalnego środowiska hosta...",
"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.":"",
"Deletes a local kubernetes cluster. This command deletes the VM, and removes all\nassociated files.":"Usuwa lokalny klaster kubernetesa. Ta komenda usuwa maszynę wirtualną i wszystkie powiązane pliki.",
"Deletes a local kubernetes cluster. This command deletes the VM, and removes all associated files.":"Usuwa lokalny klaster kubernetesa. Ta komenda usuwa maszynę wirtualną i wszystkie powiązane pliki.",
"Disables the addon w/ADDON_NAME within minikube (example: minikube addons disable dashboard). For a list of available addons use: minikube addons list ":"",
"Due to issues with CRI-O post v1.17.3, we need to restart your cluster.":"",
"Due to networking limitations of driver {{.driver_name}} on {{.os_name}}, {{.addon_name}} addon is not supported.\nAlternatively to use this addon you can use a vm-based driver:\n\n\t'minikube start --vm=true'\n\nTo track the update on this work in progress feature please check:\nhttps://github.com/kubernetes/minikube/issues/7332":"",
"Due to networking limitations of driver {{.driver_name}}, {{.addon_name}} addon is not supported. Try using a different driver.":"",
"Enables the addon w/ADDON_NAME within minikube (example: minikube addons enable dashboard). 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 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":"",
"Ensure your {{.driver_name}} is running and is healthy.":"",
"Environment variables to pass to the Docker daemon. (format: key=value)":"Zmienne środowiskowe do przekazania do demona docker (format: klucz-wartość)",
"Error: You have selected Kubernetes v{{.new}}, but the existing cluster for your profile is running Kubernetes v{{.old}}. Non-destructive downgrades are not supported, but you can proceed by performing one of the following options:\n* Recreate the cluster using Kubernetes v{{.new}}: Run \"minikube delete {{.profile}}\", then \"minikube start {{.profile}} --kubernetes-version={{.new}}\"\n* Create a second cluster with Kubernetes v{{.new}}: Run \"minikube start -p \u003cnew name\u003e --kubernetes-version={{.new}}\"\n* Reuse the existing cluster with Kubernetes v{{.old}} or newer: Run \"minikube start {{.profile}} --kubernetes-version={{.old}}":"Erreur : Vous avez sélectionné Kubernetes v{{.new}}, mais le cluster existent pour votre profil exécute Kubernetes v{{.old}}. Les rétrogradations non-destructives ne sont pas compatibles. Toutefois, vous pouvez poursuivre le processus en réalisant l'une des trois actions suivantes :\n* Créer à nouveau le cluster en utilisant Kubernetes v{{.new}} – exécutez \"minikube delete {{.profile}}\", puis \"minikube start {{.profile}} --kubernetes-version={{.new}}\".\n* Créer un second cluster avec Kubernetes v{{.new}} – exécutez \"minikube start -p \u003cnew name\u003e --kubernetes-version={{.new}}\".\n* Réutiliser le cluster existent avec Kubernetes v{{.old}} ou version ultérieure – exécutez \"minikube start {{.profile}} --kubernetes-version={{.old}}\".",
"Examples":"Przykłady",
"Executing \"{{.command}}\" took an unusually long time: {{.duration}}":"",
"Existing disk is missing new features ({{.error}}). To upgrade, run 'minikube delete'":"",
"Gets the logs of the running instance, used for debugging minikube, not user code.":"Pobiera logi z aktualnie uruchomionej instancji. Przydatne do debugowania kodu, który nie należy do aplikacji użytkownika",
"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 status of a local kubernetes cluster":"Pobiera aktualny status klastra kubernetesa",
"Gets the value of PROPERTY_NAME from the minikube config file":"",
"Global Flags":"",
"Go template format string for the cache list output. The format for Go templates can be found here: https://golang.org/pkg/text/template/\nFor the list of accessible variables for the template, see the struct values here: https://godoc.org/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://golang.org/pkg/text/template/\nFor the list of accessible variables for the template, see the struct values here: https://godoc.org/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://golang.org/pkg/text/template/\nFor the list accessible variables for the template, see the struct values here: https://godoc.org/k8s.io/minikube/cmd/minikube/cmd#Status":"",
"Group ID: {{.groupID}}":"",
"Have you set up libvirt correctly?":"Czy napewno skonfigurowano libvirt w sposób prawidłowy?",
"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. 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, delete the current cluster if start fails and try again. Defaults to false.":"",
"If set, download tarball of preloaded images if available to improve start time. Defaults to true.":"",
"If set, force the container runtime to use sytemd as cgroup manager. Currently available for docker and crio. Defaults to false.":"",
"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)":"",
"Location of the minikube iso":"Ścieżka do obrazu iso minikube",
"Location of the minikube iso.":"Ścieżka do obrazu iso minikube",
"Locations to fetch the minikube ISO from.":"",
"Log into or run a command on a machine with SSH; similar to 'docker-machine ssh'":"Zaloguj się i wykonaj polecenie w maszynie za pomocą ssh. Podobne do 'docker-machine ssh'",
"Log into or run a command on a machine with SSH; similar to 'docker-machine ssh'.":"Zaloguj się i wykonaj polecenie w maszynie za pomocą ssh. Podobne do 'docker-machine ssh'",
"Log into the minikube environment (for debugging)":"",
"Message Size: {{.size}}":"",
"Modify persistent configuration values":"",
"Most users should use the newer 'docker' driver instead, which does not require root!":"",
"Mount type: {{.name}}":"",
"Mounting host path {{.sourcePath}} into VM as {{.destinationPath}} ...":"",
"Mounts the specified directory into minikube":"Montuje podany katalog wewnątrz minikube",
"Mounts the specified directory into minikube.":"Montuje podany katalog wewnątrz minikube",
"Multi-node clusters are currently experimental and might exhibit unintended behavior.":"",
"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":"",
"Please either authenticate to the registry or use --base-image flag to use a different registry.":"",
"Please enter a value:":"Wprowadź wartość",
"Please free up disk or prune images.":"",
"Please increse Desktop's disk size.":"",
"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.":"Proszę upewnij się, że serwis którego szukasz znajduje się w prawidłowej przestrzeni nazw",
"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 upgrade the '{{.driver_executable}}'. {{.documentation_url}}":"Proszę zaktualizować '{{.driver_executable}}'. {{.documentation_url}}",
"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":"",
"Reboot to complete VirtualBox installation, and verify that VirtualBox is not blocked by your system":"Uruchom ponownie komputer aby zakończyć instalację VirtualBox'a i upewnij się, że nie jest on blokowany przez twój system",
"Reboot to complete VirtualBox installation, verify that VirtualBox is not blocked by your system, and/or use another hypervisor":"",
"Rebuild libvirt with virt-network support":"",
"Received {{.name}} signal":"",
"Registry addon on with {{.driver}} uses {{.port}} please use that instead of default 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":"",
"Restart Docker, Ensure docker is running and then run: 'minikube delete' and then 'minikube start' again":"",
"Restarting existing {{.driver_name}} {{.machine_type}} for \"{{.cluster}}\" ...":"",
"Restarting the {{.name}} service may improve performance.":"",
"Retrieve the ssh identity key path of the specified cluster":"Pozyskuje ścieżkę do klucza ssh dla wyspecyfikowanego klastra",
"Retrieve the ssh identity key path of the specified cluster.":"Pozyskuje ścieżkę do klucza ssh dla wyspecyfikowanego klastra.",
"Retrieves the IP address of the running cluster":"Pobiera adres IP aktualnie uruchomionego klastra",
"Retrieves the IP address of the running cluster, and writes it to STDOUT.":"Pobiera adres IP aktualnie uruchomionego klastra i wypisuje go do STDOUT",
"Retrieves the IP address of the running cluster, checks it\n\t\t\twith IP in kubeconfig, and corrects kubeconfig if incorrect.":"",
"Returns a URL to connect to a service":"",
"Returns logs to debug a local Kubernetes cluster":"",
"Returns the Kubernetes URL for a service in your local cluster. In the case of multiple URLs they will be printed one at a time.":"",
"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 kubectl":"Uruchamia kubectl",
"Run minikube from the C: drive.":"",
"Run the Kubernetes client, download it if necessary. Remember -- after kubectl!\n\nExamples:\nminikube kubectl -- --help\nminikube kubectl -- get pods --namespace kube-system":"",
"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 failed":"",
"Set flag to delete all profiles":"",
"Set flag to stop all profiles (clusters)":"",
"Set this flag to delete the '.minikube' folder from your user directory.":"",
"Sets an individual value in a minikube config file":"",
"Sets the PROPERTY_NAME config value to PROPERTY_VALUE\n\tThese values can be overwritten by flags or environment variables at runtime.":"",
"Sets up docker env variables; similar to '$(docker-machine env)'":"Ustawia zmienne środowiskowe dockera. Podobne do `(docker-machine env)`",
"Sets up docker env variables; similar to '$(docker-machine env)'.":"Ustawia zmienne środowiskowe dockera. Podobne do `(docker-machine env)`",
"Sets up podman env variables; similar to '$(podman-machine env)'.":"",
"Setting profile failed":"Ustawianie profilu nie powiodło się",
"Show a list of global command-line options (applies to all commands).":"",
"Show only log entries which point to known problems":"Pokaż logi które wskazują na znane problemy",
"Show only the most recent journal entries, and continuously print new entries as they are appended to the journal.":"",
"Skipped switching kubectl context for {{.profile_name}} because --keep-context was set.":"Zignorowano zmianę kontekstu kubectl ponieważ --keep-context zostało przekazane",
"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":"",
"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.":"",
"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 apiserver listening port":"API nasłuchuje na porcie:",
"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 cluster {{.cluster}} already exists which means the --nodes parameter will be ignored. Use \"minikube node add\" to add nodes to an existing cluster.":"",
"The container runtime to be used (docker, crio, containerd)":"Runtime konteneryzacji (docker, crio, containerd).",
"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 service is currently not active":"Serwis docker jest nieaktywny",
"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 kubernetes version that the minikube VM will use (ex: v1.2.3)":"Wersja kubernetesa, która zostanie użyta przez wirtualną maszynę minikube (np. v1.2.3)",
"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 name of the network plugin":"Nazwa pluginu sieciowego",
"The name of the network plugin.":"Nazwa pluginu sieciowego",
"The node to check status for. Defaults to control plane. Leave blank with default format for status on all nodes.":"",
"The node to get logs from. 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 number of bytes to use for 9p packet payload":"",
"The number of nodes to spin up. Defaults to 1.":"",
"The output format. One of 'json', 'table'":"",
"The path on the file system where the docs in markdown need to be saved":"",
"The podman service within '{{.cluster}}' is not active":"",
"The podman-env command is incompatible with multi-node clusters. Use the 'registry' add-on: https://minikube.sigs.k8s.io/docs/handbook/registry/":"",
"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 {{.service}} requires privileged ports to be exposed: {{.ports}}":"",
"The services namespace":"",
"The time interval for each check that wait performs in seconds":"",
"The value passed to --format is invalid":"Wartość przekazana do --format jest nieprawidłowa",
"The value passed to --format is invalid: {{.error}}":"Wartość przekazana do --format jest nieprawidłowa: {{.error}}",
"The vmwarefusion driver is deprecated and support for it will be removed in a future release.\n\t\t\tPlease consider switching to the new vmware unified driver, which is intended to replace the vmwarefusion driver.\n\t\t\tSee https://minikube.sigs.k8s.io/docs/reference/drivers/vmware/ for more information.\n\t\t\tTo disable this message, run [minikube config set ShowDriverDeprecationNotification false]":"",
"These --extra-config parameters are invalid: {{.invalid_extra_opts}}":"",
"These changes will take effect upon a minikube delete and then a minikube start":"",
"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 control plane is not running! (state={{.state}})":"",
"This driver does not yet work on your architecture. Maybe try --driver=none":"",
"This is unusual - you may want to investigate using \"{{.command}}\"":"",
"This will keep the existing kubectl context and will create a minikube context.":"",
"This will start the mount daemon and automatically mount files into minikube.":"",
"This {{.type}} is having trouble accessing https://{{.repository}}":"",
"Tip: To remove this root owned cluster, run: sudo {{.cmd}}":"",
"To connect to this cluster, use: kubectl --context={{.profile_name}}":"Aby połaczyć się z klastrem użyj: kubectl --context={{.profile_name}}",
"To disable this notice, run: 'minikube config set WantUpdateNotification false'":"Aby wyłączyć tę notyfikację, użyj: 'minikube config set WantUpdateNotification false'",
"To disable this notice, run: 'minikube config set WantUpdateNotification false'\\n":"",
"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.":"",
"Use \"{{.CommandPath}} [command] --help\" for more information about a command.":"",
"Use 'kubect get po -A' to find the correct and namespace name":"",
"Use -A to specify all namespaces":"",
"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'.":"",
"Verify that your HTTP_PROXY and HTTPS_PROXY environment variables are set correctly.":"Zweryfikuj czy zmienne HTTP_PROXY i HTTPS_PROXY są ustawione poprawnie",
"Verify the IP address of the running cluster in kubeconfig.":"Weryfikacja adresu IP działającego klastra w kubeconfig",
"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}}":"",
"Waiting for SSH access ...":"Oczekiwanie na połaczenie SSH...",
"Your host does not support KVM virtualization. Ensure that qemu-kvm is installed, and run 'virt-host-validate' to debug the problem":"Twoje środowisko nie wspiera wirtualizacji KVM. Upewnij się, że qemu-kvm jest zainstalowane i uruchom 'virt-host-validate' aby rozwiązać 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":"",
"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}}":"konfiguracja minikube i kubectl będzie przechowywana w katalogu {{.home_dir}}",
"kubectl not found in PATH, but is required for the dashboard. Installation guide: https://kubernetes.io/docs/tasks/tools/install-kubectl/":"kubectl nie zostało odnalezione w zmiennej środowiskowej ${PATH}. Instrukcja instalacji: https://kubernetes.io/docs/tasks/tools/install-kubectl/",
"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":"",
"service {{.namespace_name}}/{{.service_name}} has no node port":"",
"stat failed":"",
"status json failure":"",
"status text failure":"",
"toom any arguments ({{.ArgCount}}).\\nusage: minikube config set PROPERTY_NAME PROPERTY_VALUE":"",
"tunnel creates a route to services deployed with type LoadBalancer and sets their Ingress to their ClusterIP. for a detailed example see https://minikube.sigs.k8s.io/docs/tasks/loadbalancer":"",
"unable to bind flags":"",
"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":"",
