Cloud-event-proxy and consumer processes on the consumer deployment side use isolated cpus instead of reserved cpus.

# ps -e | grep "cloud-"                                                   
3798465 ?        00:00:54 cloud-event-con
3798482 ?        00:00:55 cloud-event-pro

# taskset -pc 3798465
pid 3798465's current affinity list: 3,5,7,9,11,13,15,17,19,21,23,25,27,29,31,33-71,75,77,79,81,83,85,87,89,91,93,95,97,99,101,103,105-143
# taskset -pc 3798482
pid 3798482's current affinity list: 3,5,7,9,11,13,15,17,19,21,23,25,27,29,31,33-71,75,77,79,81,83,85,87,89,91,93,95,97,99,101,103,105-143

cpu partitioning defined as following in the perf-profile:
isolated: "2-71,74-143"
reserved: "0-1,72-73"

Consumer deployment CR for events (https://github.com/redhat-cne/cloud-event-proxy/blob/main/examples/manifests/consumer.yaml)  requires the following annotation to correctly pin these processes to reserved cpus:

template:
  metadata:
    annotations:
      target.workload.openshift.io/management: '{"effect": "PreferredDuringScheduling"}'

1. Install PTP Operator
2. configure ptpOperatorConfi to enable events
3. create consumer deployment (example - https://github.com/redhat-cne/cloud-event-proxy/blob/main/examples/manifests/consumer.yaml)
4. Check the CPU affinity of the created processes on the cluster

    1.
    2.
    3.
    

    Consumer deployment processes for PTP events run on isolated cpus

https://github.com/redhat-cne/cloud-event-proxy/blob/main/examples/manifests/consumer.yaml