Description of problem:
Instance creation for container security operator hit 404 error
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Goto operatorhub and install container security operator
2. After installation, try to create
Image Manifest Vulnerability instance on console
2. The Instance creation will redirect url "k8s/ns/default/clusterserviceversions/container-security-operator.v1.0.1/secscan.quay.redhat.com~v1alpha1~ImageManifestVuln/~new" that would get 404 error
It might no need the creation button for Image Manifest Vulnerability
Moving this to 4.6.
It seems the ideal path is to disable the create form as users are not intended to create an instance of this CR. We don't have that kind of functionality at this point, however.
There is a 4.6 story for at least tagging resources owned by operators. That seems a start in the right direction, though I don't think it addresses this issue, either.
Based on my discussion with Alec and Jon, we agreed that the Container security- Image Manifest Vul operator should be marked 'internal' in the CSV to fix this bug. I'm reassigning this bug to OLM team for consideration.
Jira story referenced in Comment 1:
I also created a Jira story (https://issues.redhat.com/browse/CONSOLE-2292) to improve the interaction on the console operator details page.
@Nick - Based on my conversations with Alec and Jon, we found out to fix this bug is to add "operators.operatorframework.io/internal-objects: '["imagemanifestvulns.secscan.quay.redhat.com"]'" to Container Security - Image Manifest Vul operator in the CSV. To learn more about the issue and proposed fix, please see this PR - https://github.com/openshift/console/pull/4702
Please let me know if there is any further questions.