The microprofile-reactive-messaging-kafka quickstart provides instructions to uninstall Kafka resources using:

  oc delete -f ./charts/kafka-on-openshift.yaml

However, this command does not properly clean up all resources due to incorrect deletion order in the YAML file.

Problem

The kafka-on-openshift.yaml file contains resources in this order:

• KafkaNodePool (controller)
• KafkaNodePool (broker)
• Kafka cluster (my-cluster)
• KafkaTopic (testing)

When executing oc delete -f kafka-on-openshift.yaml:

• Kubernetes attempts to delete resources from top to bottom
• It tries to delete the first resource (KafkaNodePool controller)
• However, the KafkaNodePool cannot be deleted because the KafkaTopic (which is at the end of the file) still exists and depends on the cluster
• The KafkaTopic should be deleted first, but it's at the end of the file
• This creates a dependency deadlock: cluster resources cannot be deleted while the topic exists, but the topic deletion is attempted last
• Result: First resources (KafkaNodePool, Kafka cluster) get stuck and cannot be deleted until the topic is manually removed

Actual behavior after uninstall

Resources remain in the namespace and get stuck during deletion because the dependency order is wrong.

Expected behavior

All resources should be cleanly deleted in the correct order: KafkaTopic first, then Kafka cluster and KafkaNodePools.

Affected file

quickstarts/microprofile-reactive-messaging-kafka/charts/kafka-on-openshift.yaml