Skip to content
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

Conversation

italofernandes13
Copy link
Contributor

Translate docs to pt-br

docs/reference/node/kubelet-checkpoint-api.md

Related issues
#13939

@k8s-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign edsoncelio for approval by writing /assign @edsoncelio in a comment. For more information see the Kubernetes Code Review Process.

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 /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@k8s-ci-robot k8s-ci-robot added the language/pt Issues or PRs related to Portuguese language label Jan 30, 2023
@k8s-ci-robot k8s-ci-robot added sig/docs Categorizes an issue or PR as relevant to SIG Docs. cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. size/M Denotes a PR that changes 30-99 lines, ignoring generated files. labels Jan 30, 2023
@netlify
Copy link

netlify bot commented Jan 30, 2023

Pull request preview available for checking

Built without sensitive environment variables

Name Link
🔨 Latest commit 0012701
🔍 Latest deploy log https://app.netlify.com/sites/kubernetes-io-main-staging/deploys/63d83c5da346990008304a90
😎 Deploy Preview https://deploy-preview-39173--kubernetes-io-main-staging.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify site settings.

@stormqueen1990
Copy link
Member

/label tide/merge-method-squash

@k8s-ci-robot k8s-ci-robot added the tide/merge-method-squash Denotes a PR that should be squashed by tide when it merges. label Feb 2, 2023
Copy link
Member

@stormqueen1990 stormqueen1990 left a 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!

Comment on lines +2 to +3
content_type: "referência"
título: API de Checkpoint do Kubelet
Copy link
Member

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.
Copy link
Member

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.
Copy link
Member

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
Copy link
Member

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
Copy link
Member

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
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Typo in "requirido".

Comment on lines +49 to +57
- **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
Copy link
Member

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
Copy link
Member

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)
Copy link
Member

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 on lines +79 to +84
{{< 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 >}}
Copy link
Member

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.

@k8s-triage-robot
Copy link

The Kubernetes project currently lacks enough contributors to adequately respond to all PRs.

This bot triages PRs according to the following rules:

  • After 90d of inactivity, lifecycle/stale is applied
  • After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
  • After 30d of inactivity since lifecycle/rotten was applied, the PR is closed

You can:

  • Mark this PR as fresh with /remove-lifecycle stale
  • Close this PR with /close
  • Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label May 3, 2023
@stormqueen1990
Copy link
Member

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 #kubernetes-docs-pt channel in Kubernetes Slack.


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 #kubernetes-docs-pt no Slack do Kubernetes.

/close

@k8s-ci-robot
Copy link
Contributor

@stormqueen1990: Closed this PR.

In response to this:

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 #kubernetes-docs-pt channel in Kubernetes Slack.


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 #kubernetes-docs-pt no Slack do Kubernetes.

/close

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. language/pt Issues or PRs related to Portuguese language lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. sig/docs Categorizes an issue or PR as relevant to SIG Docs. size/M Denotes a PR that changes 30-99 lines, ignoring generated files. tide/merge-method-squash Denotes a PR that should be squashed by tide when it merges.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants