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
Is your feature request related to a problem? Please describe.
OpenEBS has deprecated their legacy do-everything helm chart, as seen here. This is unfortunately the chart currently used by k0s, and while there are docs on how to move from the embedded OpenEBS chart to a user-configured one, those docs still presuppose that you will be migrating to version 3.x of the do-everything chart.
There is a new OpenEBS localpv hostpath provisioner chart, here, that starts from version 4.0. However, it uses a different chart name + values configuration, and so the current documentation is insufficient.
Describe the solution you would like
Documentation on how to perform this migration would be greatly appreciated. An automatic migration of the storage extension version from 3.x to 4.x would be wonderful too, of course.
Describe alternatives you've considered
No response
Additional context
No response
The text was updated successfully, but these errors were encountered:
There's actually a successor openebs/openebs@4.0.1 chart at https://github.com/openebs/openebs/tree/main/charts (same chart name, different repository URL) - that would be far easier to migrate to than the subchart that only handles local path storage!
Is your feature request related to a problem? Please describe.
OpenEBS has deprecated their legacy do-everything helm chart, as seen here. This is unfortunately the chart currently used by k0s, and while there are docs on how to move from the embedded OpenEBS chart to a user-configured one, those docs still presuppose that you will be migrating to version 3.x of the do-everything chart.
There is a new OpenEBS localpv hostpath provisioner chart, here, that starts from version 4.0. However, it uses a different chart name + values configuration, and so the current documentation is insufficient.
Describe the solution you would like
Documentation on how to perform this migration would be greatly appreciated. An automatic migration of the storage extension version from 3.x to 4.x would be wonderful too, of course.
Describe alternatives you've considered
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: