Open ricardoapl opened 6 months ago
@ricardoapl you mentioned over on Slack that Manuel had done the CLOMonitor integration. Is there anything more to do?
Yes, I suggest the following based on Security Slam: Kubernetes Lightning Round
Release to Community Infrastructure
Automate Security Documentation
CLOMonitor: Secure Development Practices
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
/remove-lifecycle stale
/assign @ricardoapl /triage accepted
What would you like to be added:
Similar to what was proposed in https://github.com/kubernetes-sigs/prometheus-adapter/issues/638 for prometheus-adapter, I suggest we implement the following for metrics-server:
We should probably also follow up on CLOMonitor security checks previously configured in https://github.com/cncf/clomonitor/pull/1407:
Why is this needed:
I believe this relates to https://github.com/kubernetes/sig-release/blob/193a3cdf8d73e0888c7f6829eea3716918a5af4a/roadmap.md
/kind feature