Bug 1830124
| Summary: | OCP 4.5 - Missing specDescriptor fields on "Create Operands Form" view for CRDs without a structural schema | ||||||
|---|---|---|---|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | tony.wu | ||||
| Component: | Management Console | Assignee: | bpeterse | ||||
| Status: | CLOSED DUPLICATE | QA Contact: | Yadan Pei <yapei> | ||||
| Severity: | unspecified | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | 4.5 | CC: | aos-bugs, jokerman, jonjacks | ||||
| Target Milestone: | --- | ||||||
| Target Release: | --- | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2020-05-06 15:54:39 UTC | Type: | Bug | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Embargoed: | |||||||
| Attachments: |
|
||||||
*** This bug has been marked as a duplicate of bug 1830125 *** |
Created attachment 1683454 [details] [OCP4.5]__Create_APIcast__Red_Hat_Integration-3scale_APIcast_gateway_Operator Description of problem: The latest Operand's creation form logic in OCP 4.5 Console requires the Operand (CRD) to have a structural schema, otherwise, no fields would be rendered on Operand's creation form even with specDescritpors included in Operator's CSV file. However, due to the below reasons, OCP 4.5 Console would still need to support the existing (OCP4.3/4.4) creation form logic: OCP 4.5 is based on k8s 1.18 Only CRDs in `apiextensions.k8s.io/v1` have to have a structural schema (available since k8s 1.16) CRD in `apiextensions.k8s.io/v1beta1` structural schema is "optional" and will be deprecated in k8s 1.19 (OCP 4.6) This means for OCP 4.5 (k8s 1.18), there will be still quite a lot of CRDs still in`apiextensions.k8s.io/v1beta1` without structural schema. (e.g. Red Hat Integration - 3scale APIcast gateway Operator, APIcast Operator, Business Automation, Akka Operator etc) Version-Release number of selected component (if applicable): OCP 4.5 How reproducible: 100% Steps to Reproduce: 1. Go to 'OperatorHub' view and install "Red Hat Integration - 3scale APIcast gateway" 2. Go to 'Installed Operators' view and create "APIcast" instance Actual results: A "blank" creation form only show "Name" and "Labels" fields. Expected results: A creation form show "Name" and "Labels" fields Support the original creation form logic as in OCP 4.4 in OCP 4.5 for those CRD without structural schema. If we would like to deprecate the old logic, that could be happening alongside with CRD deprecates `apiextensions.k8s.io/v1beta1` in k8s 1.19 Additional info: