[ja]Update /content/ja/docs/concepts/scheduling-eviction/assign-pod-node.md

[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/scheduling-eviction/assign-pod-node.md file.

Fixes #38756

[ziyi-xie]

/retitle [WIP][ja]Update /content/ja/docs/concepts/scheduling-eviction/assign-pod-node.md

[ziyi-xie]

/assign @nasa9084
/cc @atoato88 @t-inu
Hi! I've updated Japanese translation for the /content/ja/docs/concepts/scheduling-eviction/assign-pod-node.md file line 1 to line 157 (That would be line 1 to line 112 in the Japanese version), would you mind checking if everything looks alright at your convenience time please? Here is the original English text and thank you so much!

[netlify]

✅ Pull request preview available for checking

Built without sensitive environment variables

Name	Link
🔨 Latest commit	7ea13b6
🔍 Latest deploy log	https://app.netlify.com/sites/kubernetes-io-main-staging/deploys/640e6113525f5e00085a6d26
😎 Deploy Preview	https://deploy-preview-38800--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.

[ziyi-xie]

/remove-language en

[t-inu]

I'm still in the middle of my review, but I left comments.

[atoato88]

The target page on preview site for this PR:

• https://deploy-preview-38800--kubernetes-io-main-staging.netlify.app/ja/docs/concepts/scheduling-eviction/assign-pod-node/

[ziyi-xie]

The target page on preview site for this PR:

• https://deploy-preview-38800--kubernetes-io-main-staging.netlify.app/ja/docs/concepts/scheduling-eviction/assign-pod-node/

Thank you so much for the link!

[atoato88]

I reviewed content till the ### Nodeの分離/制限 section.

[t-inu]

@ziyi-xie
The file pod-with-node-affinity.yaml has already been updated in PR #39247.
You no longer need to update this file.

[ziyi-xie]

I've updated Japanese translation for the /content/ja/docs/concepts/scheduling-eviction/assign-pod-node.md file line 158 to line 329 (That would be line 113 to line 221 in the Japanese version), would you mind checking if everything looks alright at your convenience time please? Here is the original English text and thank you so much!

[ziyi-xie]

@ziyi-xie The file pod-with-node-affinity.yaml has already been updated in PR #39247. You no longer need to update this file.

Thank you so much for the information! I'll modify it as soon as possible.

[ziyi-xie]

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

[ziyi-xie]

It's about heading IDs. The original heading ID used in here is deleted, so it won't jump to the right place in the original English text. I changed the ID here in Japanese page, and I'm wondering if it's necessary or not.

I think we can do followings:

• Merge this PR use #scheduled-by-default-scheduler similar with original content.

• Create a issue about "dead heading ID in en content", and update that by other PRs.

  • I think en content is basically truth even if that have some errors. that's why I wrote this step.

• We can feedback that to ja content by other PR.

It will take some time, but it will keep the valid of content.

Thank you so much for the kind instructions!
I've changed the ID in Japanese page back to #scheduled-by-default-scheduler and will create an issue with en label to check whether it's appropriate or not.

[ziyi-xie]

It's about heading IDs. The original heading ID used in here is deleted, so it won't jump to the right place in the original English text. I changed the ID here in Japanese page, and I'm wondering if it's necessary or not.

I think we can do followings:

• Merge this PR use #scheduled-by-default-scheduler similar with original content.

• Create a issue about "dead heading ID in en content", and update that by other PRs.

  • I think en content is basically truth even if that have some errors. that's why I wrote this step.

• We can feedback that to ja content by other PR.

It will take some time, but it will keep the valid of content.

Thank you so much for the kind instructions! I've changed the ID in Japanese page back to #scheduled-by-default-scheduler and will create an issue with en label to check whether it's appropriate or not.

FYI: #39864

[atoato88]

/lgtm

And the topic about "#scheduled-by-default-scheduler" related to: #39484

[k8s-ci-robot]

LGTM label has been added.

Git tree hash: b5167214f6e4ae3b844833d6f9ef5c598cc779e1

[atoato88]

/assign @nasa9084
Could you review this?

[ziyi-xie]

/lgtm

And the topic about "#scheduled-by-default-scheduler" related to: #39484

Sorry I just noticed the assign-pods-nodes.md file in #39484 may not be the same file as mine.
@atoato88 @nasa9084 I'm planning to add all the heading IDs in this file ASAP, sorry for the inconvenience and could you review afterwards?

[ziyi-xie]

/hold

[ziyi-xie]

/lgtm
And the topic about "#scheduled-by-default-scheduler" related to: #39484

Sorry I just noticed the assign-pods-nodes.md file in #39484 may not be the same file as mine. @atoato88 @nasa9084 I'm planning to add all the heading IDs in this file ASAP, sorry for the inconvenience and could you review afterwards?

I just added all the heading IDs and could you review at your spare time please? Thanks in advance!
6e33512

[ziyi-xie]

/unhold

[atoato88]

/lgtm

[k8s-ci-robot]

LGTM label has been added.

Git tree hash: 525eb269b313f54f4c3a40098990e983cf680193

[nasa9084]

/approve

[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