[zh-cn] Sync and add anchors for tasks/access-application-cluster/*

[fenggw-fnst]

No description provided.

[netlify]

✅ Pull request preview available for checking

Built without sensitive environment variables

Name	Link
🔨 Latest commit	10681a6
🔍 Latest deploy log	https://app.netlify.com/sites/kubernetes-io-main-staging/deploys/642fe7f330839f0008708453
😎 Deploy Preview	https://deploy-preview-40534--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.

[windsonsea]

These 5 fives are in sync when you run ./scripts/lsync.sh to check differences from en source.

You need to confirm the synchronization conditions with en version one by one, line by line, before merging.

[fenggw-fnst]

Thanks for reply.
I have checked these files with ./scripts/lsync.sh, and it shows that list-all-running-container-images.md needs to be updated, but actually it is in sync at present. Other files under tasks/access-application-cluster/ are all in sync.

This PR aims to:

1. Resync (refresh) the lsync.sh result for list-all-running-container-images.md.
2. Add anchors for the files that lack them.

You need to confirm the synchronization conditions with en version one by one, line by line, before merging.

Understood, for manually checking the sync status, I'd like to open another PR to fix them if I do find something out of sync, since manual proofreading may take a lot of time.

[windsonsea]

The reason of in sync from ./scripts/lsync.sh is some contributors only changed part of out-of-sync content, so it's not encouraged to merge partial change in general. This behavior will invalidate the command ./scripts/lsync.sh.

[fenggw-fnst]

The reason of in sync from ./scripts/lsync.sh is some contributors only changed part of out-of-sync content, so it's not encouraged to merge partial change in general. This behavior will invalidate the command ./scripts/lsync.sh.

Thanks for explaining, indeed, that's why every time I update a single page, I take a quick look at the entire text to see if there's anything out of sync elsewhere.

But in my understanding, ./scripts/lsync.sh tells us whether the page needs to be synced or not, if a page is in sync, then it is safe to do some specific fixes. If it's not in sync, then we have to sync it first, and then do the fix.

If we have to manually proofread the entire page when we want to modify some specific problems on the basis that the page is still showd in sync, then ./scripts/lsync.sh loses its value.

For this PR, my main purpose is to fix them for the anchor aspect and this will make our zh-cn pages better. I'm not saying I won't check them out manually, I just mean that it doesn't break the sync status.

[tengqm]

/approve
/lgtm
/hold

Feel free to lift the hold if the pages are confirmed to be in sync.

[k8s-ci-robot]

LGTM label has been added.

Git tree hash: f3b912b1f8ca919c176bf0bfeb243471c11d6018

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: tengqm

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/zh-cn/OWNERS [tengqm]

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

[fenggw-fnst]

Updated, now they are all confirmed to be in sync, PTAL, thanks.
/unhold

[windsonsea]

/lgtm

[k8s-ci-robot]

LGTM label has been added.

Git tree hash: f8f4fd4b981b732874afed15fa03495962355b6d