Bug 1705752
| Summary: | Missing openapi CRD definitions for oc explain to work for image-registry operator CRD | |||
|---|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Maciej Szulik <maszulik> | |
| Component: | Image Registry | Assignee: | Adam Kaplan <adam.kaplan> | |
| Status: | CLOSED ERRATA | QA Contact: | Wenjing Zheng <wzheng> | |
| Severity: | unspecified | Docs Contact: | ||
| Priority: | unspecified | |||
| Version: | 4.1.0 | CC: | adam.kaplan, aos-bugs, eparis, obulatov, wzheng | |
| Target Milestone: | --- | Flags: | adam.kaplan:
needinfo-
|
|
| Target Release: | 4.2.0 | |||
| Hardware: | Unspecified | |||
| OS: | Unspecified | |||
| Whiteboard: | ||||
| Fixed In Version: | Doc Type: | Bug Fix | ||
| Doc Text: |
Cause: CRD doesn't have OpenAPI schema
Consequence: oc explain doesn't work for config.imageregistry resource
Fix: generate OpenAPI schema
Result: oc explain can provide information about config.imageregistry.operator.openshift.io.
|
Story Points: | --- | |
| Clone Of: | ||||
| : | 1705753 1709090 1714775 (view as bug list) | Environment: | ||
| Last Closed: | 2019-10-16 06:28:30 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: | ||||
| Bug Depends On: | 1712317 | |||
| Bug Blocks: | 1705753, 1708600, 1714775 | |||
|
Description
Maciej Szulik
2019-05-02 21:06:23 UTC
Adam, I couldn't figure out a component for cluster-samples-operator but I've created just one issue wrt to imageregistry and sample operator configs. I'd like to see both addressed. I created clone https://bugzilla.redhat.com/show_bug.cgi?id=1705753 to cover the samples operator aspect of this. @Maciej this is a bit of a riskier proposition, since adding library-go requires bumping k8s.io deps to 1.13. Can we address this as tech debt in 4.2 (with a potential z-stream update for 4.1)? Yes 4.1.x is perfect. *** Bug 1708597 has been marked as a duplicate of this bug. *** moving to 4.2.0, if you decide to backport it to 4.1.z create a clone. *** Bug 1659897 has been marked as a duplicate of this bug. *** Needs DESCRIPTION to be fully populated in order to pass. Current output from dev clusters:
```
$ oc explain config --api-version imageregistry.operator.openshift.io/v1
KIND: Config
VERSION: imageregistry.operator.openshift.io/v1
DESCRIPTION:
<empty>
FIELDS:
apiVersion <string>
APIVersion defines the versioned schema of this representation of an
object. Servers should convert recognized schemas to the latest internal
value, and may reject unrecognized values. More info:
https://git.k8s.io/community/contributors/devel/api-conventions.md#resources
kind <string>
Kind is a string value representing the REST resource this object
represents. Servers may infer this from the endpoint the client submits
requests to. Cannot be updated. In CamelCase. More info:
https://git.k8s.io/community/contributors/devel/api-conventions.md#types-kinds
metadata <Object>
Standard object's metadata. More info:
https://git.k8s.io/community/contributors/devel/api-conventions.md#metadata
spec <Object>
status <Object>
```
Waiting on input from the CLI team on how to proceed.
Oleg, https://github.com/openshift/cluster-image-registry-operator/pull/319 is closed. Other PRs associated w/ this BZ are closed or merged. Should it be moved to modified or back to assigned? Post doesn't seem correct at this point. Verified with below version:
Client Version: v4.2.0
Server Version: v1.14.0+1682e38
OpenShift Version: 4.2.0-0.nightly-2019-07-30-000900
$ oc explain config --api-version imageregistry.operator.openshift.io/v1
KIND: Config
VERSION: imageregistry.operator.openshift.io/v1
DESCRIPTION:
Config is the configuration object for a registry instance managed by the
registry operator
FIELDS:
apiVersion <string>
APIVersion defines the versioned schema of this representation of an
object. Servers should convert recognized schemas to the latest internal
value, and may reject unrecognized values. More info:
https://git.k8s.io/community/contributors/devel/api-conventions.md#resources
kind <string>
Kind is a string value representing the REST resource this object
represents. Servers may infer this from the endpoint the client submits
requests to. Cannot be updated. In CamelCase. More info:
https://git.k8s.io/community/contributors/devel/api-conventions.md#types-kinds
metadata <Object> -required-
Standard object's metadata. More info:
https://git.k8s.io/community/contributors/devel/api-conventions.md#metadata
spec <Object> -required-
status <Object>
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2019:2922 |