Skip to content
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

[BUG] The description of throttlingPercent in the documentation is incorrect #2021

Open
j4ckstraw opened this issue Apr 25, 2024 · 4 comments · May be fixed by koordinator-sh/website#180
Open
Assignees
Labels
documentation Improvements or additions to documentation kind/bug Create a report to help us improve
Milestone

Comments

@j4ckstraw
Copy link
Contributor

What happened:
文档中关于throttlingPercent的描述没有更新,和代码实现不一致。
image

What you expected to happen:

How to reproduce it (as minimally and precisely as possible):

Anything else we need to know?:

Environment:

  • App version:
  • Kubernetes version (use kubectl version):
  • Install details (e.g. helm install args):
  • Node environment (for koordlet/runtime-proxy issue):
    • Containerd/Docker version:
    • OS version:
    • Kernal version:
    • Cgroup driver: cgroupfs/systemd
  • Others:
@j4ckstraw j4ckstraw added the kind/bug Create a report to help us improve label Apr 25, 2024
@saintube
Copy link
Member

Nice catch. The memory.high calculation is upgraded following the K8S 1.27 (see #1455), so the documentation is outdated.

@saintube saintube added the documentation Improvements or additions to documentation label Apr 28, 2024
@zwzhang0107
Copy link
Contributor

it will be great if you can update the website

@ZiMengSheng ZiMengSheng added this to the v1.5 milestone May 7, 2024
@jasonliu747
Copy link
Member

@saintube
Copy link
Member

saintube commented Jun 3, 2024

To be fixed by koordinator-sh/website#180

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation kind/bug Create a report to help us improve
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants