Closed creydr closed 1 month ago
I don't know how Eventing does this, but isn't the convention to remove the config-
when referring to CMs? The CM is not named config-config-features, or is it?
I don't know how Eventing does this, but isn't the convention to remove the
config-
when referring to CMs? The CM is not named config-config-features, or is it?
I didn't know this convention. But we use everywhere else config-features
(e.g. https://github.com/openshift-knative/eventing-kafka-broker/blob/4b716d32bde19ecd34b1efdb51734619c91723bf/openshift/knative-eventing.yaml#L15 or https://github.com/openshift-knative/eventing-kafka-broker/blob/4b716d32bde19ecd34b1efdb51734619c91723bf/openshift/knative-eventing-encryption-auth.yaml#L3).
And from https://github.com/knative/operator/blob/9099b1baa374fbc0ccf3093a53419fe54cf0dbf0/pkg/apis/operator/base/common.go#L224-L227 I would assume the real name.
[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: creydr, pierDipi
The full list of commands accepted by this bot can be found here.
The pull request process is described here
Currently we use different keys for the eventing config-features configmap in the KnativeEventing CR. E.g.
features
(here) orconfig-features
in #2660. This leads to patches like the following, which are problematic as only one is considered:This PR addresses it and updates the key for the CM accordingly.
This should help with https://github.com/openshift-knative/eventing-istio/pull/265#issuecomment-2111972249 and https://github.com/openshift-knative/serverless-operator/pull/2659