Closed PushkarJ closed 1 year ago
/kind feature
The Kubernetes project currently lacks enough contributors to adequately respond to all issues.
This bot triages un-triaged issues according to the following rules:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the issue is closedYou can:
/remove-lifecycle stale
/close
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale
Add a field named "prow job", under the custom map of
_kubernetes.io
at the top of the feed (not part of each CVE item) with single value being "https://testgrid.k8s.io/sig-security-cve-feed#auto-refreshing-official-cve-feed"
Ah I was thinking that we wanted to link to the specific job that created the JSON itself, and I'm not sure we can do that simply. If it's just a hardcoded single value to the testgrid.k8s.io website, I guess it's fairly trivial! :)
/assign
/remove-lifecycle stale
/triage accepted /sig security docs /area security
@PushkarJ: The label(s) area/security
cannot be applied, because the repository doesn't have them.
Description
Freshness of a feed is dependent on successful scheduled prow job runs. Adding a link to job in the "json" feed and the markdown description, allows folks to look at the prow job to ensure that prow job has been running successfully as recent as few hours ago.
Details
Add a field named "prow job", under the custom map of
_kubernetes.io
at the top of the feed (not part of each CVE item) with single value being "https://testgrid.k8s.io/sig-security-cve-feed#auto-refreshing-official-cve-feed"