-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
Visible backticks in OCP 4.13 release notes #64740
Comments
Marking this as a good candidate for Hacktoberfest The PR should be submitted against the enterprise-4.13 branch |
can I take this issue ? |
Hey there @7h3-3mp7y-m4n! 🎉 Absolutely!
|
Any new issues @ShaunaDiaz to contribute in ? |
@ayan-joshi My colleague still has three unassigned issues if you'd like to take a look: |
Hi @7h3-3mp7y-m4n, are you still interested fixing this issue? |
Yes I'm interested in it , I'll soon raise a PR |
Hi @7h3-3mp7y-m4n, are you able to raise a PR for this issue? |
sorry for the delay @ShaunaDiaz but I did it. |
Thank you @7h3-3mp7y-m4n, PR looks good! #67516 |
Which section(s) is the issue in?
https://docs.openshift.com/container-platform/4.13/release_notes/ocp-4-13-release-notes.html#ocp-4-13-bug-fixes
This bullet is just above https://docs.openshift.com/container-platform/4.13/release_notes/ocp-4-13-release-notes.html#ocp-4-13-technology-preview, so it is likely easier to go there and scroll up.
What needs fixing?
Fix the backticks by inserting a space between "Windows" and the first backtick of "DaemonSet."
DaemonSet
pods to block Windows nodes that the WMCO attempted to remove or upgrade. With this update, an WMCO includes additional role-based access control (RBAC) permissions, so that the WMCO can remove DaemonSet workloads. An WMCO can also delete any processes that were created with the containerd shim, so that DaemonSet containers do not exist on a Windows instance after a WMCO removes a node from a cluster. (OCPBUGS-5354)The text was updated successfully, but these errors were encountered: