-
Notifications
You must be signed in to change notification settings - Fork 14.6k
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
[KEP-3203] Fetch and Render CVE JSON Feed #35228
[KEP-3203] Fetch and Render CVE JSON Feed #35228
Conversation
b1e8d8e
to
6356d72
Compare
6356d72
to
566edee
Compare
✅ Pull request preview available for checkingBuilt without sensitive environment variables
To edit notification comments on pull requests, go to your Netlify site settings. |
566edee
to
c8d8ba1
Compare
✅ Pull request preview available for checkingBuilt without sensitive environment variables
To edit notification comments on pull requests, go to your Netlify site settings. |
ea22fca
to
2a2fdcc
Compare
2a2fdcc
to
5acbad1
Compare
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.
- Paths within
static
that are actually generated should includegenerated
in their path. Afind
andgrep
should show some existing paths that follow that convention. - I'd name
gen-cve-feed.sh
asfetch-cve-feed.sh
❓ How do we make sure that people don't accidentally commit that fetched file?
❓ For a container build, shouldn't the fetch happen inside the container?
Rendered page LGTM |
3d6f130
to
099ebeb
Compare
Should this PR target the dev-1.25 branch? (I'm not sure - do we want to add the feed with the v1.25 release, or perhaps actually combine the blog announcement for the new feed with the switch-on) We have options, and several of them are good. I want to be clear on which option we're picking so I can based my approval decision on that context. |
- Pull JSON blob from queried issues - Use layout output formats + templates to generate HTML table and JSON blob - Add localized strings and caption for CVE feed - Add a new page to describe details about CVE feed and how to use it - Update existing pages and link the official CVE feed from it Co-authored-by: Neha Lohia <[email protected]> Co-authored-by: Tim Bannister <[email protected]>
099ebeb
to
cafe6d2
Compare
I'm not sure I understand. Which of these is right:
? |
What I meant was, the feed goes live on v1.25 release day, the feature blog is followed soon after (in next few days). This will allow the feed to have some soak time to iron out any issues we find after going live :) |
Sounds good to me. /approve |
(I'd like somebody else to add the LGTM here) |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: nehaLohia27, 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 |
/cc @nehaLohia27 @savitharaghunathan (Tagging you both for |
/milestone 1.25 |
/lgtm |
LGTM label has been added. Git tree hash: 7581df102046b8f3ddd1be864ad4b2ad7561bd2b
|
Hi from the Comms team! We have you tracked for a feature blog, but the link provided to us was a KEP, not a placeholder blog PR. Are you still intending to have a feature blog for this release? |
Announcement blog article will be added via #35608 |
Description
Notes for Reviewers
Why are we regenerating JSON blob from the JSON blob in the bucket ?
Why not version control the JSON blob?
To avoid multiple sources of truth. The content in the bucket will remain the only source of truth as the JSON blob is constructed from GitHub issues with label
official-cve-feed
(See this for more info: kubernetes/test-infra#23428). However, as a break glass, there is an option to temporarily push the JSON blob by overriding the layouts json file with raw JSON in cases where push to bucket fails or if bucket is inaccessible.Are the locations for the layouts files correct?
Current locations are mostly my guess, so happy to refactor them as needed
TODO:
Preview: https://deploy-preview-35228--kubernetes-io-main-staging.netlify.app/docs/reference/issues-security/official-cve-feed/
KEP tracker: kubernetes/enhancements#3203
xref: kubernetes/sig-security#1
supersedes #31051 and #34765
/hold
/sig security docs