-
Notifications
You must be signed in to change notification settings - Fork 38.7k
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
format error in CHANGELOG-1.14.md #75543
Conversation
Hi @qingsenLi. Thanks for your PR. I'm waiting for a kubernetes member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. 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. |
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.
/lgtm
/ok-to-test
/priority important-soon
@qingsenLi please send a cherry pick of this PR to that branch. here is info how: thanks. |
CHANGELOG-1.14.md
Outdated
@@ -272,7 +272,7 @@ filename | sha512 hash | |||
* While this is a backwards-incompatible change, it would have been impossible to setup reliable monitoring around these metrics since the labels were not stable. | |||
* Add a configuration field to shorten the timeout of validating/mutating admission webhook call. The timeout value must be between 1 and 30 seconds. Default to 30 seconds when unspecified. ([#74562](https://github.com/kubernetes/kubernetes/pull/74562), [@roycaihw](https://github.com/roycaihw)) | |||
* client-go: PortForwarder.GetPorts() now contain correct local port if no local port was initially specified when setting up the port forwarder ([#73676](https://github.com/kubernetes/kubernetes/pull/73676), [@martin-helmich](https://github.com/martin-helmich)) | |||
* # Apply resources from a directory containing kustomization.yaml ([#74140](https://github.com/kubernetes/kubernetes/pull/74140), [@Liujingfang1](https://github.com/Liujingfang1)) | |||
* Apply resources from a directory containing kustomization.yaml ([#74140](https://github.com/kubernetes/kubernetes/pull/74140), [@Liujingfang1](https://github.com/Liujingfang1)) | |||
* kubectl apply -k dir | |||
* # Delete resources from a directory containing kustomization.yaml. |
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.
/hold
the whole block needs to be formatted better:
# Apply resources from a directory containing kustomization.yaml
kubectl apply -k dir
# Delete resources from a directory containing kustomization.yaml.
kubectl delete -k dir
# List resources from a directory containing kustomization.yaml
kubectl get -k dir
i.e. not using bullets *
(see the markdown preview).
/cc @neolit123 @tpepper |
CHANGELOG-1.14.md
Outdated
* # List resources from a directory containing kustomization.yaml | ||
* kubectl get -k dir | ||
* The examples in kubectl apply/get/delete are updated to support -k. ([#74140](https://github.com/kubernetes/kubernetes/pull/74140), [@Liujingfang1](https://github.com/Liujingfang1)) | ||
* `kubectl apply -k dir` # Apply resources from a directory containing kustomization.yaml. |
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.
IMO the "title" / one-line sentence is the only that should show up in these change log entries. I've edited the release notes block for #74140 accordingly
/cc @jeefy @dstrebel @onyiny-ang |
/hold |
/retest |
/cc @jeefy @dstrebel @onyiny-ang |
/hold cancel |
/assign @smarterclayton @liggitt |
/approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: liggitt, qingsenLi 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 |
/retest Review the full test history for this PR. Silence the bot with an |
1 similar comment
/retest Review the full test history for this PR. Silence the bot with an |
What type of PR is this?
/kind cleanup
/sig release
What this PR does / why we need it:
Which issue(s) this PR fixes:
Fixes #
Special notes for your reviewer:
Does this PR introduce a user-facing change?: