Closed trgeiger closed 2 months ago
Name | Link |
---|---|
Latest commit | 494291d0da670a07c52c7a307ec2b153853e97a3 |
Latest deploy log | https://app.netlify.com/sites/olmv1/deploys/6697e27f46c4720008de77e8 |
Deploy Preview | https://deploy-preview-1060--olmv1.netlify.app |
Preview on mobile | Toggle QR Code...Use your smartphone camera to open QR code link. |
To edit notification comments on pull requests, go to your Netlify site configuration.
All modified and coverable lines are covered by tests :white_check_mark:
Project coverage is 73.91%. Comparing base (
ca4f4e3
) to head (494291d
).
:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.
This matches the default configuration in OLMv0 by including OperatorHub
Description
This change simply adds the OperatorHub ClusterCatalog to the installation script. On a fresh installation, users will now have the same default operator listings as in OLMv0.
Right now I just have the script applying the sample YAML from this repository. If we wanted to match the way we install actual releases of Cert Manager and Catalogd, then I could make a PR in Catalogd to add the OperatorHub catalog yaml to the release artifacts and cut a release of Catalogd for those to be included.
Related issue: #1026
I'll follow up this PR with documentation changes as suggested in 1026
Reviewer Checklist