Retire storage enabled volumes for the OCI registry

[michael-valdron]

Which area/kind this issue is related to?

/area registry

Issue Description

Currently, the registry operator and the registry helm chart support the usage of a storage enabled volume for the OCI registry path to be mounted on. This allowed OCI artifacts to persist across deployments of the registry. These OCI artifacts at this point are created from the source content on the devfile-index (registry server) image, therefore in addition with security challenges with OpenShift it is best that support for this feature is retired.

The registry operator field spec.storage.enabled should be deprecated and the helm chart field persistence.enabled should also be deprecated. The field spec.storage.enabled should be disabled by default in https://github.com/devfile/api/issues/1092.

Acceptance Criteria

• [ ] spec.storage.enabled should be disabled by default
• [ ] spec.storage.enabled should be marked as deprecated
• [ ] persistence.enabled should be marked as deprecated
• [ ] Update documentation to reflect these changes

[github-actions[bot]]

This issue is stale because it has been open for 90 days with no activity. Remove stale label or comment or this will be closed in 60 days.

[michael-valdron]

This is a future change that is planned to occur, removing the stale status.

[thepetk]

We might need to add the acceptance criteria for this issue. Putting it on "waiting" for now.

[michael-valdron]

We might need to add the acceptance criteria for this issue. Putting it on "waiting" for now.

This issue description has been updated to include the acceptance criteria items.

[elsony]

Make sure the doc includes that the doc mentioned will be using emptyDir storage by default.

[Horiodino]

Hii , i would like to work on the issue .can refer where to make changes exactly?

[github-actions[bot]]

This issue is stale because it has been open for 90 days with no activity. Remove stale label or comment or this will be closed in 60 days.