Hide Forgot
Description of problem: In OpenShift 4.10, Kubernetes Services are [valid sink resources during Event Source creation](https://developers.redhat.com/articles/2022/03/22/whats-new-developers-openshift-410-console#openshift_4_10_serverless_and_eventing_features) - however, the generated `ContainerSource` resource sets `.spec.apiVersion` to `core/v1` instead of `v1`. This results in the `SinkBinding` failing to generate the URI to the sink. How reproducible: Yes Steps to Reproduce: 1. Install OpenShift Serverless on OpenShift 4.10.11 (RHPDS OpenShift 4.10 Workshop) and setup Knative Serving and Knative Eventing 2. Create a `Deployment` and `Service` that listens for CloudEvents - 3. In the OpenShift console, a. Select Add / Eventing / EventSource / ContainerSource / Create Event Source b. Set the Image field to something that sends CloudEvents - I used `ghcr.io/kwkoo/fast-ping` c. Set the Input Target field to Resource and point it to the `event-display-deploy` Service d. Click Create 4. When you look at the generated `SinkBinding`, you get: ``` ... spec: sink: ref: apiVersion: core/v1 kind: Service name: event-display-deploy namespace: demo subject: apiVersion: apps/v1 kind: Deployment name: fast-ping-deployment namespace: demo status: conditions: - lastTransitionTime: '2022-05-06T05:24:28Z' message: 'URI could not be extracted from destination ' reason: NoURI status: 'False' type: Ready ``` 5. It only works if you change `.spec.sink.ref.apiVersion` in the `ContainerSource` to `v1`
(Trigger Jira sync)
Verified on build version: 4.11.0-0.nightly-2022-05-20-213928 browser version: Chrome 99
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 (Important: OpenShift Container Platform 4.11.0 bug fix and security update), 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/RHSA-2022:5069