-
Bug DescriptionWhen I deploy a kafka instance, I find that the operator started entity-operator has no cpu, memory limit and requests, Steps to reproducekafka-instance.yaml apiVersion: kafka.strimzi.io/v1beta2
kind: Kafka
metadata:
name: kafka-cluster
spec:
kafka:
version: 3.4.0
image: test/kafka:0.37.0-kafka-3.4.0
authorization:
type: simple
replicas: 3
listeners:
- name: plain
port: 9092
type: internal
tls: false
- name: tls
port: 9093
type: internal
tls: true
authentication:
type: tls
config:
offsets.topic.replication.factor: 3
transaction.state.log.replication.factor: 3
transaction.state.log.min.isr: 2
default.replication.factor: 3
min.insync.replicas: 1
inter.broker.protocol.version: "3.4"
resources:
limits:
cpu: 4
memory: 4Gi
requests:
cpu: 2
memory: 2Gi
storage:
type: jbod
volumes:
- id: 0
type: persistent-claim
size: 5Gi
deleteClaim: false
zookeeper:
replicas: 3
storage:
type: persistent-claim
size: 5Gi
deleteClaim: false
resources:
limits:
cpu: 2
memory: 2Gi
requests:
cpu: 1
memory: 1Gi
entityOperator:
topicOperator: {}
userOperator: {}
---
apiVersion: kafka.strimzi.io/v1beta2
kind: KafkaTopic
metadata:
name: kafka-topic
labels:
strimzi.io/cluster: kafka-cluster
spec:
partitions: 1
replicas: 1
config:
retention.ms: 7200000
segment.bytes: 1073741824
---
apiVersion: kafka.strimzi.io/v1beta2
kind: KafkaUser
metadata:
name: kafka-user
labels:
strimzi.io/cluster: kafka-cluster
spec:
authentication:
type: tls
authorization:
type: simple
acls:
# Example consumer Acls for topic my-topic using consumer group my-group
# - resource:
# type: topic
# name: my-topic
# patternType: literal
# operations:
# - Describe
# - Read
# host: "*"
- resource:
type: group
name: "*"
patternType: literal
operations:
- Read
host: "*"
# Example Producer Acls for topic my-topic
- resource:
type: topic
name: kafka-topic
patternType: literal
operations:
- Create
- Describe
- Write
- Read
host: "*" apply yaml kubectl apply -f kafka-instance.yaml Expected behaviorExpect to be able to configure the entity-operator resources in the kafka-instance.yaml Strimzi version0.37.0 Kubernetes versionkubernetes 1.24.10 Installation methodHelm Chart InfrastructureNo response Configuration files and logsNo response Additional contextNo response |
Beta Was this translation helpful? Give feedback.
Answered by
scholzj
Dec 12, 2023
Replies: 1 comment 1 reply
-
You can set resources for the Entity Operator and its containers in the Kafka CR in the same way you do it for Kafka or ZooKeeper. E.g. entityOperator:
topicOperator:
resources:
requests:
memory: 256Mi
cpu: "0.2"
limits:
memory: 256Mi
cpu: "0.5"
userOperator:
resources:
requests:
memory: 512Mi
cpu: "0.2"
limits:
memory: 512Mi
cpu: "0.5"
tlsSidecar:
resources:
requests:
cpu: 200m
memory: 64Mi
limits:
cpu: 500m
memory: 128Mi |
Beta Was this translation helpful? Give feedback.
1 reply
Answer selected by
tanberBro
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
You can set resources for the Entity Operator and its containers in the Kafka CR in the same way you do it for Kafka or ZooKeeper. E.g.