You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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
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.
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
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.The text was updated successfully, but these errors were encountered: