Container image. The operator uses --default-broker-image when this field is absent.
nodeIdStart
integer
yes
First node id. Pod ordinal i -> node_id = nodeIdStart + i.
replicas
integer
no
1
Number of pods. Validation: it must equal 1.
resources
object
no
Broker container resources.
resources.claims
array
no
Claims lists the names of resources, defined in spec.resourceClaims, that are used by this container. This is an alpha field and requires enabling the DynamicResourceAllocation feature gate. This field is immutable. It can only be set for containers.
resources.limits
object
no
Limits describes the maximum amount of compute resources allowed. More info: https://kubernetes.io/docs/concepts/configuration/manage-resources-containers/
resources.requests
object
no
Requests describes the minimum amount of compute resources required. If Requests is omitted for a container, it defaults to Limits if that is explicitly specified, otherwise to an implementation-defined value. Requests cannot exceed Limits. More info: https://kubernetes.io/docs/concepts/configuration/manage-resources-containers/
roles
array
yes
Roles that each node in this pool has. Only the union {Controller, Broker} is supported.
storage
object
no
Storage configuration. None, which means that the field is absent, gives an emptyDir. That is the default. See [Storage].
storage.class
string
no
storage.deleteClaim
boolean
no
storage.size
string
no
storage.type
string
yes
storage.volumes
array
no
template
object
no
Optional pod-level customization for every pod in this pool.
template.affinity
object
no
The operator copies this to PodSpec.affinity.
template.affinity.nodeAffinity
object
no
Describes node affinity scheduling rules for the pod.
The scheduler will prefer to schedule pods to nodes that satisfy the affinity expressions specified by this field, but it may choose a node that violates one or more of the expressions. The node that is most preferred is the one with the greatest sum of weights, i.e. for each node that meets all of the scheduling requirements (resource request, requiredDuringScheduling affinity expressions, etc.), compute a sum by iterating through the elements of this field and adding "weight" to the sum if the node matches the corresponding matchExpressions; the node(s) with the highest sum are the most preferred.
If the affinity requirements specified by this field are not met at scheduling time, the pod will not be scheduled onto the node. If the affinity requirements specified by this field cease to be met at some point during pod execution (e.g. due to an update), the system may or may not try to eventually evict the pod from its node.
The scheduler will prefer to schedule pods to nodes that satisfy the affinity expressions specified by this field, but it may choose a node that violates one or more of the expressions. The node that is most preferred is the one with the greatest sum of weights, i.e. for each node that meets all of the scheduling requirements (resource request, requiredDuringScheduling affinity expressions, etc.), compute a sum by iterating through the elements of this field and adding "weight" to the sum if the node has pods which matches the corresponding podAffinityTerm; the node(s) with the highest sum are the most preferred.
If the affinity requirements specified by this field are not met at scheduling time, the pod will not be scheduled onto the node. If the affinity requirements specified by this field cease to be met at some point during pod execution (e.g. due to a pod label update), the system may or may not try to eventually evict the pod from its node. When there are multiple elements, the lists of nodes corresponding to each podAffinityTerm are intersected, i.e. all terms must be satisfied.
template.affinity.podAntiAffinity
object
no
Describes pod anti-affinity scheduling rules (e.g. avoid putting this pod in the same node, zone, etc. as some other pod(s)).
The scheduler will prefer to schedule pods to nodes that satisfy the anti-affinity expressions specified by this field, but it may choose a node that violates one or more of the expressions. The node that is most preferred is the one with the greatest sum of weights, i.e. for each node that meets all of the scheduling requirements (resource request, requiredDuringScheduling anti-affinity expressions, etc.), compute a sum by iterating through the elements of this field and adding "weight" to the sum if the node has pods which matches the corresponding podAffinityTerm; the node(s) with the highest sum are the most preferred.
If the anti-affinity requirements specified by this field are not met at scheduling time, the pod will not be scheduled onto the node. If the anti-affinity requirements specified by this field cease to be met at some point during pod execution (e.g. due to a pod label update), the system may or may not try to eventually evict the pod from its node. When there are multiple elements, the lists of nodes corresponding to each podAffinityTerm are intersected, i.e. all terms must be satisfied.
template.metadata
object
no
Extra labels and annotations on the pod template.
template.metadata.annotations
object
no
template.metadata.labels
object
no
template.nodeSelector
object
no
The operator copies this to PodSpec.nodeSelector.
template.tolerations
array
no
The operator copies this to PodSpec.tolerations.
Status
Field
Type
Required
Default
Description
conditions
array
no
[]
Standard Kubernetes-style condition list.
readyReplicas
integer
no
The same value as StatefulSet.status.readyReplicas.