zh: adds karmadactl flags for proper display

[zhzhuang-zju]

What type of PR is this?
/kind documentation

What this PR does / why we need it:
Refer to #763 (comment)

Which issue(s) this PR fixes:
Fixes #

Special notes for your reviewer:

[zhzhuang-zju]

karmadactl introduced the operation-scope flag starting from version 1.11.0, and the corresponding documentation needs to be updated.

cc @LavredisG @RainbowMango

[samzong]

/lgtm

[RainbowMango]

/lgtm
/approve

[zhzhuang-zju]

/retest

[zhzhuang-zju]

FATAL ERROR: Ineffective mark-compacts near heap limit Allocation failed - JavaScript heap out of memory

https://app.netlify.com/sites/karmada/deploys/675fce07d8baa700087e6d73#L164

[zhzhuang-zju]

CI [Header rules] almost always fails in these two days, with the following logs:

9:43:38 AM: FATAL ERROR: Ineffective mark-compacts near heap limit Allocation failed - JavaScript heap out of memory

Found a related solution in netlify's FAQ to increase NodeJS memory by adding NODE_OPTIONS = “--max_old_space_size=4096” to netlify's build environment. And it works!

[zhzhuang-zju]

Reducing the number of maintained documents seems to solve this issue too. Could we limit ourselves to keeping only a fixed number of document versions? For example, the last three minor releases.

[RainbowMango]

I understand the root cause of this issue is that the website is getting bigger and bigger, which requires more memory to build.

The solution mentioned above (#764 (comment)) is essentially a workaround, if we do not clean the EOL docs, we are likely to face this issue again shortly.

So, I tend to cleanup the EOL docs. But we need a way to back up before removing them.

[RainbowMango]

I just created https://github.com/karmada-io/website/tree/release-1.12 branch which can be used as a backup, but we need to explore if we need further configuration on Netlify.

[zhzhuang-zju]

I just created https://github.com/karmada-io/website/tree/release-1.12 branch which can be used as a backup, but we need to explore if we need further configuration on Netlify.

I can start by understanding what configurations are available for Netlify

[zhzhuang-zju]

By removing the index of EOL docs from versions.json, the building phase of the website will miss these documents. From the CI result, we can also achieve the goal of reducing the memory required for the website-building phase

[RainbowMango]

By removing the index of EOL docs from versions.json, the building phase of the website will miss these documents. From the CI result, we can also achieve the goal of reducing the memory required for the website-building phase

I prefer to remove them from the code base.

Reducing the number of maintained documents seems to solve this issue too. Could we limit ourselves to keeping only a fixed number of document versions? For example, the last three minor releases.

How about keeping the latest 6 releases?

[karmada-bot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: RainbowMango

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:

• i18n/OWNERS [RainbowMango]
• versioned_docs/version-v1.11/OWNERS [RainbowMango]
• versioned_docs/version-v1.12/OWNERS [RainbowMango]

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

[zhzhuang-zju]

The good news is that no changes are required to pass the CI; the bad news is that this makes me unsure about the actual reason for the previous failure. 😕

[RainbowMango]

/lgtm

So, no evidence that this error is due to too many docs. :)

We can start to handle it when we face it next time.