Change:
This is a Feature Request <!-- Please only use this template for submitting feature/enhancement requests --<!-- See for guidance on writing an actionable issue description. --What would you like to be <!-- Describe as precisely as possible how this feature/enhancement should work from the user perspective. What should be changed, etc. --Update the page Olá, Minikube (Brazilian Portuguese) to reflect the latest content in English. The Portuguese version of this page is a little bit outdated when compared to the English version. Page address: Content path in the repository: Why is this needed To keep the content in Brazilian Portuguese in sync with the English version. Comments <!-- Any additional related comments that might help. Drawings/mockups would be extremely helpful (if required). --/help /good-first-issue
This request has been marked as suitable for new contributors. Please ensure that the issue body includes answers to the following questions: Why are we solving this issue? To address this issue, are there any code changes? If there are code changes, what needs to be done in the code and what places can the assignee treat as reference points? Does this issue have zero to low barrier of entry? How can the assignee reach out to you for help? For more details on the requirements of such an issue, please see and ensure that they are met. If this request no longer meets these requirements, the label can be removed by commenting with the command. <detailsIn response to : This is a Feature Request <!-- See for guidance on writing an actionable issue description. --<!-- Describe as precisely as possible how this feature/enhancement should work from the user perspective. What should be changed, etc. --Update the page Olá, Minikube (Brazilian Portuguese) to reflect the latest content in English. The Portuguese version of this page is a little bit outdated when compared to the English version. To keep the content in Brazilian Portuguese in sync with the English version. <!-- Any additional related comments that might help. Drawings/mockups would be extremely helpful (if required). --/good-first-issue Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details
/triage accepted
/language pt-br Kindly provide the link to the page as well.
The label(s) cannot be applied, because the repository doesn't have them. <detailsIn response to : /language pt-br Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details
/language pt
Hi there, Just the page address and the content path to the issue description.
/assign
I didn't understand this point.
If you are familiar with the localization language used here, I don't think you should have a doubt about understanding it. However, if you don't, we recommend folks only pick up those issues of the language they're comfortable with and use it often.
/assign

Discussion:
{{< kat-button >}} {{< note >}} <del> Se você instalou o Minikube localmente, execute: `minikube start`. </del> <ins> Se você instalou o Minikube localmente, execute: `minikube start`. Antes de executar `minikube dashboard`, abra um novo terminal, execute `minikube dashboard` nele, e retorne para o terminal anterior. </ins> {{< /note >}} 2. Abra o painel do Kubernetes em um navegador:

minikube dashboard ``` <del> 3. Apenas no ambiente do Katacoda: Na parte superior do terminal, clique em **Preview Port 30000**. </del> <ins> 3. Apenas no ambiente do Katacoda: Na parte superior to painel do terminal, clique no sinal de mais (+), e selecione **Select port to view on Host 1**. 4. Apenas no ambiente do Katacoda: Digite `30000`, e clique em **Display Port**. {{< note >}} O comando `dashboard` habilita o complemento (_addon_) de dashboard e abre o proxy no navegador padrão. Voce pode criar recursos no Kubernetes, como Deployment e Service, pela dashboard. Se você está executando em um ambiente como administrador (_root_), veja [Acessando a Dashboard via URL](#acessando-a-dashboard-via-url). Por padrão, a dashboard só é accesível internamente pela rede virtual do Kubernetes. O comando `dashboard` cria um proxy temporário que permite que a dashboard seja acessada externamente à rede virtual do Kubernetes. Para parar o proxy, execute `Ctrl+C` para terminar o processo. A dashboard permanece sendo executada no cluster Kubernetes depois do comando ter sido terminado. Você pode executar o comando `dashboard` novamente para criar outro proxy para accessar a dashboard {{< /note >}} ## Acessando a Dashboard via URL Caso não queira abrir o navegador, execute o comando `dashboard` com a flag `--url` para ver a URL: ```shell minikube dashboard --url ``` </ins> ## Criando um Deployment

5. (**Apenas no ambiente do Katacoda**) Observe o número da porta com 5 dígitos exibido ao lado de `8080` na saída do serviço. Este número de porta é gerado aleatoriamente e pode ser diferente para você. Digite seu número na caixa de texto do número da porta e clique em **Display Port**. Usando o exemplo anterior, você digitaria `30369`. <del> Isso abre uma janela do navegador, acessa o seu aplicativo e mostra o retorno da requisição. </del> <ins> Isso abre uma janela do navegador, acessa o seu aplicativo e mostra o retorno da requisição. </ins> ## Habilitando Complementos (addons)

* Aprender mais sobre [Deployment objects](/docs/concepts/workloads/controllers/deployment/). * Aprender mais sobre [Deploying applications](/docs/tasks/run-application/run-stateless-application-deployment/). * Aprender mais sobre [Service objects](/docs/concepts/services-networking/service/).