8000 [ja] Translate kms-provider.md into Japanese by laxman-gupta1006 · Pull Request #51690 · kubernetes/website · GitHub
[go: up one dir, main page]

Skip to content

Conversation

laxman-gupta1006
Copy link
< 8000 span data-view-component="true" class="Label ml-1">Contributor

Description

This PR provides a complete Japanese translation of the KMS provider documentation ([kms-provider.md] to improve accessibility for Japanese-speaking Kubernetes users. The translation maintains technical accuracy while preserving all code examples, YAML configurations, Hugo shortcodes, and markdown structure. All technical terminology is appropriately translated following existing Japanese documentation conventions in the repository.

File added: [kms-provider.md]

This translation is added to the Japanese documentation tree under the administration cluster tasks section, following the same structure as the English documentation.

Issue

Closes: #51634

@k8s-ci-robot k8s-ci-robot added the cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. label Jul 24, 2025
@k8s-ci-robot
Copy link
Contributor

Welcome @laxman-gupta1006!

It looks like this is your first PR to kubernetes/website 🎉. Please refer to our pull request process documentation to help your PR have a smooth ride to approval.

You will be prompted by a bot to use commands during the review process. Do not be afraid to follow the prompts! It is okay to experiment. Here is the bot commands documentation.

You can also check if kubernetes/website has its own contribution guidelines.

You may want to refer to our testing guide if you run into trouble with your tests not passing.

If you are having difficulty getting your pull request seen, please follow the recommended escalation practices. Also, for tips and tricks in the contribution process you may want to read the Kubernetes contributor cheat sheet. We want to make sure your contribution gets all the attention it needs!

Thank you, and welcome to Kubernetes. 😃

@k8s-ci-robot k8s-ci-robot requested review from bells17 and inductor July 24, 2025 06:47
@k8s-ci-robot k8s-ci-robot added area/localization General issues or PRs related to localization language/ja Issues or PRs related to Japanese language sig/docs Categorizes an issue or PR as relevant to SIG Docs. size/L Denotes a PR that changes 100-499 lines, ignoring generated files. labels Jul 24, 2025
Copy link
netlify bot commented Jul 24, 2025

Pull request preview available for checking

Built without sensitive environment variables

Name Link
🔨 Latest commit b615d8f
🔍 Latest deploy log https://app.netlify.com/projects/kubernetes-io-main-staging/deploys/689f6a356f7fc90008203849
😎 Deploy Preview https://deploy-preview-51690--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 project configuration.

@g1eng
Copy link
Contributor
g1eng commented Jul 24, 2025

Thanks for your contribution!

/area localization
/language ja

@laxman-gupta1006 laxman-gupta1006 force-pushed the ja-translate-kms-provider branch from 51c5453 to ade32dd Compare July 24, 2025 12:34
@laxman-gupta1006 laxman-gupta1006 requested a review from g1eng July 24, 2025 12:44
@laxman-gupta1006 laxman-gupta1006 requested a review from lmktfy July 25, 2025 06:57
Copy link
Contributor
@g1eng g1eng left a comment

Choose a reason for hiding this comment

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

@laxman-gupta1006 I reveiwed half of the article.
I really appreciate your context-awared translation but your PR still contains several violations to the translation style guide.

I'll make review for the residual portion after your fixation at this point.

PTAL: https://kubernetes.io/ja/docs/contribute/localization
Also see #51690 (comment) .

Comment on lines 184 to 187
`DecryptRequest`プロシージャーコールは、`EncryptRequest`からの`(ciphertext, key_id, annotations)`と
ログ目的のUIDを提供します。期待される通り、これは`EncryptRequest`呼び出しの逆です。プラグインは
`key_id`が理解できるものであることを検証する必要があります - 以前の時点で自分が暗号化したデータであることを確信していない限り、
データの復号化を試みてはいけません。
Copy link
Contributor
@g1eng g1eng Jul 27, 2025

Choose a reason for hiding this comment

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

Suggested change
8000
`DecryptRequest`プロシージャーコールは`EncryptRequest`からの`(ciphertext, key_id, annotations)`
ログ目的のUIDを提供します。期待される通り、これは`EncryptRequest`呼び出しの逆です。プラグインは
`key_id`が理解できるものであることを検証する必要があります - 以前の時点で自分が暗号化したデータであることを確信していない限り、
データの復号化を試みてはいけません
`DecryptRequest`プロシージャーコールでは`EncryptRequest`から得た`(ciphertext, key_id, annotations)`とログ目的のUIDを提供します。
期待される通り、これは`EncryptRequest`呼び出しの逆です。
プラグインは`key_id`が既知のものかどうかを検証しなければなりません(MUST)。
また、プラグインは自身が以前に暗号化したデータであることを確証できない限り、データの復号を試みてはいけません(MUST NOT)

But I wonder why this sentence says:

(ciphertext, key_id, annotations) from EncryptRequest

because these fields are owned by EncryptResponse and only be given by EncryptResponse.

I think that the first sentence of the original article is incorrect and original document should be fixed.
HDYT about that?

original:

The DecryptRequest procedure call provides the (ciphertext, key_id, annotations) from EncryptRequest and a UID for logging purposes.

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 that the first sentence of the original article is incorrect and original document should be fixed.

Although this data is indeed included in EncryptResponse, I think this sentence is fine as it is.
Because the data is obtained through the processing of EncryptRequest.

@laxman-gupta1006
Copy link
Contributor Author

@g1eng
Copy link
Contributor
g1eng commented Jul 28, 2025

@g1eng I have made the changes you requested in commit ab95c4a. Please review when you have a chance.

@laxman-gupta1006 Thanks!
I'll review the residual part of the PR tommorow.

@g1eng
Copy link
Contributor
g1eng commented Jul 30, 2025

Hi. I've reviewed your PR again. @laxman-gupta1006
There are several (10+) style guide violations in the file, until now (ab95c4a).

Please take a look at the code, especially for the rule of newlines after symbols.
You can detect such violation with a regex pattern such as 。[^$]. Also you can use a builtin regex filter on your editor, grep with -E flag or textlint to achieve the validation on your machine.
Probably as you know, newlines inside a list * at line head followed by text) does not break the page displayed, so also put newlines after in a list item.
You may feel that it is inconvenient to do your works with such checks, but we create and maintain the guideline to ensure the documentation quality and maintainability for future contributors, reviewers or readers.

