Merge pull request #15716 from rook/mergify/bp/release-1.17/pr-15686

doc: add CephBucketTopic kafka mechanism field to upgrade docs (backport #15686)
This commit is contained in:
Blaine Gardner authored and GitHub committed 2025-04-15 10:19:52 -06:00
commit 84fe7dbc2f
2 files changed
+20

No files matched your search

+12
View File
@@ -71,6 +71,18 @@ those releases.
new `ROOK_OBC_ALLOW_ADDITIONAL_CONFIG_FIELDS` to enable users to set potentially risky options.
See [#15376](https://github.com/rook/rook/pull/15376) for more information.
* Kafka notifications configured via CephBucketTopic resources will now default
to setting the Kafka authentication mechanism to `PLAIN`. Previously, no auth
mechanism was specified by default. It was possible to set the auth mechanism
via `CephBucketTopic.spec.endpoint.kafka.opaqueData`. However, setting
`&mechanism=<auth type>` via `opaqueData` is no longer possible. If any auth
mechanism other than `PLAIN` is in use, modification to `CephBucketTopic`
resources is required.
See:
- [#15711](https://github.com/rook/rook/issues/15711)
- [#15554](https://github.com/rook/rook/pull/15554)
## Considerations
With this upgrade guide, there are a few notes to consider:
+8
View File
@@ -20,6 +20,14 @@ Object:
the new credential management feature instead.
For more details, see [#15359](https://github.com/rook/rook/issues/15359).
- Kafka notifications configured via CephBucketTopic resources will now default
to setting the Kafka authentication mechanism to `PLAIN`. Previously, no auth
mechanism was specified by default. It was possible to set the auth mechanism
via `CephBucketTopic.spec.endpoint.kafka.opaqueData`. However, setting
`&mechanism=<auth type>` via `opaqueData` is no longer possible. If any auth
mechanism other than `PLAIN` is in use, modification to `CephBucketTopic`
resources is required.
## Features
- Support external mons for local Rook cluster (see [#14733](https://github.com/rook/rook/issues/14733)).