이 콘텐츠는 선택한 언어로 제공되지 않습니다.

Chapter 5. Operating a proxy


Monitor the operational status of the proxy and configure resource usage. This section explains how to check the status of the KafkaProxyIngress and VirtualKafkaCluster resources, and how to set CPU and memory requests and limits for the proxy container.

This section assumes you have a running Streams for Apache Kafka Proxy instance.

5.1. Checking the status of the VirtualKafkaCluster resource

The status of a VirtualKafkaCluster resource provides feedback on its configuration through a set of conditions. These include the ResolvedRefs condition, which indicates whether all referenced resources exist, and the Accepted condition, which indicates whether the cluster’s configuration was successfully applied to the proxy.

5.1.1. ResolvedRefs conditions

When you create a VirtualKafkaCluster, the operator checks whether the following exist:

  • A KafkaProxy matching spec.proxyRef.
  • Each KafkaProxyIngress specified in spec.ingresses, and whether they refer to the same KafkaProxy as the virtual cluster.
  • A Secret referred to in the tls property.

The result is reported in status.conditions with a ResolvedRefs condition accordingly.

Example VirtualKafkaCluster status when all referenced resources exist

kind: VirtualKafkaCluster
apiVersion: kroxylicious.io/v1alpha1
metadata:
  # ...
  generation: 12
spec:
  # ...
status:
  observedGeneration: 12 
1

  conditions:
    - type: ResolvedRefs 
2

      status: True 
3

      observedGeneration: 12
Copy to Clipboard Toggle word wrap

1
The observedGeneration in the status matches the metadata.generation, indicating that the status is up-to-date for the latest spec.
2
The ResolvedRefs condition type reports any issues with referenced resources.
3
A status value of True means that all referenced resources exist.

A status value of False means that one or more of the referenced resources is missing. In this case, the condition includes reason and message properties with more details.

5.1.2. Accepted conditions

When a VirtualKafkaCluster has a valid spec, the operator attempts to configure the proxy instance accordingly. This might not be possible. For example, the spec may be valid but incompatible with other virtual clusters running in the same proxy instance.

The operator sets a condition type of Accepted in status.conditions to indicate whether or not a virtual cluster has been successfully configured within a proxy instance.

5.2. Checking the status of the KafkaProxyIngress resource

The status of a KafkaProxyIngress resource provides feedback on its configuration through a set of conditions. These include the ResolvedRefs condition, which indicates whether all referenced resources exist.

When you create a KafkaProxyIngress, the operator checks whether a KafkaProxy corresponding to the spec.proxyRef exists. The result is reported in status.conditions with a ResolvedRefs condition accordingly.

Example KafkaProxyIngress status when spec.proxyRef exists

kind: KafkaProxyIngress
apiVersion: kroxylicious.io/v1alpha1
metadata:
  name: cluster-ip
  namespace: my-proxy
  generation: 12
spec:
  # ...
status:
  observedGeneration: 12 
1

  conditions:
    - type: ResolvedRefs 
2

      status: True 
3

      observedGeneration: 12
Copy to Clipboard Toggle word wrap

1
The observedGeneration in the status matches the metadata.generation, indicating that the status is up-to-date for the latest spec.
2
The ResolvedRefs condition type reports any issues with referenced resources.
3
A status value of True means that all referenced resources exist.

A status value of False means that the KafkaProxy resource is missing. In this case, the condition includes reason and message properties with more details.

5.3. Configuring Proxy container CPU and memory resource limits and requests

When you define a KafkaProxy resource, a number of OpenShift Pods are created, each with a proxy container. Each of these containers runs a single Streams for Apache Kafka Proxy process.

By default, these proxy containers are defined without resource limits. To manage CPU and memory consumption in your environment, modify the proxyContainer section within your KafkaProxy specification.

Example KafkaProxy configuration with proxy container resource specification

kind: KafkaProxy
apiVersion: kroxylicious.io/v1alpha1
metadata:
  namespace: my-proxy
  name: simple
spec:
  infrastructure:
    proxyContainer:
      resources:
        requests:
          cpu: '400m'
          memory: '656Mi'
        limits:
          cpu: '500m'
          memory: '756Mi'
Copy to Clipboard Toggle word wrap

Red Hat logoGithubredditYoutubeTwitter

자세한 정보

평가판, 구매 및 판매

커뮤니티

Red Hat 문서 정보

Red Hat을 사용하는 고객은 신뢰할 수 있는 콘텐츠가 포함된 제품과 서비스를 통해 혁신하고 목표를 달성할 수 있습니다. 최신 업데이트를 확인하세요.

보다 포괄적 수용을 위한 오픈 소스 용어 교체

Red Hat은 코드, 문서, 웹 속성에서 문제가 있는 언어를 교체하기 위해 최선을 다하고 있습니다. 자세한 내용은 다음을 참조하세요.Red Hat 블로그.

Red Hat 소개

Red Hat은 기업이 핵심 데이터 센터에서 네트워크 에지에 이르기까지 플랫폼과 환경 전반에서 더 쉽게 작업할 수 있도록 강화된 솔루션을 제공합니다.

Theme

© 2026 Red Hat
맨 위로 이동