Skip to content
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

Upgrade external-snapshotter to use Debian 12 Distroless #1090

Open
jhawkins1 opened this issue May 14, 2024 · 1 comment
Open

Upgrade external-snapshotter to use Debian 12 Distroless #1090

jhawkins1 opened this issue May 14, 2024 · 1 comment

Comments

@jhawkins1
Copy link

jhawkins1 commented May 14, 2024

Is your feature request related to a problem?/Why is this needed

Describe the solution you'd like in detail

Since Debian 12 Distroless is available, as well as, the latest releases of Kubernetes and many of the Kubernetes related projects have moved to Debian 12, we would request that external-snapshotter components move to Debian 12 Distroless to align with other Kubernetes components.

Benefits: Alignment of the Container OS being used to other Kubernetes Components and related Projects. Reduces fan-out of multiple OSes or different versions of OSes across components. Potential benefits as to being able to obtain OS patches for vulnerabilities where Debian has decided only to fix in latest LTS (Debian 12) release and not older LTS releases.

Describe alternatives you've considered

Additional context

@kady1711
Copy link

Following up on the feature request for migrating the external-snapshotter components to Debian 12 Distroless. This migration is crucial for aligning with the current standards across the Kubernetes ecosystem, which has seen a significant shift towards Debian 12. The benefits of this migration include improved alignment with other Kubernetes components, reduced complexity in managing multiple OS versions, and enhanced security through access to OS patches for vulnerabilities that Debian has committed to fixing in its latest LTS release only.

Could you please provide an update on the status of this request? Specifically, it would be helpful to know if there is a targeted release date or version number by which this migration is expected to be completed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants