Is it possible to install this plugin using knative-operator?

[gilesrapkinb]

I'm trying to install knative-eventing using the operator, with eventing-kafka-broker installed via additionalManifests in the KnativeEventing resource:

apiVersion: operator.knative.dev/v1beta1
kind: KnativeEventing
metadata:
  name: knative-eventing
  namespace: knative-eventing
spec:
  version: 1.13.1
  additionalManifests:
  - URL: https://github.com/knative-extensions/eventing-kafka-broker/releases/download/knative-v1.13.1/eventing-kafka-controller.yaml
  - URL: https://github.com/knative-extensions/eventing-kafka-broker/releases/download/knative-v1.13.1/eventing-kafka-broker.yaml

However, the operator is throwing an error on install:

Install failed with message: the version of the manifests ve6b002188068b4caebdba747eda522f465fa1583 of the component kafka-broker-config does not match the target version of the operator CR v1.13.1

It looks like the operator is blocking on applying the extra manifests because the resources in them have the label app.kubernetes.io/version: "e6b002188068b4caebdba747eda522f465fa1583" (It looks like the version label has the git SHA rather than the version tag?). Is this a bug? Or am I trying to use the wrong manifests to install with the operator?

[pierDipi]

cc @houshengbo

[Cali0707]

@pierDipi I think this might be a bug in how we are building our releases in this repo. Looking at the releases from eventing core resources, the app.kubernetes.io/version label is set to the semantic version (e.g. "1.12.6"), but for our ekb releases it is the git SHA.

[github-actions]

This issue is stale because it has been open for 90 days with no
activity. It will automatically close after 30 more days of
inactivity. Reopen the issue with /reopen. Mark the issue as
fresh by adding the comment /remove-lifecycle stale.

[gilesrapkinb]

/remove-lifecycle stale

[github-actions]

This issue is stale because it has been open for 90 days with no
activity. It will automatically close after 30 more days of
inactivity. Reopen the issue with /reopen. Mark the issue as
fresh by adding the comment /remove-lifecycle stale.

[gilesrapkinb]

/remove-lifecycle stale

[richardvflux]

The knative-eventing version is also not necessarily in sync with the kafka extension either, as i write the current versions for v14 are like 7 versions apart. So I can understand it comparing 1.14 but not 1.14.14 for example.

[richardvflux]

I pulled the manifests and uploaded them elsewhere and hand-edited them to fix the versioning and that confirms that the issue is definitely the sha vs version issue.