Some Kafka Topics not shown as "READY"

[AydinChavez]

Hi,

what could be the reason/fault for some Kafka Topics not shown as "READY" and having no cluster assigned to them?
I suspect that those were created by the Producer (having auto.create.topics.enable: true on broker side).

I could not find any related error message in the broker logs.
When using kubectl describe, there is also no particular event / error message listed which could hint to a misconfiguration.

kubectl get KafkaTopic -n kafka-dev

NAME                                                          CLUSTER   PARTITIONS   REPLICATION FACTOR   READY
consumer-offsets---84e7a678d08f4bd226872e5cdd4eb527fadc1c6a   myc       50           3                    True
logs                                                          myc       1            3                    True
myc.abcdef.archive.v1.out                                               3            3                    
myc.abcdef.archive.v1.in                                      myc       3            3                    True
..

[scholzj]

You should check the error messages in the:

• Topic operator logs
• In the status section of the custom resource (it normally contains some errors when the topic is not ready)

[AydinChavez]

For reference, solution was in this comment: #7168 (reply in thread)

[AydinChavez]

I don't have error messages in both of them - maybe the ones in the topic operator logs were there when topics being created but they not part of the kubectl log output anymore and I guess those logs are not persisted somewhere.

For the CR, there is even no Status-section for the topic not being ready in its YAML definition.
One difference is in the metadata.Generation field, but don't know if this is related:

Topic being OK/ready:

Name:        myc.abcdef.archive.v1.in  
Namespace:    kafka-dev
Labels:       app.kubernetes.io/instance=v1
              app.kubernetes.io/name=kafka-topics
              strimzi.io/cluster=mds
Annotations:  <none>
API Version:  kafka.strimzi.io/v1beta2
Kind:         KafkaTopic
Metadata:
  Creation Timestamp:  2022-08-03T11:19:44Z
  Generation:          2
  Managed Fields:
    API Version:  kafka.strimzi.io/v1beta2
    Fields Type:  FieldsV1
    fieldsV1:
      f:metadata:
        f:labels:
          .:
          f:strimzi.io/cluster:
      f:spec:
        .:
        f:config:
        f:replicas:
        f:topicName:
    Manager:      okhttp
    Operation:    Update
    Time:         2022-08-03T11:19:44Z
    API Version:  kafka.strimzi.io/v1beta2
    Fields Type:  FieldsV1
    fieldsV1:
      f:status:
        .:
        f:conditions:
        f:observedGeneration:
        f:topicName:
    Manager:      okhttp
    Operation:    Update
    Subresource:  status
    Time:         2022-08-03T11:19:45Z
    API Version:  kafka.strimzi.io/v1beta2
    Fields Type:  FieldsV1
    fieldsV1:
      f:metadata:
        f:annotations:
          .:
          f:kubectl.kubernetes.io/last-applied-configuration:
        f:labels:
          f:app.kubernetes.io/instance:
          f:app.kubernetes.io/name:
      f:spec:
        f:config:
          f:retention.ms:
          f:segment.bytes:
        f:partitions:
    Manager:         kubectl-client-side-apply
    Operation:       Update
    Time:            2022-08-03T17:51:28Z
  Resource Version:  35651527
  UID:               9d067609-2228-466a-be5a-c8b3d1fa83df
Spec:
  Config:
    retention.ms:   7200000
    segment.bytes:  1073741824
  Partitions:       3
  Replicas:         3
  Topic Name:       myc.abcdef.archive.v1.in  
Status:
  Conditions:
    Last Transition Time:  2022-08-03T17:51:29.623150Z
    Status:                True
    Type:                  Ready
  Observed Generation:     2
  Topic Name:              myc.abcdef.archive.v1.in  
Events:                    <none>

Topic not being ready:

Name:         myc.abcdef.archive.v1.out 
Namespace:    kafka-dev
Labels:       app.kubernetes.io/instance=v1
              app.kubernetes.io/name=kafka-topics
Annotations:  <none>
API Version:  kafka.strimzi.io/v1beta2
Kind:         KafkaTopic
Metadata:
  Creation Timestamp:  2022-08-03T17:51:28Z
  Generation:          1
  Managed Fields:
    API Version:  kafka.strimzi.io/v1beta2
    Fields Type:  FieldsV1
    fieldsV1:
      f:metadata:
        f:annotations:
          .:
          f:kubectl.kubernetes.io/last-applied-configuration:
        f:labels:
          .:
          f:app.kubernetes.io/instance:
          f:app.kubernetes.io/name:
      f:spec:
        .:
        f:config:
          .:
          f:retention.ms:
          f:segment.bytes:
        f:partitions:
        f:replicas:
    Manager:         kubectl-client-side-apply
    Operation:       Update
    Time:            2022-08-03T17:51:28Z
  Resource Version:  35651531
  UID:               7daa6221-c712-43f8-9b3e-4af41a9f8a05
Spec:
  Config:
    retention.ms:   7200000
    segment.bytes:  1073741824
  Partitions:       3
  Replicas:         3
Events:             <none>

[scholzj]

You seem to be missing the strimzi.io/cluster=mds label on that KafkaTopic. So the operator does not see it and therefore it does not set the status in any way (nor to an error, neither to ready)

[AydinChavez]

Thanks a lot, this is it!