-
Notifications
You must be signed in to change notification settings - Fork 14.3k
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
Update hardening Kubernetes clusters URL in website to the latest version 1.2 #44031
Conversation
NSA and CISA released the 1.0 version of the Kubernetes hardening guide in August 2021 and updated it based on industry feedback in March 2022 (version 1.1). The most recent version of the Kubernetes hardening guidance was released in August 2022 with corrections and clarifications.
Welcome @seifrajhi! |
✅ Pull request preview available for checkingBuilt without sensitive environment variables
To edit notification comments on pull requests, go to your Netlify site configuration. |
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.
Thanks for spotting that there's an update available.
The change doesn't make sense: the background to this article only includes things that had happened prior to publication. It will jar with readers if the article appears to have been written taking into account guidance published a year later.
You could reframe the change as an aside to the article text. Please check in with the 3 article authors to make sure they're happy with the proposed change.
The current link in this blog gives 404 error, so it should be changed or removed imo.
I will do that 👍 , it's a better approach.
I will try to contact them, to ask them if they are ok with my changes. |
This blog was actually one of the inputs taken as feedback to v1.0 and then the newer published version of hardening guide added the blog as a reference. Adding a line at the top as a markdown "note" mentioning that and then linking the v1.1 version as part of it would make more sense to avoid circular referencing :) Thank you @seifrajhi for spotting this and opening a PR to fix it. |
Hey @PushkarJ , thank you for the prompt feedback !! That's exactly what I did, I added a note saying that there are newer versions v1.1 and v1.2 and I updated the PDF link to the latest version v1.2 ( v1.0 is not accessible anymore on the current link used in the blog ) |
> The National Security Agency (NSA) and the Cybersecurity and Infrastructure Security Agency (CISA) released | ||
> the 1.0 version of the Kubernetes hardening guide in August 2021 and updated it based on industry feedback in March 2022 (version 1.1). | ||
> The most recent version of the Kubernetes hardening guidance was released in August 2022 with corrections and clarifications. | ||
> Version 1.2 outlines a number of recommendations for (hardening Kubernetes clusters)[https://media.defense.gov/2022/Aug/29/2003066362/-1/-1/0/CTR_KUBERNETES_HARDENING_GUIDANCE_1.2_20220829.PDF]. |
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.
Thanks, but: please don't mark this as a quote (it's not a quote). Try using italics instead; for example:
**Update, November 2023**
_The National Security Agency (NSA) and the Cybersecurity and Infrastructure Security Agency (CISA)_
_released the 1.0 version of the Kubernetes hardening guide in August 2021 and updated it based on_
_industry feedback in March 2022 (version 1.1)._
_The most recent version of the Kubernetes hardening guidance was released in August 2022_
_with corrections and clarifications._
_Version 1.2 outlines a number of recommendations for_
[_hardening Kubernetes clusters_](https://media.defense.gov/2022/Aug/29/2003066362/-1/-1/0/CTR_KUBERNETES_HARDENING_GUIDANCE_1.2_20220829.PDF].
ℹ️ The trailing whitespace is intentional and significant.
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.
Changes are made per suggestion @sftim
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.
Hello, any other changes to be made ?
I am okay with these new changes with a note. Tagging the remaining authors for review |
I am fine with the changes but will defer accepting this PR to sig-docs leads. IIRC, there used to be a policy on not updating blogposts. I am not sure if there are exceptions. Tagging co-chairs and apologies in advance for spamming. |
@seifrajhi The update seems to have been formatted incorrectly in the deploy preview. Could you please advise if this was intentional? If not, please could you fix it at the earliest possible? |
Hey @divya-mohan0209, Yes it was intentional, Tim advised me to use this format and to use the italic font in this comment |
_The National Security Agency (NSA) and the Cybersecurity and Infrastructure Security Agency (CISA)_ | ||
_released the 1.0 version of the Kubernetes hardening guide in August 2021 and updated it based on_ | ||
_industry feedback in March 2022 (version 1.1)._ | ||
_The most recent version of the Kubernetes hardening guidance was released in August 2022_ | ||
_with corrections and clarifications._ | ||
_Version 1.2 outlines a number of recommendations for_ | ||
[_hardening Kubernetes clusters_](https://media.defense.gov/2022/Aug/29/2003066362/-1/-1/0/CTR_KUBERNETES_HARDENING_GUIDANCE_1.2_20220829.PDF). |
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.
Hmm, I didn't expect this to wrap like it has. Please amend so it renders as a paragraph.
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.
ok I change it to paragraph without italic font
Please put back the emphasis - even if that means making it all one line, or something. It's useful to highlight that this is an aside to the main article. |
You could use a pageinfo - does that work? |
Fwiw: The comment was not on the emphasis but the actual rendering of the text that was added. It wasn't wrapped correctly and my question to @seifrajhi was regarding that. I can see how that wasn't clear in my previous statement and I apologize. |
@sftim, I used a waiting for your feedback |
/sig security |
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.
Thanks
/lgtm
/approve
|
||
The National Security Agency (NSA) and the Cybersecurity and Infrastructure Security Agency (CISA) released the 1.0 version of the Kubernetes hardening guide in August 2021 and updated it based on industry feedback in March 2022 (version 1.1). | ||
|
||
The most recent version of the Kubernetes hardening guidance was released in August 2022 with corrections and clarifications. Version 1.2 outlines a number of recommendations for [hardening Kubernetes clusters](https://media.defense.gov/2022/Aug/29/2003066362/-1/-1/0/CTR_KUBERNETES_HARDENING_GUIDANCE_1.2_20220829.PDF). |
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.
Even better, IMO:
The most recent version of the Kubernetes hardening guidance was released in August 2022 with corrections and clarifications. Version 1.2 outlines a number of recommendations for [hardening Kubernetes clusters](https://media.defense.gov/2022/Aug/29/2003066362/-1/-1/0/CTR_KUBERNETES_HARDENING_GUIDANCE_1.2_20220829.PDF). | |
A more recent version of the Kubernetes hardening guidance was released in August 2022 with corrections and clarifications. Version 1.2 outlines a number of recommendations for [hardening Kubernetes clusters](https://media.defense.gov/2022/Aug/29/2003066362/-1/-1/0/CTR_KUBERNETES_HARDENING_GUIDANCE_1.2_20220829.PDF). |
LGTM label has been added. Git tree hash: f76d311b6346c202a74b6a6b5c32bbd9fc21cd6b
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: sftim 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 |
…sion 1.2 (kubernetes#44031) * Update 2021-10-05-nsa-cisa-hardening.md NSA and CISA released the 1.0 version of the Kubernetes hardening guide in August 2021 and updated it based on industry feedback in March 2022 (version 1.1). The most recent version of the Kubernetes hardening guidance was released in August 2022 with corrections and clarifications. * Add the changes as an aside to the article text * Update formatting per suggestion * make changes in font * update formatting * more changes in formatting * more changes in formatting * Update 2021-10-05-nsa-cisa-hardening.md * Update 2021-10-05-nsa-cisa-hardening.md * Update 2021-10-05-nsa-cisa-hardening.md
…sion 1.2 (kubernetes#44031) * Update 2021-10-05-nsa-cisa-hardening.md NSA and CISA released the 1.0 version of the Kubernetes hardening guide in August 2021 and updated it based on industry feedback in March 2022 (version 1.1). The most recent version of the Kubernetes hardening guidance was released in August 2022 with corrections and clarifications. * Add the changes as an aside to the article text * Update formatting per suggestion * make changes in font * update formatting * more changes in formatting * more changes in formatting * Update 2021-10-05-nsa-cisa-hardening.md * Update 2021-10-05-nsa-cisa-hardening.md * Update 2021-10-05-nsa-cisa-hardening.md
…sion 1.2 (kubernetes#44031) * Update 2021-10-05-nsa-cisa-hardening.md NSA and CISA released the 1.0 version of the Kubernetes hardening guide in August 2021 and updated it based on industry feedback in March 2022 (version 1.1). The most recent version of the Kubernetes hardening guidance was released in August 2022 with corrections and clarifications. * Add the changes as an aside to the article text * Update formatting per suggestion * make changes in font * update formatting * more changes in formatting * more changes in formatting * Update 2021-10-05-nsa-cisa-hardening.md * Update 2021-10-05-nsa-cisa-hardening.md * Update 2021-10-05-nsa-cisa-hardening.md
NSA and CISA released the 1.0 version of the Kubernetes hardening guide in August 2021 and updated it based on industry feedback in March 2022 (version 1.1). The most recent version of the Kubernetes hardening guidance was released in August 2022 with corrections and clarifications.