By the way, I've had lower back injury (herniated disc) and cannot move my body enough for current works.
I'm sorry but the review for the PR should be lower priority for me at now.
If you'd like to proceed tasks for the PR with other reviewers, it is recommended to ensure the fixation I suggest in this message at first.

If you have any questions about the style guide, feel free to ask me or other sig/org members.

/cc @t-inu @nasa9084
(Do you have any time to follow him?)

Copy link
Contributor
@g1eng g1eng left a comment

Choose a reason for hiding this comment

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

Add missing review comments.

@laxman-gupta1006
Copy link
Contributor Author
laxman-gupta1006 commented Jul 30, 2025

Hi @g1eng , Thank you for the feedback!
I’ve gone through the file again and applied the suggested fixes, especially ensuring proper newlines after 。 symbols, including in list items.

The changes have been committed here: 10d0323

Also, I hope you recover soon from your back injury, please don’t worry about prioritizing the review, and I’m fine waiting or proceeding with other reviewers as needed.

@g1eng
Copy link
Contributor
g1eng commented Jul 31, 2025

@laxman-gupta1006 Thanks. I'll provide feedbacks in another day.

Copy link
Member
@t-inu t-inu left a comment

Choose a reason for hiding this comment

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

Please change the notation of these words.

  • レイテンシ -> レイテンシー
    latency (-cy)
  • プロシージャーコール -> プロシージャコール
    procedure (-re) call

ref: 長音の有無

@laxman-gupta1006
Copy link
Contributor Author
laxman-gupta1006 commented Aug 7, 2025

Please change the notation of these words.

  • レイテンシ -> レイテンシー
    latency (-cy)
  • プロシージャーコール -> プロシージャコール
    procedure (-re) call

ref: 長音の有無

Thanks t-inu, I have changed the notations. 01b606e

@Okabe-Junya
Copy link
Member

/cc g1eng
/label tide/merge-method-squash

Big thank you for your review, Can you please take a look again to move this PR with forward

@k8s-ci-robot k8s-ci-robot requested a review from g1eng August 11, 2025 16:50
@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 Aug 11, 2025
@Okabe-Junya
Copy link
Member

@laxman-gupta1006

First of all, thank you for your interest in the Japanese localization project.
Contributor resources are very important, but reviewer resources are equally important.

To reduce minor/nit comments, please follow our style guide - https://kubernetes.io/ja/docs/contribute/localization/#style-guide

Thanks again

Applied suggestions from code review

Co-authored-by: inukai <82919057+t-inu@users.noreply.github.com>
Co-authored-by: youmeim <83828177+g1eng@users.noreply.github.com>
@laxman-gupta1006
Copy link
Contributor Author

@t-inu I have applied all the changes from the review. Thank you for your time. b615d8f

Copy link
Member
@t-inu t-inu left a comment

Choose a reason for hiding this comment

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

Thanks!
/lgtm

@k8s-ci-robot k8s-ci-robot added the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Aug 18, 2025
@k8s-ci-robot
Copy link
Contributor

LGTM label has been added.

Git tree hash: 01d4ee85238017632afde2b23a7b39afe36ce989

@t-inu
Copy link
Member
t-inu commented Aug 18, 2025

Regarding this comment, if the original document needs to be fixed, we will update the Japanese page later.

/assign Okabe-Junya
for approval

Copy link
Member
@Okabe-Junya Okabe-Junya left a comment

Choose a reason for hiding this comment

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

Thanks, LGTM

@k8s-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: Okabe-Junya

The full list of commands accepted by this bot can be found here.

The pull request process is described 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 approved Indicates a PR has been approved by an approver from all required OWNERS files. label Aug 18, 2025
@k8s-ci-robot k8s-ci-robot merged commit 7d5bebd into kubernetes:main Aug 18, 2025
6 checks passed
kamothi pushed a commit to kamothi/website that referenced this pull request Oct 2, 2025
* [ja] Translate kms-provider.md into Japanese

* Remove reviewers field from Japanese translation metadata

* Localize placeholder text and remove legacy hyperlinks in Japanese KMS provider docs

* Fix Japanese localization style guide violations in KMS provider docs

* Refactor KMS provider documentation for clarity and readability

* Improve Japanese language flow and formatting

* Changed notations

* Apply suggestions from code review

Applied suggestions from code review

Co-authored-by: inukai <82919057+t-inu@users.noreply.github.com>
Co-authored-by: youmeim <83828177+g1eng@users.noreply.github.com>

---------

Co-authored-by: inukai <82919057+t-inu@users.noreply.github.com>
Co-authored-by: youmeim <83828177+g1eng@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. area/localization General issues or PRs related to localization cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. language/ja Issues or PRs related to Japanese language lgtm "Looks good to me", indicates that a PR is ready to be merged. sig/docs Categorizes an issue or PR as relevant to SIG Docs. size/L Denotes a PR that changes 100-499 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.

[ja] translate content/en/docs/tasks/administer-cluster/kms-provider.md into Japanese
7 participants
0