Spike: Investigate what is needed for registry operator and helm chart consistency

[michael-valdron]

Which area/kind this issue is related to?

/area registry

Issue Description

The setup for the devfile registry helm chart and devfile registry operator are currently inconsistent. We need to ensure that the registry helm chart and registry operator setups are in sync before we can provide official releases #410.

First, we need to investigate what we need to change to ensure consistency of these setups.

#1028 is a bug which only exists in the registry operator and needs to be fixed in order to close this issue.

Related to #1260.

Outcome

To obtain details needed for implementing the changes needed to make the registry operator and registry helm chart consistent #1274.

Acceptance Criteria

• Investigate specifications under registry operator and registry helm chart
  • Deployment specifications
  • Service specifications
  • Route specifications
  • Ingress specifications
  • Configmap specifications
  • Persistent Volume Claim (PVC) specifications
• Investigate DevfileRegistry CR and helm chart parameters
• Investigate registry operator cluster service version (CSV) and the Chart.yaml
• Investigate hostname setup on both
• Investigate app name setup on both
• Investigate the helm chart requirements to check if it supports the same requirements as the registry operator

[michael-valdron]

blocked by #1028 changes to the deployment setup.

[michael-valdron]

#1211 is blocking this issue from starting and will be no longer be a blocker once the pre-release is cut.

[michael-valdron]

Investigating how to split this up for both epics, #410 and #1009.

[michael-valdron]

Investigating how to split this up for both epics, #410 and #1009.

Created #1260 to track changes to the helm chart and will be under #1009 epic. This issue will remain tracking changes to the registry operator and will still be under #410 epic.