Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Conformance tests for channel CRD spec requirements #2988

Closed
1 task
aliok opened this issue Apr 15, 2020 · 8 comments · Fixed by #3050
Closed
1 task

Conformance tests for channel CRD spec requirements #2988

aliok opened this issue Apr 15, 2020 · 8 comments · Fixed by #3050
Assignees
Labels

Comments

@aliok
Copy link
Member

aliok commented Apr 15, 2020

Problem

Extracting from the spec:

Spec Requirements
v1alpha1 Spec: each channel CRD MUST contain an array of subscribers: spec.subscribable.subscribers
v1beta1 Spec: each channel CRD MUST contain an array of subscribers: spec.subscribers

Tests:

  • Channel CRD MUST have spec.subscribable.subscribers or spec.subscribers. 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 Conformance tests for channel annotation requirements #2987.

Persona:
System Integrator, Contributors

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

Time Estimate (optional):
2d

@aliok aliok changed the title Conformance tests for channel spec requirements Conformance tests for channel CRD spec requirements Apr 15, 2020
@aliok
Copy link
Member Author

aliok commented Apr 16, 2020

/area channels
/area test-and-release

@knative-prow-robot knative-prow-robot added area/channels area/test-and-release Test infrastructure, tests or release labels Apr 16, 2020
@aliok
Copy link
Member Author

aliok commented Apr 24, 2020

/close

This test does not make a lot of sense.
Similar to #2989 (comment)

@knative-prow-robot
Copy link
Contributor

@aliok: Closing this issue.

In response to this:

/close

This test does not make a lot of sense.
Similar to #2989 (comment)

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.

@aliok
Copy link
Member Author

aliok commented Apr 24, 2020

/reopen

No, it makes sense. We cannot create CRs with random fiels; the fields should be configured. Webhook is configured that way and we can test it.

@knative-prow-robot
Copy link
Contributor

@aliok: Reopened this issue.

In response to this:

/reopen

No, it makes sense

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.

@matzew
Copy link
Member

matzew commented Apr 27, 2020

With a v1beta1 and v1alpha Channel (backed by IMC) I get nothing in the spec, for the channel. but for the actual IMC

spec:
  subscribers:
  - delivery:
      deadLetterSink: {}
    generation: 2
    subscriberUri: http://channel-display0.default.svc.cluster.local
    uid: 7e233c04-e250-478e-b9e8-8575157beb83

@matzew
Copy link
Member

matzew commented Apr 27, 2020

the spec.subscribers is updated by the subscription

@grantr grantr assigned aliok and lberk May 4, 2020
@aliok
Copy link
Member Author

aliok commented May 5, 2020

I added the conformance tests in #3050 but there's some things that are not compliant. Created #3051 for that.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants