-
Notifications
You must be signed in to change notification settings - Fork 14.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
Add Blog Post for KEP-3202 beta (CVE feed) #39644
Conversation
edbc922
to
cb82f27
Compare
✅ Pull request preview available for checkingBuilt without sensitive environment variables
To edit notification comments on pull requests, go to your Netlify site settings. |
✅ Pull request preview available for checkingBuilt without sensitive environment variables
To edit notification comments on pull requests, go to your Netlify site settings. |
cb82f27
to
f9f5423
Compare
f9f5423
to
19a371d
Compare
Thank you so much for getting on this and creating a wonderful draft @cailynse :) /sig security |
Thanks a lot for the draft and placeholder work! Now, most of the changes are merged, let's write the blog :) |
content/en/blog/_posts/2023-03-08-Updates-to-the-Auto-refreshing-Official-CVE-Feed/index.md
Outdated
Show resolved
Hide resolved
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.
Some suggestions for completeness
content/en/blog/_posts/2023-03-08-Updates-to-the-Auto-refreshing-Official-CVE-Feed/index.md
Outdated
Show resolved
Hide resolved
content/en/blog/_posts/2023-03-08-Updates-to-the-Auto-refreshing-Official-CVE-Feed/index.md
Outdated
Show resolved
Hide resolved
content/en/blog/_posts/2023-03-08-Updates-to-the-Auto-refreshing-Official-CVE-Feed/index.md
Outdated
Show resolved
Hide resolved
19a371d
to
27d5098
Compare
Hey cailyne, I cannot push to this PR (of course), so could you do a rebase of this branch on main? This branch is pre-cve feed fix and other fixes which prevent it to build locally. I can fix my local copy of your branch but not the remote. If you use gh repo sync caylinse/website
git checkout main && git fetch && git pull origin main
git checkout KEP-3202-blog && git rebase main
git push origin KEP-3202-blog --force-with-lease |
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 a lot for doing this, he are my suggestions for organization and the content that you can hopefully directly apply from GitHub as a batch!
content/en/blog/_posts/2023-03-08-Updates-to-the-Auto-refreshing-Official-CVE-Feed/index.md
Outdated
Show resolved
Hide resolved
content/en/blog/_posts/2023-03-08-Updates-to-the-Auto-refreshing-Official-CVE-Feed/index.md
Outdated
Show resolved
Hide resolved
--- | ||
layout: blog | ||
title: Updates to the Auto-refreshing Official CVE Feed | ||
date: 2023-02-08 |
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.
Reminder that we will have to update this on publication.
content/en/blog/_posts/2023-03-08-Updates-to-the-Auto-refreshing-Official-CVE-Feed/index.md
Outdated
Show resolved
Hide resolved
content/en/blog/_posts/2023-03-08-Updates-to-the-Auto-refreshing-Official-CVE-Feed/index.md
Outdated
Show resolved
Hide resolved
content/en/blog/_posts/2023-03-08-Updates-to-the-Auto-refreshing-Official-CVE-Feed/index.md
Outdated
Show resolved
Hide resolved
content/en/blog/_posts/2023-03-08-Updates-to-the-Auto-refreshing-Official-CVE-Feed/index.md
Outdated
Show resolved
Hide resolved
content/en/blog/_posts/2023-03-08-Updates-to-the-Auto-refreshing-Official-CVE-Feed/index.md
Outdated
Show resolved
Hide resolved
content/en/blog/_posts/2023-03-08-Updates-to-the-Auto-refreshing-Official-CVE-Feed/index.md
Outdated
Show resolved
Hide resolved
If you prefer applying a git patch instead of clicking all these buttons you can |
27d5098
to
17a113d
Compare
@cailynse please tag me when you are able to make updates to dates as suggested by @harshitasao on the file name and metadata. Happy to |
@PushkarJ - should the date be set to the deadline, April 4th? Or before? |
45f058d
to
a84410b
Compare
Oops @cailynse you maybe right and I guess I misunderstood. @harshitasao can you clarify which of the following is true: do we want the blog to be "ready to merge" with OR Do we want just a PR open without need for any approvals or reviews by April 4? (Which is already what the blog's current state is) OR Is the publication date for this blog set to April 4? |
Hey @PushkarJ Sorry for the delayed response. We want just a PR open with a complete blog drafted by April 4th, which is the hard deadline, to better plan the release dates and avoid missing out. The feature blogs publication will start after the release (i.e., after April 11th). We're finalizing the publishing schedules, and I'll let you know the publication date. |
Hello @harshitasao - this PR is the complete blog - do we need to change anything? |
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.
A copy edit pass with some spelling corrections in line.
content/en/blog/_posts/2023-04-04-Updates-to-the-Auto-refreshing-Official-CVE-Feed/index.md
Outdated
Show resolved
Hide resolved
content/en/blog/_posts/2023-04-04-Updates-to-the-Auto-refreshing-Official-CVE-Feed/index.md
Outdated
Show resolved
Hide resolved
content/en/blog/_posts/2023-04-04-Updates-to-the-Auto-refreshing-Official-CVE-Feed/index.md
Outdated
Show resolved
Hide resolved
…ng-Official-CVE-Feed/index.md Co-authored-by: Nate W. <[email protected]>
…ng-Official-CVE-Feed/index.md Co-authored-by: Nate W. <[email protected]>
164c183
to
8f8bdf3
Compare
Hello, Comms Lead for v1.27 here. The publication order and date for the Feature Blog series has been finalized and the tracking board is updated. The publication date for this article is 25-04-2023 (April 25). Thank you! |
--- | ||
layout: blog | ||
title: Updates to the Auto-refreshing Official CVE Feed | ||
date: |
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.
date: | |
date: 2023-04-25 |
Please also change the file path to match the new date.
…ng-Official-CVE-Feed/index.md Co-authored-by: Nate W. <[email protected]>
8f8bdf3
to
9411b28
Compare
/lgtm |
LGTM label has been added. Git tree hash: 73e641ac5c5ad203b70a5b0b89735ce419bbbb09
|
/assign @kubernetes/sig-docs-blog-owners |
/assign kubernetes/sig-docs-en-reviews |
/assign @sftim |
/approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: tengqm 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 |
/hold cancel |
This is a PR for the blog post explaining the updates to the Auto-refreshing Official CVE feed.