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
fix link in CHANGELOG-1.12.md #69501
Conversation
/kind cleanup |
/ok-to-test |
/lgtm |
/test pull-kubernetes-e2e-kops-aws |
ping @monopole Could you take a look and approve this? Thank u! |
CHANGELOG-1.12.md
Outdated
@@ -147,7 +147,7 @@ filename | sha512 hash | |||
|
|||
## Known Issues | |||
|
|||
- Feature [#566](https://github.com/kubernetes/kubernetes/issues/566) enabling CoreDNS as the default for kube-up deployments was dropped from the release due to a scalability memory resource consumption issue observed. If a cluster operator is considering using CoreDNS on a cluster greater than 2000 nodes, it may be necessary to give more consideration to CoreDNS pod memory resource limits and experimentally measure that memory usage versus cluster resource availability. | |||
- Feature [#566](https://github.com/kubernetes/features/issues/566) enabling CoreDNS as the default for kube-up deployments was dropped from the release due to a scalability memory resource consumption issue observed. If a cluster operator is considering using CoreDNS on a cluster greater than 2000 nodes, it may be necessary to give more consideration to CoreDNS pod memory resource limits and experimentally measure that memory usage versus cluster resource availability. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
s/enhancements/features
The features repo was renamed as enhancements recently.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Updated. Thanks!
@Pingan2017 Sorry for the delay here! Can you make changes as per the comment? Will try to get it approved after that. |
53f4b14
to
c398046
Compare
/lgtm /assign @liggitt |
is that change needed anywhere else in the repo? if so, let's find/replace all at once |
New changes are detected. LGTM label has been removed. |
d3cf974
to
0776668
Compare
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: Pingan2017 If they are not already assigned, you can assign the PR to them by writing 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:
Approvers can indicate their approval by writing |
/close |
@Pingan2017: Closed this PR. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
@Pingan2017: The following tests failed, say
Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here. |
new pr #71979 |
What this PR does / why we need it:
Which issue(s) this PR fixes (optional, in
fixes #<issue number>(, fixes #<issue_number>, ...)
format, will close the issue(s) when PR gets merged):Fixes #
Special notes for your reviewer:
Release note: