[ja]docs/concepts/security/security-checklist.md #47547

[luna029]

Description

Translated content/en/docs/concepts/security/security-checklist.md into Japanese.
The following Open Issues have been addressed #47547

Issue

#47547

Closes: #

[linux-foundation-easycla]

The committers listed above are authorized under a signed CLA.

• ✅ login: luna029 (b42c936, 7c3818e, 9360a9d, 98db1d0, 2561528, af769d8, 8a53c86, 819bc9e, 148be29, 789ec3c, 932ced3, 5bb5464, f5a99a5, c443e98, 74cd8d4, c689468, c6ba873, c17ffed, 88e9acf)

[k8s-ci-robot]

Welcome @luna029!

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]

[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 okabe-junya for approval. 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:

• content/ja/OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[netlify]

✅ Pull request preview available for checking

Built without sensitive environment variables

Name	Link
🔨 Latest commit	c443e98
🔍 Latest deploy log	https://app.netlify.com/sites/kubernetes-io-main-staging/deploys/675848775f11d600083dae02
😎 Deploy Preview	https://deploy-preview-48744--kubernetes-io-main-staging.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

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

[Okabe-Junya]

First of all, thank you for your contribution to k/website

In Japanese, spaces are not included between words.
Additionally, our project has a style guide, so please ensure that your translation adheres to it, particularly regarding the use of half-width and full-width characters, as well as long vowel marks.

FYI: https://kubernetes.io/ja/docs/contribute/localization/#style-guide

Since Kubernetes documentation is read by many Japanese speakers, l10n is a complex task.
Please make sure to work in the language you are most proficient in.
(If you choose to move forward with this PR, refer to the style guide. If it is too difficult, feel free to close it.)

/hold

[luna029]

@Okabe-Junya
Thank you for your confirmation.
This is our first submission. We apologize for any inaccuracies.
We have made several updates following the guidance below, including the points you mentioned.
We have referred you to other documents committed to the master branch for any unclear points.
We hope you will check them when you have a chance. Thank you in advance.

参考: https://kubernetes.io/ja/docs/contribute/localization/#style-guide

[Okabe-Junya]

@t-inu

こちらレビューいただくことはできますか？
自分の方でも確認してlgtm, approveできたらと思います

[t-inu]

@luna029
I've reviewed until the "認証と認可" section.
Thereafter, please modify the followings first. Then I'll resume the review.

• pod -> Pod
• Remove spaces between words (except between English words)

[luna029]

@t-inu
Thank you for pointing out some things.
My understanding has improved. Please let me correct it again. I plan to address it over the weekend.
I would also like to add the following translation guidelines along with example sentences to the points I have been pointed out.
https://kubernetes.io/ja/docs/contribute/localization/#style-guide
I appreciate your help.

[t-inu]

@luna029

Please let me correct it again. I plan to address it over the weekend.

Are you still working on the corrections for the “ネットワークセキュリティ” section and after?
Please let us know the status.

[luna029]

@t-inu
I apologize for the delay.
I have updated it so I hope you will proceed with your review.

On a separate note, I submitted a pull request that merged your points into the translation style guide so that I wouldn't forget them.
#49016

[t-inu]

Reviewed the “ネットワークセキュリティ” section.

[t-inu]

Suggested change

	- [ ] イングレスおよびエグレスネットワークポリシーは、クラスター内のすべてのワークロードに適用しています。
	- [ ] ingressおよびegressのネットワークポリシーは、クラスター内のすべてのワークロードに適用しています。

I suggest that "ingress" and "egress" not to be translated, since they are not used in katakana in this document.
ネットワークポリシー page is also helpful.

[t-inu]

Suggested change

	- [ ] 適切な場合、Service Meshを使用してクラスター内のすべての通信を暗号化しています。
	- [ ] 適切な場合、サービスメッシュを使用してクラスター内のすべての通信を暗号化しています。

"service mesh" is usually written in katakana.

[t-inu]

Suggested change

	- [ ] LoadBalancerおよびExternalIPsの使用は制限しています。
	- [ ] LoadBalancerおよびExternalIPの使用は制限しています。

As a general rule, please use the singular form for Japanese.

[t-inu]

Suggested change

	各Namespaceですべての出力と入力をブロックし、すべてのPodを選択するデフォルトのネットワークポリシーは、許可リストアプローチを採用してワークロードが失われないようにするのに役立ちます。
	各Namespaceですべてのegressとingressをブロックし、すべてのPodを選択するデフォルトのネットワークポリシーは、許可リストアプローチを採用してワークロードの見落としがないようにするのに役立ちます。

Default network policies blocking everything egress and ingress, in each namespace, selecting all the pods, can be useful to adopt an allow list approach, ensuring that no workloads is missed.

I think this "miss" refers to a security issue that allows communication that should be restricted.

[t-inu]

Suggested change

	選択したプラグインにこの機能がない場合、代替ソリューションとして、Service Meshを使用してその機能を提供することができます。
	選択したプラグインにこの機能がない場合、代替ソリューションとして、サービスメッシュを使用してその機能を提供することができます。

[t-inu]

Suggested change

	コントロールプレーンのetcdデータストアには、アクセスを制限し、インターネット上で公開されないようにするコントロールが必要です。
	コントロールプレーンのetcdデータストアには、アクセスを制限し、インターネット上で公開されないようにする制御が必要です。

Either is fine.

[t-inu]

Suggested change

	その後、Bastionホストを使用してサーバーにアクセスできます。
	その場合、要塞ホストを使用してサーバーにアクセスできます。

From the context, "その場合" would be better.
"bastion host" translates to "要塞ホスト".

[t-inu]

Suggested change

	[kubelet](/ja/docs/reference/command-line-tools-reference/kubelet/)APIアクセスは制限し、公開しないようにする必要があります。
	[kubelet](/ja/docs/reference/command-line-tools-reference/kubelet/)のAPIアクセスは制限し、公開しないようにする必要があります。

[t-inu]

Suggested change

	デフォルトの認証および承認設定は、`--config`フラグで構成ファイルが指定されていない場合は許可されています。
	`--config`フラグで設定ファイルが指定されていない場合、デフォルトの認証および認可設定は過度に許可されています。

Suggestion for more understandable.
And translation for "overly".

[t-inu]

Suggested change

	LoadBalancerおよびExternalIPsの制限付き使用の詳細については[CVE-2020-8554: LoadBalancer または ExternalIPs を使用した中間者攻撃](https://github.com/kubernetes/kubernetes/issues/97076)および[DenyServiceExternalIPs アドミッション コントローラー](/ja/docs/reference/access-authn-authz/admission-controllers/#denyserviceexternalips)を参照してください。
	LoadBalancerおよびExternalIPの制限付き使用の詳細については[CVE-2020-8554: Man in the middle using LoadBalancer or ExternalIPs](https://github.com/kubernetes/kubernetes/issues/97076)および[DenyServiceExternalIPsアドミッションコントローラー](/docs/reference/access-authn-authz/admission-controllers/#denyserviceexternalips)を参照してください。

It is not necessary to translate GitHub issue title.
"Admission Control in Kubernetes" page in Japanese does not exist.
BTW, since "DenyServiceExternalIPs" is the admission control plugin name itself, it should remain in the plural form I think.