Support for image volume source

[brandtkeller]

Is your feature request related to a problem? Please describe.

Kubernetes 1.31 introduced image volume source in alpha.

As this is an associated OCI artifact - Zarf may require the need to be checking for images used as volumes during mutation in the agent.

Describe the solution you'd like

• Given a pod uses an image volume source
• When the mutation of a pod ocurs
• Then the image reference is updated to the zarf registry

Additional context

KEP-4639

Understand this is an alpha feature that requires the ImageVolume feature gate - opening this issue for tracking intent to support if not intending to support until graduation.

[AustinAbro321]

IMO given that this would be a simple, nonbreaking, change to the agent, this is something that doesn't need to wait until graduation to implement. IMO it'll be reasonable to add once tools like k3s and eks support 1.31

[phillebaba]

This needs to be discussed, regarding if we want to support Alpha features. I am a fan of OCI volumes but this feature will change in the future.

@AustinAbro321 this will not hit EKS when 1.31 gets there. Alpha features and for a while now Beta feature are disabled by default. We wont see any major adoption until it gets into a graduated state.

If we end up supporting this for a specific use case it should be marked with a big experimental flag that allows us to break it at any time.

[willswire]

It appears that Kubernetes v1.35 may include GA for ImageVolume. We may also want to keep a close eye on k3s-io/k3s#12390 which will include the necessary update for containerd to support image volumes.

[brandtkeller]

Thanks for the added context @willswire . Given that a target is approaching for GA - I believe it's important to start scoping this effort and work down the path of requirements (logic, testing, etc).

@a1994sc you have an open PR for this - are you interested in pursuing this further? (if so I will assign you and provide more feedback on the PR directly)

[a1994sc]

@brandtkeller I would be more then happy to be assigned this ticket!

I was thinking about circling back on this around when 1.35 released, but would be happy to test on that 1.34.x of k3s that has the support