Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

docs(edit): removes some mm1 content #10945

Merged
merged 1 commit into from
Dec 12, 2024
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Original file line number Diff line number Diff line change
Expand Up @@ -318,14 +318,13 @@ These components are not version dependent, so no additional configuration is ne

*Configuring the `image` property for Kafka, Kafka Connect, and Kafka MirrorMaker*

Kafka, Kafka Connect, and Kafka MirrorMaker support multiple versions of Kafka.
Kafka, Kafka Connect, and Kafka MirrorMaker 2 support multiple versions of Kafka.
Each component requires its own image.
The default images for the different Kafka versions are configured in the following environment variables:

* `STRIMZI_KAFKA_IMAGES`
* `STRIMZI_KAFKA_CONNECT_IMAGES`
* `STRIMZI_KAFKA_MIRROR_MAKER2_IMAGES`
* (Deprecated) `STRIMZI_KAFKA_MIRROR_MAKER_IMAGES`

These environment variables contain mappings between Kafka versions and corresponding images.
The mappings are used together with the `image` and `version` properties to determine the image used:
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -31,9 +31,6 @@ The configuration must specify:

For a deeper understanding of the Kafka MirrorMaker 2 cluster configuration options, refer to the link:{BookURLConfiguring}[Strimzi Custom Resource API Reference^].

NOTE: MirrorMaker 2 resource configuration differs from the previous version of MirrorMaker, which is now deprecated.
There is currently no legacy support, so any resources must be manually converted into the new format.

.Default configuration
MirrorMaker 2 provides default configuration values for properties such as replication factors.
A minimal configuration, with defaults left unchanged, would be something like this example:
Expand Down
2 changes: 1 addition & 1 deletion documentation/modules/configuring/con-pod-management.adoc
Original file line number Diff line number Diff line change
Expand Up @@ -13,4 +13,4 @@ You must not create, update, or delete `StrimziPodSet` resources.
The `StrimziPodSet` custom resource is used internally and resources are managed solely by the Cluster Operator.
As a consequence, the Cluster Operator must be running properly to avoid the possibility of pods not starting and Kafka clusters not being available.

NOTE: Kubernetes `Deployment` resources are used for creating and managing the pods of other components: Kafka Bridge, Kafka Exporter, Cruise Control, (deprecated) MirrorMaker 1, User Operator and Topic Operator.
NOTE: Kubernetes `Deployment` resources are used for creating and managing the pods of other components: Kafka Bridge, Kafka Exporter, Cruise Control, User Operator and Topic Operator.
Original file line number Diff line number Diff line change
Expand Up @@ -140,10 +140,6 @@ For example `{KafkaVersionLower}={DockerKafkaImagePrevious}, {KafkaVersionHigher
The mapping from the Kafka version to the corresponding image of MirrorMaker 2 for that version.
For example `{KafkaVersionLower}={DockerKafkaImagePrevious}, {KafkaVersionHigher}={DockerKafkaImageCurrent}`.

(Deprecated) `STRIMZI_KAFKA_MIRROR_MAKER_IMAGES`:: Required.
The mapping from the Kafka version to the corresponding image of MirrorMaker for that version.
For example `{KafkaVersionLower}={DockerKafkaImagePrevious}, {KafkaVersionHigher}={DockerKafkaImageCurrent}`.

`STRIMZI_DEFAULT_TOPIC_OPERATOR_IMAGE`:: Optional.
The default is `{DockerTopicOperator}`.
The image name to use as the default when deploying the Topic Operator
Expand Down
Loading