-
Notifications
You must be signed in to change notification settings - Fork 14.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[pt-br] Add docs/reference/node/kubelet-checkpoint-api.md #39173
[pt-br] Add docs/reference/node/kubelet-checkpoint-api.md #39173
Conversation
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
✅ Pull request preview available for checkingBuilt without sensitive environment variables
To edit notification comments on pull requests, go to your Netlify site settings. |
/label tide/merge-method-squash |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hello there, @italofernandes13! 👋
Thank you very much for your contribution! 🎉
This page needs some adjustments, especially on the translations for checkpoint. I left comments on the things I think need to be adjusted; if you disagree with anything or feels there's a better way forward, feel free to suggest it. I'm available on the #kubernetes-docs-pt
channel of Kubernetes Slack if you want to talk or need help. 😃
Once these bits have been addressed, feel free to request me for a new review by writing /cc @stormqueen1990
on a comment in this PR.
Thanks again!
content_type: "referência" | ||
título: API de Checkpoint do Kubelet |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
"reference" and "title" are front matter defined data and should not be translated.
|
||
{{< feature-state for_k8s_version="v1.25" state="alpha" >}} | ||
|
||
Verificar um contêiner é a funcionalidade de criar uma cópia com estado de um contêiner em execução. Uma vez que você tem uma cópia com estado de um contêiner, você pode movê-lo para um computador diferente para depuração ou fins semelhantes. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
"Verificar" completely changes the meaning of "checkpoint". I see that "ponto de verificação" is used in Portuguese, so perhaps rewording this sentence to use "A criação de um ponto de verificação" instead might be a good idea.
|
||
Verificar um contêiner é a funcionalidade de criar uma cópia com estado de um contêiner em execução. Uma vez que você tem uma cópia com estado de um contêiner, você pode movê-lo para um computador diferente para depuração ou fins semelhantes. | ||
|
||
Se você mover os dados do contêiner verificado para um computador que seja capaz de restaurá-lo, esse contêiner restaurado continua a ser executado exatamente no mesmo ponto em que foi verificado. Você também pode inspecionar os dados salvos, desde que tenha ferramentas adequadas para isso. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Same consideration here.
|
||
Se você mover os dados do contêiner verificado para um computador que seja capaz de restaurá-lo, esse contêiner restaurado continua a ser executado exatamente no mesmo ponto em que foi verificado. Você também pode inspecionar os dados salvos, desde que tenha ferramentas adequadas para isso. | ||
|
||
Criando um ponto de verificação de um contêiner pode ter implicações de segurança. Normalmente |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
"Criando um ..." sounds very strange. Perhaps "A criação de um ..." would fit better?
|
||
Criando um ponto de verificação de um contêiner pode ter implicações de segurança. Normalmente | ||
um ponto de verificação contém todas as páginas de memória de todos os processos no contêiner | ||
verificado. Isso significa que tudo o que costumava estar na memória agora está disponível |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Some bits here:
- Suggestion: "estava em memória" instead of "costumava estar na memória".
- Same consideration about "verificado".
|
||
{{< glossary_tooltip term_id="namespace" >}} | ||
|
||
- **pod** (*in path*): string, requirido |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Typo in "requirido".
- **namespace** (*in path*): string, requerido | ||
|
||
{{< glossary_tooltip term_id="namespace" >}} | ||
|
||
- **pod** (*in path*): string, requirido | ||
|
||
{{< glossary_tooltip term_id="pod" >}} | ||
|
||
- **container** (*in path*): string, requerido |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
How do you feel about using "parâmetro da URL" instead of "in path" in those parameters?
|
||
{{< glossary_tooltip term_id="container" >}} | ||
|
||
- **timeout** (*in query*): integer |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
How do you feel about using "parâmetro da query" here instead of "in query"?
|
||
401: Unauthorized | ||
|
||
404: Not Found (se o `ContainerCheckpoint` feature gate estiver desativado) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'd stylize "feature gate" as italic and move it to before ContainerCheckpoint
("se o feature gate ContainerCheckpoint
...").
{{< comment >}} | ||
TODO: Add more information about return codes once CRI implementation have checkpoint/restore. | ||
This TODO cannot be fixed before the release, because the CRI implementation need | ||
the Kubernetes changes to be merged to implement the new ContainerCheckpoint CRI API | ||
call. We need to wait after the 1.25 release to fix this. | ||
{{< /comment >}} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think we could remove this from the localized version.
The Kubernetes project currently lacks enough contributors to adequately respond to all PRs. This bot triages PRs according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale |
Hello there, @italofernandes13! 👋 Thank you very much for your work on this PR. However, it has been open and reviewed for a while with no action taken. For this reason, I will be closing this PR. If you wish to continue your work on this, please feel free to reopen it. Should you have any questions, please don't hesitate to reach out to the Olá, @italofernandes13! 👋 Obrigada pelo teu trabalho neste PR. Devido a inatividade após a revisão, irei fechá-lo. No entanto, caso desejes continuar teu trabalho, podes reabrir o PR a qualquer momento. Se tiveres dúvidas, não hesita em contatar-nos através do canal /close |
@stormqueen1990: Closed this PR. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
Translate docs to pt-br
docs/reference/node/kubelet-checkpoint-api.md
Related issues
#13939