-
-
Notifications
You must be signed in to change notification settings - Fork 41
Investigate using Image volumes for extensions #874
Copy link
Copy link
Open
Labels
area/imagesIssues that have any relation with any of the imagesIssues that have any relation with any of the imagesarea/installerIssues that have any relation with the installation scriptsIssues that have any relation with the installation scriptsarea/operatorsIssues that have any relation with the OperatorsIssues that have any relation with the OperatorsenhancementNew feature or requestNew feature or request
Description
Metadata
Metadata
Assignees
Labels
area/imagesIssues that have any relation with any of the imagesIssues that have any relation with any of the imagesarea/installerIssues that have any relation with the installation scriptsIssues that have any relation with the installation scriptsarea/operatorsIssues that have any relation with the OperatorsIssues that have any relation with the OperatorsenhancementNew feature or requestNew feature or request
Type
Fields
Give feedbackNo fields configured for issues without a type.
Projects
Status
Untriaged
Is your feature request related to a problem? Please describe.
Educates extension packages are installed via vendir, so that they are pulled from within the container image. For big extensions this might be a problem as startup would take longer time, as vendir would not use containerd caches (if configured on the platform) or any other caching/pull-through mechanism.
Describe the solution you'd like
Starting in kubernetes 1.33, Image volumes is in Beta and enabled by default, which means we can use the same cluster mechanisms to pull the images/extensions, benefiting from things like PullPolicy, as well as image proxies/pull-through and registries authentication mechanisms.
Describe alternatives you've considered
No response
Additional information
No response