Skip to content
This repository was archived by the owner on Feb 22, 2022. It is now read-only.
This repository was archived by the owner on Feb 22, 2022. It is now read-only.

KnativeEventing CRD doesn't have proper openApi validation definition #162

@aliok

Description

@aliok

Describe the bug
OpenAPI validation in KnativeEventing CRD is not good.
It doesn't provide anything useful.

$ kubectl explain knativeeventings.operator.knative.dev
KIND:     KnativeEventing
VERSION:  operator.knative.dev/v1alpha1

DESCRIPTION:
     <empty>

Expected behavior
Expected is something like KnativeServing example:

$ kubectl explain knativeserving
KIND:     KnativeServing
VERSION:  operator.knative.dev/v1alpha1

DESCRIPTION:
     Schema for the knativeservings API

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/sig-architecture/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/sig-architecture/api-conventions.md#types-kinds

   metadata     <Object>
     Standard object's metadata. More info:
     https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata

   spec <Object>
     Spec defines the desired state of KnativeServing

   status       <Object>
     Status defines the observed state of KnativeServing

To Reproduce

kubectl explain knativeeventings.operator.knative.dev

Knative release version
0.13.x

Additional context

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions