Conformance tests for channel CRD status requirements

[aliok]

Problem

Following tasks are created according to the spec.

Note: this ticket is only for CRD validation. Values of the fields in the status are to be tested in #2992.

Tests:

• v1alpha1: Channel CRD MUST have astatus subresource which contains address and
  subscribableStatus.subscribers (as an array).
• v1alpha1: Channel CRD SHOULD have astatus subresource which contains observedGeneration and
  conditions (as an array). If they don't exist, report them.
• v1beta1: Channel CRD MUST have astatus subresource which contains address and
  subscribers (as an array).
• v1beta1: Channel CRD SHOULD have astatus subresource which contains observedGeneration and
  conditions (as an array). If they don't exist, report them.

Note: As there's no way of knowing what channel spec version the channel supports, instantiate a channel and then check the annotation messaging.knative.dev/subscribable in the channel instance . There's more info for this in #2987.

Note 2: Reporting the missing optional features is perhaps something done in serving conformance tests.

Persona:
System Integrator, Contributors

Exit Criteria
Test required behavior of channel, maybe report on optional capabilities.

Time Estimate (optional):
2d

[aliok]

/area channels
/area test-and-release

[aliok]

/assign @aliok

[aliok]

/close

This case is invalid. A Channel implements Channelable and these things in the PR description are always available in Channelables.
We cannot check if the CRD has these. We can only check if the instance, CR, has these fields set properly. There are other tests for them: #2992, #2993

[knative-prow-robot]

@aliok: Closing this issue.

Details

In response to this:

/close

This case is invalid. A Channel implements Channelable and these things in the PR description are always available in Channelables.
We cannot check if the CRD has these. We can only check if the instance, CR, has these fields set properly. There are other tests for them: #2992, #2993

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.