-
Notifications
You must be signed in to change notification settings - Fork 14.7k
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
Translate docs/tasks/configmap-secret/managing-secret-using-config-file/ into Japanese #27065
Conversation
…le/ into Japanese
Deploy preview for kubernetes-io-master-staging ready! Built with commit 04c41cb https://deploy-preview-27065--kubernetes-io-master-staging.netlify.app |
/assign @nasa9084 |
|
||
## 設定ファイルを作成する | ||
|
||
先にJSONやYAML形式のファイルでSecretを作成してから、そのオブジェクトを作成することができます。 |
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 about
あらかじめJSONやYAML形式のファイルを作成することで、Secretを作成することができます。
?
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.
@YuikoTakada I think することで implies a way to do something.「あらかじめJSONやYAML形式のファイルを作成」only says that you can create a YAML/JSON file, which does not mean you can create an actual object, so I would leave it as 「してから」 rather than using 「することで」, because 作成することで~できます sounds like you can create the object just by creating the YAML/JSON file which is not true.
What about something like this
あらかじめYAMLまたはJSON形式でSecretのマニフェストを作成したうえで、オブジェクトを作成することができます。
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.
@inductor thank you for your comments.
あらかじめYAMLまたはJSON形式でSecretのマニフェストを作成したうえで、オブジェクトを作成することができます。
It sounds good, thanks.
|
||
{{< note >}} | ||
SecretデータのシリアライズされたJSONおよびYAMLの値は、base64文字列としてエンコードされます。 | ||
これらの文字列の中では、改行は有効ではなく、省略する必要があります。 |
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.
in https://kubernetes.io/ja/docs/concepts/configuration/secret/ , written as:
シリアライズされたJSONやYAMLの機密データはBase64エンコードされています。
文字列の中の改行は不正で、含まれていてはなりません。
I myself prefer Secretデータ
rather than 機密データ
so I love your translation, but I think 不正な
is better than 有効でなく
. so I suggest:
SecretデータのシリアライズされたJSONおよびYAMLの値は、base64文字列としてエンコードされます。
文字列の中の改行は不正で、含まれていてはなりません。
How do you thinnk?
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.
nit: I'd write 文字列中
instead because の~の sounds a bit lengthy
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.
@inductor thank you for your comments.
you mean, you prefer 文字列中の改行は不正で、
instead of 文字列の中の改行は不正で、
, right?
it sounds good :)
Thank you for your PR. I wrote one more comments, so please check it. |
Thanks for your review. I applied suggestion. |
/approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: nasa9084 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 |
/lgtm |
LGTM label has been added. Git tree hash: 1b6f485e99aef679d9240a652bac9fc09c17ed52
|
closes #27064