Skip to content

Conformance tests for channel annotation requirements #2987

@aliok

Description

@aliok

Problem

Extracting from the spec:

Annotation Requirements
Each instantiated Channel (ie, Custom Object) SHOULD have an annotation indicating which version of the Channelable duck type it conforms to. We currently have two versions:
v1alpha1
v1beta1
So, for example to indicate that the Channel supports v1beta1 duck type, you should annotate it like so (only showing the annotations):

- apiVersion: messaging.knative.dev/v1beta1
  kind: YourChannelType
  metadata:
    annotations: 
      messaging.knative.dev/subscribable: v1beta1

Unfortunately, we had to make breaking changes between the two versions, and to ensure functionality, the channel implementer must indicate which version they support. To ensure backwards compatibility with old channels, if no annotation is given, we assume it's v1alpha1.

Tests:

  • Instantiated channel should have messaging.knative.dev/subscribable annotation with value v1alpha1 or v1beta1

Persona:
System Integrator, Contributors

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

Time Estimate (optional):
1d

Metadata

Metadata

Assignees

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions