Patching for base images

[sozercan]

What would you like to be added:

Are there any plans to automatically patch actionable CVEs in base images, such as debian-base, and push new versions? Is this a manual process today?

Why is this needed:

It would be ideal if base image versions are automated when an actionable CVE is found so individual projects don't have to maintain OS level patching.

[puerco]

I'll start thinking about this. If anyone wants to sync with me on this issue let me know.
/help

[k8s-ci-robot]

@puerco:
This request has been marked as needing help from a contributor.

Please ensure the request meets the requirements listed here.

If this request no longer meets these requirements, the label can be removed
by commenting with the /remove-help command.

In response to this:

I'll start thinking about this. If anyone wants to sync with me on this issue let me know.
/help

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[saschagrunert]

Interesting topic. What would be the source of information for available CVEs?

[nasirhm]

I'll start thinking about this. If anyone wants to sync with me on this issue let me know.

I would like to work together on it.

[sladyn98]

@puerco I could help assist you with this. Let me know how : ) and would love to help

[PushkarJ]

@puerco has there been any progress on this? I am leading a new sub-group sig-security-tooling and would like to give this more visibility in our upcoming meeting so we can collaborate on this. Let me know what you think :)

/sig security

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue or PR as fresh with /remove-lifecycle stale
• Mark this issue or PR as rotten with /lifecycle rotten
• Close this issue or PR with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale