RBAC Kafka consumer calls the Kessel Relations API. To prevent stale updates and ensure consistency when multiple consumer instances process messages, we need to implement a fencing token mechanism.

 What is a Fencing Token?

  A fencing token is a distributed locking pattern that prevents concurrent modifications from multiple consumer instances. When a Kafka partition is assigned to a consumer, that consumer acquires a unique
  lock token. All subsequent API calls to the Relations API must include this token. If the partition gets reassigned to another consumer (during rebalancing), the old consumer's token becomes invalid,
  preventing it from making stale updates.