Skip to content

feat: KafkaTopic controller - #1050

Open
labrenbe wants to merge 47 commits into
feat/kafka-adminfrom
feat/kafka-topic
Open

labrenbe wants to merge 47 commits into
feat/kafka-adminfrom
feat/kafka-topic

Conversation

@labrenbe

@labrenbe labrenbe commented Oct 23, 2026 •

Copy link
Copy Markdown
Member

Part of stackabletech/issues#888.

Description

Definition of Done Checklist

  • Not all of these items are applicable to all PRs, the author should update this template to only leave the boxes in that are relevant
  • Please make sure all these things are done and tick the boxes

Author

  • Changes are OpenShift compatible
  • CRD changes approved
  • CRD documentation for all fields, following the style guide.
  • Helm chart can be installed and deployed operator works
  • Integration tests passed (for non trivial changes)
  • Changes need to be "offline" compatible
  • Links to generated (nightly) docs added
  • Release note snippet added

Reviewer

  • Code contains useful comments
  • Code contains useful logging statements
  • (Integration-)Test cases added
  • Documentation added or updated. Follows the style guide.
  • Changelog updated
  • Cargo.toml only contains references to git tags (not specific commits or branches)

Acceptance

  • Feature Tracker has been updated
  • Proper release label has been added
  • Links to generated (nightly) docs added
  • Release note snippet added
  • Add type/deprecation label & add to the deprecation schedule
  • Add type/experimental label & add to the experimental features tracker

@labrenbe labrenbe self-assigned this Oct 23, 2026
@labrenbe
labrenbe changed the base branch from main to feat/kafka-admin October 23, 2026 19:01
@labrenbe
labrenbe marked this pull request as ready for review October 28, 2026 20:47
@labrenbe labrenbe moved this to Development: Waiting for Review in Stackable Engineering Oct 28, 2026
@labrenbe
labrenbe requested a review from a team October 28, 2026 20:48

@sbernauer sbernauer left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I very much like the extensive kuttl topic test! I only reviewed that.

One problem I noticed: I often times do --skip-delete to end up with a working example I can play around with. This PR always deletes everything at the end. Maybe you can ask AI if we can easily add something like stackabletech/airflow-operator#841 here as well. If not possible, I think this case is ok, as there is much deletion testing going on.

spec:
clusterRef:
name: test-kafka
topicName: orders

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

strimzi recommends to only set this when topicName != .metadata.name, which I agree with

Suggested change
topicName: orders

spec:
clusterRef:
name: test-kafka
topicName: orders

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

strimzi recommends to only set this when topicName != .metadata.name, which I agree with

Suggested change
topicName: orders

Comment on lines +8 to +14
clusterRef:
name: test-kafka
topicName: orders
partitions: 2
replicationFactor: 3
configOverrides:
retention.ms: "7200000"

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I find the tests easier to understand when we only patch what we want to patch

Suggested change
clusterRef:
name: test-kafka
topicName: orders
partitions: 2
replicationFactor: 3
configOverrides:
retention.ms: "7200000"
partitions: 2
replicationFactor: 3

spec:
clusterRef:
name: test-kafka
topicName: throttled

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

strimzi recommends to only set this when topicName != .metadata.name, which I agree with

Suggested change
topicName: throttled

spec:
clusterRef:
name: test-kafka
topicName: legacy

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

strimzi recommends to only set this when topicName != .metadata.name, which I agree with

Suggested change
topicName: legacy

Comment on lines +8 to +14
clusterRef:
name: test-kafka
topicName: orders
partitions: 5
replicationFactor: 1
configOverrides:
retention.ms: "10800000"

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I would contain the patch to what changed

Suggested change
clusterRef:
name: test-kafka
topicName: orders
partitions: 5
replicationFactor: 1
configOverrides:
retention.ms: "10800000"

Comment on lines +7 to +13
clusterRef:
name: test-kafka
topicName: orders
partitions: 5
replicationFactor: 1
configOverrides:
retention.ms: "10800000"

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I would contain the patch to what changed

Suggested change
clusterRef:
name: test-kafka
topicName: orders
partitions: 5
replicationFactor: 1
configOverrides:
retention.ms: "10800000"

Comment on lines +8 to +9
clusterRef:
name: test-kafka

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I would contain the patch to what changed

Suggested change
clusterRef:
name: test-kafka

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can we please reduce the patch to what we actually want to change, I guess managementAccess.enabled; false?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Status: Development: Waiting for Review

Development

Successfully merging this pull request may close these issues.

2 participants