Subscriber receives irrelevant events


Subscriber receives irrelevant events.


To conform to Cloud Event specifications, Eventing modifies the event names to filter out prohibited characters. For details, see event name cleanup. In some cases, it can lead to a naming collision, which can cause subscribers to receive irrelevant events.


Follow these steps to detect if naming collision is the source of the problem:

  1. Get the clean types from the status of the Subscription.

    Click to copy
    kubectl -n {NAMESPACE} get {NAME} -o jsonpath='{.status.types}'
  2. Search for any other Subscription using the same CleanType as in your Subscription.

    Click to copy
    kubectl get -A | grep {CLEAN_TYPE}
  3. If you find that the CleanType collides with some other Subscription, a solution for this is to use a different event type.