이 콘텐츠는 선택한 언어로 제공되지 않습니다.
Chapter 2. Enhancements
AMQ Streams 2.1 adds a number of enhancements.
2.1. Kafka 3.1.0 enhancements 링크 복사링크가 클립보드에 복사되었습니다!
For an overview of the enhancements introduced with Kafka 3.1.0, refer to the Kafka 3.1.0 Release Notes.
2.2. Running AMQ Streams on a FIPS-enabled cluster 링크 복사링크가 클립보드에 복사되었습니다!
You can now run AMQ Streams on a FIPS-enabled cluster, although currently not in a FIPS-compliant configuration.
The OpenJDK used in AMQ Streams container images will automatically switch to FIPS mode on a FIPS-enabled cluster. This prevents AMQ Streams from running on the cluster.
To run AMQ Streams on a FIPS-enabled cluster, you disable the OpenJDK FIPS mode by setting a FIPS_MODE environment variable to disabled in the deployment configuration for the Cluster Operator. The AMQ Streams deployment won’t be FIPS compliant, but the AMQ Streams operators as well as all of its operands will be able to run on the FIPS-enabled Kubernetes cluster.
Example FIPS configuration for the Cluster Operator
apiVersion: apps/v1
kind: Deployment
spec:
# ...
template:
spec:
serviceAccountName: strimzi-cluster-operator
containers:
# ...
env:
# ...
- name: "FIPS_MODE"
value: "disabled"
# ...
- 1
- Disables the FIPS mode.
2.3. Cruise Control intra-broker disk balancing 링크 복사링크가 클립보드에 복사되었습니다!
Cruise Control remains in Technology Preview.
If you are running a Kafka deployment that uses JBOD storage with multiple disks on the same broker, Cruise Control can balance partitions between the disks.
You use the rebalanceDisk configuration option. To perform an intra-broker disk balance, you set rebalanceDisk to true under the KafkaRebalance.spec.
2.4. Feature gates move to beta maturity 링크 복사링크가 클립보드에 복사되었습니다!
The feature gates ControlPlaneListener and ServiceAccountPatching move to beta maturity. This means that they are both enabled by default.
Feature gates at the beta level of maturity are well tested and their functionality is not likely to change.
See Configuring feature gates and Feature gate releases.
The ControlPlaneListener feature gate must be disabled when upgrading from or downgrading to AMQ Streams 1.7 and earlier versions.
2.5. Loadbalancer Listener bootstrap service 링크 복사링크가 클립보드에 복사되었습니다!
A new listener configuration property let’s you control whether or not to create a bootstrap service for a loadBalancer type of listener. A <cluster_name>-kafka-external-bootstrap bootstrap service is created by default for a Kafka cluster. You can choose not to create the service for a loadbalancer by setting the createBootstrapService property to false in the listener configuration.
Example configuration for a loadbalancer external listener that does not create a bootsrap service
listeners:
#...
- name: external
port: 9094
type: loadbalancer
tls: true
authentication:
type: tls
configuration:
createBootstrapService: false
# ...
# ...
2.6. OAuth configuration options 링크 복사링크가 클립보드에 복사되었습니다!
New OAuth configuration properties have been introduced to the OAuth authentication configuration.
The properties related to timeouts and extracting groups information.
Timout properties
-
connectTimeoutSecondsspecifies the maximum time in seconds to connect to an authorization server before a timeout. -
readTimeoutSecondsspecifies the maximum time in seconds to read from an authorization server before a timeout.
The default is sixty seconds for both.
Groups properties
-
groupsClaimspecifies a JsonPath query to extract groups information from a JWT token or introspection endpoint response. Not set by default. -
groupsClaimDelimiterspecifies a delimiter to parse groups information when returned as a single delimited string. The default value is ',' (comma).
Example OAuth configuration for a Kafka broker listener
#...
- name: external
port: 9094
type: loadbalancer
tls: true
authentication:
type: oauth
# ...
connectTimeoutSeconds: 60
readTimeoutSeconds: 60
groupsClaim: "$.groups"
groupsClaimDelimiter: ","
See KafkaListenerAuthenticationOAuth schema reference and KafkaClientAuthenticationOAuth schema properties.