Requirements for an operator-managed Event Gateway

Edit online

Additional requirements and planning for an operator-managed Event Gateway installation.

Before you begin

Ensure that your environment meets the general requirements that are described in Planning your Event Gateway deployment.

Resource requirements

Minimum resource requirements for an Event Endpoint Management operator and operator-managed gateway deployment are shown in table 1.
Table 1. Event Endpoint Management Operator and Event Gateway resource requirements.
Deployment CPU (cores) Requests CPU (cores) Limits Memory (GiB) Requests Memory (GiB) Limits
Event Endpoint Management operator 0.2 1.0 0.5 1.0
Event Gateway instance 1.0 2.0 1.0 2.0

Requests and limits are Kubernetes concepts for controlling resource types such as CPU and memory.

  • Requests set the minimum requirements that a container requires to be scheduled. If your system does not have the required request value, then the services cannot start.
  • Limits set the maximum resource that a container can use. Containers that exceed a CPU resource limit are throttled, and containers that exceed a memory resource limit are terminated.

Ensure that you have sufficient CPU capacity and physical memory in your environment to service these requirements. Your Event Gateway instances can be dynamically updated later.

You can install only one version of the Event Endpoint Management operator on a cluster. Installing multiple versions on a single cluster is not supported due to possible compatibility issues as they share the Custom Resource Definitions (CRDs).

Cluster-scoped permissions required

The Event Endpoint Management operator requires the following cluster-scoped permissions, even if the operator is set to manage instances in a single namespace:

  • Permission to retrieve storage classes: The Event Endpoint Management operator uses admission webhooks to provide immediate validation and feedback about the creation and modification of the Event Gateway instances. The permission to retrieve storage classes is used by the webhooks to find a default storage class.
  • Permission to list specific CustomResourceDefinitions: This allows Event Endpoint Management to identify if other optional dependencies are installed in the cluster.

Red Hat OpenShift Security Context Constraints

If used, Event Endpoint Management requires a Security Context Constraint (SCC) to be bound to the target namespace before installation.

By default, Event Endpoint Management complies with restricted or restricted-v2 SCC depending on your Red Hat OpenShift Container Platform version.