-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Promote UnidirectionalTopicOperator
feature gate to GA
#9840
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Left few comments. Thanks a lot for the changes :)
api/src/main/java/io/strimzi/api/kafka/model/kafka/entityoperator/EntityOperatorSpec.java
Outdated
Show resolved
Hide resolved
documentation/modules/operators/ref-operator-cluster-feature-gates.adoc
Outdated
Show resolved
Hide resolved
systemtest/src/test/java/io/strimzi/systemtest/cruisecontrol/CruiseControlConfigurationST.java
Outdated
Show resolved
Hide resolved
systemtest/src/test/java/io/strimzi/systemtest/operators/topic/TopicST.java
Show resolved
Hide resolved
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the Pr, this looks good. I left some comments ... also some other things I think are missing:
- In docker-images, I think we do not need to install the stunnel anymore and the scripts for running / configuring it.
- In the docs, I left some comments. But in general, the docs are for Strimzi 0.41 and all mentiones of bidirectional TO can be removed apart form the feautre gates section that lists the (now unused) UTO feature gate and what it was doing. There is no need to explain that before 0.41 there was some other topic operator.
cluster-operator/src/test/java/io/strimzi/operator/cluster/model/EntityOperatorTest.java
Show resolved
Hide resolved
documentation/modules/operators/proc-changing-topic-operator-mode.adoc
Outdated
Show resolved
Hide resolved
documentation/modules/operators/ref-operator-cluster-feature-gates.adoc
Outdated
Show resolved
Hide resolved
systemtest/src/test/java/io/strimzi/systemtest/mirrormaker/MirrorMaker2ST.java
Outdated
Show resolved
Hide resolved
systemtest/src/test/java/io/strimzi/systemtest/mirrormaker/MirrorMaker2ST.java
Show resolved
Hide resolved
@scholzj I guess these warnings should not appear when the deprecated properties are not used right? status:
clusterId: vPnoXMxwTyay53EMBJ3chQ
conditions:
- lastTransitionTime: "2024-03-15T17:11:41.886032728Z"
status: "True"
type: Ready
- lastTransitionTime: "2024-03-15T17:10:09.681532310Z"
message: In resource Kafka(test/my-cluster) in API version kafka.strimzi.io/v1beta2
the zookeeperSessionTimeoutSeconds property at path spec.entityOperator.topicOperator.zookeeperSessionTimeoutSeconds
has been deprecated. This property has been deprecated because ZooKeeper is
not used anymore by the Topic Operator.
reason: DeprecatedFields
status: "True"
type: Warning
- lastTransitionTime: "2024-03-15T17:10:09.681532310Z"
message: In resource Kafka(test/my-cluster) in API version kafka.strimzi.io/v1beta2
the topicMetadataMaxAttempts property at path spec.entityOperator.topicOperator.topicMetadataMaxAttempts
has been deprecated. This property has been deprecated because ZooKeeper is
not used anymore by the Topic Operator.
reason: DeprecatedFields
status: "True"
type: Warning
kafkaMetadataState: ZooKeeper
kafkaVersion: 3.7.0
... |
@fvaleri Are those |
Not just that, we were also setting default values for these fields. Now it looks good. Please, run regression suites when you have time. Thanks. |
/azp run regression |
Azure Pipelines successfully started running 1 pipeline(s). |
/azp run feature-gates-regression |
Azure Pipelines successfully started running 1 pipeline(s). |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Some more nits. You should also:
- Update the Helm Chart in packaging to temove the TLS sidecar image
- Render the installation YAML from it
api/src/main/java/io/strimzi/api/kafka/model/kafka/entityoperator/EntityOperatorSpec.java
Outdated
Show resolved
Hide resolved
api/src/main/java/io/strimzi/api/kafka/model/kafka/entityoperator/EntityTopicOperatorSpec.java
Outdated
Show resolved
Hide resolved
api/src/main/java/io/strimzi/api/kafka/model/kafka/entityoperator/EntityTopicOperatorSpec.java
Outdated
Show resolved
Hide resolved
cluster-operator/src/test/java/io/strimzi/operator/cluster/model/EntityTopicOperatorTest.java
Outdated
Show resolved
Hide resolved
/azp run kraft-regression |
Azure Pipelines successfully started running 1 pipeline(s). |
/azp run upgrade |
Azure Pipelines successfully started running 1 pipeline(s). |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Overall lgtm. I left a few minor comments.
cluster-operator/src/main/java/io/strimzi/operator/cluster/model/KRaftUtils.java
Show resolved
Hide resolved
api/src/main/java/io/strimzi/api/kafka/model/kafka/entityoperator/EntityOperatorSpec.java
Outdated
Show resolved
Hide resolved
api/src/main/java/io/strimzi/api/kafka/model/kafka/entityoperator/EntityTopicOperatorSpec.java
Outdated
Show resolved
Hide resolved
api/src/main/java/io/strimzi/api/kafka/model/kafka/entityoperator/EntityTopicOperatorSpec.java
Outdated
Show resolved
Hide resolved
Signed-off-by: Federico Valeri <[email protected]>
/azp run kraft-regression |
Azure Pipelines successfully started running 1 pipeline(s). |
/azp run upgrade |
Azure Pipelines successfully started running 1 pipeline(s). |
/azp run regression |
Azure Pipelines successfully started running 1 pipeline(s). |
/azp run feature-gates-regression |
Azure Pipelines successfully started running 1 pipeline(s). |
@fvaleri I restarted it. But |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, assuming tests pass. 👍
Signed-off-by: Federico Valeri <[email protected]>
Ok, found the issue. With the last commit KafkaST.testRemoveComponentsFromEntityOperator should work with both STRIMZI_USE_KRAFT_IN_TESTS equal true (test currently failing) and false. |
/azp run kraft-regression |
Azure Pipelines successfully started running 1 pipeline(s). |
/azp run regression |
Azure Pipelines successfully started running 1 pipeline(s). |
/azp run feature-gates-regression |
Azure Pipelines successfully started running 1 pipeline(s). |
Signed-off-by: Federico Valeri <[email protected]> Signed-off-by: Lukas Kral <[email protected]> Co-authored-by: Lukas Kral <[email protected]> Signed-off-by: Steffen Karlsson <[email protected]>
Signed-off-by: Federico Valeri <[email protected]> Signed-off-by: Lukas Kral <[email protected]> Co-authored-by: Lukas Kral <[email protected]> Signed-off-by: Steffen Karlsson <[email protected]>
Signed-off-by: Federico Valeri <[email protected]> Signed-off-by: Lukas Kral <[email protected]> Co-authored-by: Lukas Kral <[email protected]>
This change promotes the
UnidirectionalTopicOperator
feature gate to GA. It removes the Bidirectional Topic Operator code and theUnidirectionalTopicOperator
feature gate. It also updates all related tests and documentation.Additional notes:
KRaftKafkaUpgradeDowngradeST
fails becauseSTRIMZI_USE_NODE_POOLS_IN_TESTS
is set to false by default (fixed separately).UTONotSupported
that should be re-enabled (fixed separately).