[ja] Updated content/ja/docs/concepts/workloads/pods/_index.md file

[ziyi-xie]

There are several updates in the original English text and therefore this page is outdated.
This PR updated Japanese translation for the content/ja/docs/concepts/workloads/pods/_index.md file.

Fixes #35828

[netlify]

✅ Pull request preview available for checking

Built without sensitive environment variables

Name	Link
🔨 Latest commit	7154a0c
🔍 Latest deploy log	https://app.netlify.com/sites/kubernetes-io-main-staging/deploys/630b2c6b58e4ff00072910b8
😎 Deploy Preview	https://deploy-preview-35848--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 settings.

[t-inu]

The original page has "Pod update and replacement" section between "Pod templates" and "Resource sharing and communication".
It looks like this section should be added to the Japanese page as well.

ref: #25756

[ziyi-xie]

The original page has "Pod update and replacement" section between "Pod templates" and "Resource sharing and communication". It looks like this section should be added to the Japanese page as well.

ref: #25756

Thank you for your kind instruction! I will go check it right away.

[ziyi-xie]

/retitle [WIP][ja] Updated content/ja/docs/concepts/workloads/pods/_index.md file

[ziyi-xie]

/retitle [ja] Updated content/ja/docs/concepts/workloads/pods/_index.md file

[nasa9084]

/assign
/approve
but I'm not sure we should use {{< skew currentVersion >}} in Japanese page (because actually sometimes Japanese pages are not well-maintained... sadly though)

[k8s-ci-robot]

[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:

• content/ja/OWNERS [nasa9084]

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

[ziyi-xie]

/assign /approve but I'm not sure we should use {{< skew currentVersion >}} in Japanese page (because actually sometimes Japanese pages are not well-maintained... sadly though)
@nasa9084 Thank you for your approval!
And regarding {{< skew currentVersion >}}, could I ask that what would happen if I still use this piece of code and didn't maintain these pages in time? I thought it will change automatically when there's new kubernetes version come out. Thank you so much!

[ziyi-xie]

/cc @t-inu @atoato88
Hi! I've updated Japanese translation for the content/ja/docs/concepts/workloads/pods/_index.md file, would you mind checking if everything looks alright at your convenience time please? Here is the original English text and thank you so much!

[nasa9084]

And regarding {{< skew currentVersion >}}, could I ask that what would happen if I still use this piece of code and didn't maintain these pages in time? I thought it will change automatically when there's new kubernetes version come out. Thank you so much!

Yes, as you said, it will change automatically when there's a new kubernetes version, even the document is not updated.
so, my concern is, if .spec.os.name field affects scheduling with a new kubernetes version and this page is not updated, the page will say "the field won't affect scheduling with THE NEW VERSION"....
anyway, I can go as it is for now

[t-inu]

I reviewed and left comments.

[ziyi-xie]

And regarding {{< skew currentVersion >}}, could I ask that what would happen if I still use this piece of code and didn't maintain these pages in time? I thought it will change automatically when there's new kubernetes version come out. Thank you so much!

Yes, as you said, it will change automatically when there's a new kubernetes version, even the document is not updated. so, my concern is, if .spec.os.name field affects scheduling with a new kubernetes version and this page is not updated, the page will say "the field won't affect scheduling with THE NEW VERSION".... anyway, I can go as it is for now

@nasa9084 Thank you so much for your detailed explanation! I'll keep that in mind and check the updates frequently.

[atoato88]

It's LGTM.
Should I add ltgm label or wait for adding lgtm tag by other reviewers?

[atoato88]

BTW, I agree with the topic about {{< skew currentVersion >}} spoken here.
And an original English contents have also {{< skew currentVersion >}}, so it's a same situation both of EN and JP(and maybe also same with other language).

[nasa9084]

And an original English contents have also {{< skew currentVersion >}}, so it's a same situation both of EN and JP(and maybe also same with other language).

I guess this issue can be an issue for other languages but maybe not for English because English contents should be well-maintained than translation...

Should I add ltgm label or wait for adding lgtm tag by other reviewers?

It seems that you are a member of Kubernetes org so you can use /lgtm if you want (https://kubernetes.io/docs/contribute/participate/roles-and-responsibilities/#members) or of course you can just say LGTM and wait for other reviewer.

[t-inu]

/label tide/merge-method-squash

[t-inu]

Looks good!
/lgtm

[k8s-ci-robot]

LGTM label has been added.

Git tree hash: e2caac761528c3df4b24356efa73b7327245b068

[atoato88]

LGTM too 😄