Strimzi
cluster-operator doesn't create external listener #6286
Replies: 5 comments 8 replies
-
|
For a start, you would probably need to format the YAML as a code to make it readable. |
Beta Was this translation helpful? Give feedback.
-
|
File in attach |
Beta Was this translation helpful? Give feedback.
-
Beta Was this translation helpful? Give feedback.
-
Beta Was this translation helpful? Give feedback.
-
|
Well, it tells you the error, or? It looks like your Ingress does not work and does not set the address on the Ingress resources in their status section. |
Beta Was this translation helpful? Give feedback.
-
|
all endpoints present |
Beta Was this translation helpful? Give feedback.
-
|
As I said above, you are missing the |
Beta Was this translation helpful? Give feedback.
-
|
It's normal status for my ingress controller |
Beta Was this translation helpful? Give feedback.
-
|
That it will not work with Strimzi. Strimzi expects it to set the address in the status. This is what the Kubernetes Nginx Ingress controller which we support and test with does. Because that failed, the operator does not know how to configure the broker and did not add the port to the pods. |
Beta Was this translation helpful? Give feedback.
-
Thanks a lot for help I find solution - I insert some params in config-map for ingress-controller After that - kafka-cluster created correctly |
Beta Was this translation helpful? Give feedback.
-
|
Interesting. I didn't know about such configuration. Seems to be set automatically in all my environments. But glad you made it work 👍 |
Beta Was this translation helpful? Give feedback.
-
|
describe ingress |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
HI! I need your help
I use cluster-operator to create a kafka-cluster
My platform - k8s version v1.22.3
When I apply yaml file to configure kafka-cluster, cluster-operator don't create a external listener
apiVersion: kafka.strimzi.io/v1beta2 kind: Kafka metadata: name: kafka-cluster namespace: kafka spec: kafka: version: 3.0.0 replicas: 3 listeners: - name: plain port: 9092 type: internal tls: false - name: tls port: 9093 type: internal tls: true - name: external port: 9094 type: ingress tls: true configuration: brokerCertChainAndKey: secretName: kafka-secret-tls certificate: tls.crt key: tls.key class: nginx bootstrap: host: kafka.service.rowi.tech brokers: - broker: 0 host: kafka-0.service.rowi.tech - broker: 1 host: kafka-1.service.rowi.tech - broker: 2 host: kafka-2.service.rowi.tech ............ config: # start manual config ssl.cipher.suites: "TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384" ssl.enabled.protocols: "TLSv1.2" ssl.protocol: "TLSv1.2" log.retention.hours: 24 log.segment.bytes: 104857600 log.retention.bytes: 1073741824 log.retention.check.interval.ms: 300000 log.cleaner.enable: truestatus of kafka-cluster
`
kubectl -n kafka get kafka kafka-cluster -o yaml
apiVersion: kafka.strimzi.io/v1beta2
kind: Kafka
metadata:
creationTimestamp: "2022-02-01T10:54:01Z"
generation: 2
name: kafka-cluster
namespace: kafka
resourceVersion: "27797783"
uid: b2c4e679-d534-403e-8fac-be519f4aa35d
spec:
cruiseControl:
metricsConfig:
type: jmxPrometheusExporter
valueFrom:
configMapKeyRef:
key: cruise-metrics-config.yml
name: cruise-control-metrics
entityOperator:
topicOperator: {}
userOperator: {}
kafka:
config:
default.replication.factor: 3
inter.broker.protocol.version: "3.0"
log.cleaner.enable: true
log.cleanup.policy: delete
log.retention.bytes: 1073741824
log.retention.check.interval.ms: 300000
log.retention.hours: 24
log.segment.bytes: 104857600
min.insync.replicas: 2
offsets.topic.replication.factor: 3
ssl.cipher.suites: TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384
ssl.enabled.protocols: TLSv1.2
ssl.protocol: TLSv1.2
transaction.state.log.min.isr: 2
transaction.state.log.replication.factor: 3
listeners:
- name: plain
port: 9092
tls: false
type: internal
- name: tls
port: 9093
tls: true
type: internal
- configuration:
bootstrap:
host: kafka.service.rowi.tech
brokerCertChainAndKey:
certificate: tls.crt
key: tls.key
secretName: kafka-secret-tls
brokers:
- broker: 0
host: kafka-0.service.rowi.tech
- broker: 1
host: kafka-1.service.rowi.tech
- broker: 2
host: kafka-2.service.rowi.tech
class: nginx
name: external
port: 9094
tls: true
type: ingress
metricsConfig:
type: jmxPrometheusExporter
valueFrom:
configMapKeyRef:
key: kafka-metrics-config.yml
name: kafka-metrics
replicas: 3
storage:
type: jbod
volumes:
- deleteClaim: false
id: 0
size: 45Gi
type: persistent-claim
version: 3.0.0
kafkaExporter:
enableSaramaLogging: true
groupRegex: .*
logging: debug
resources:
limits:
cpu: 500m
memory: 128Mi
requests:
cpu: 200m
memory: 64Mi
topicRegex: .*
zookeeper:
metricsConfig:
type: jmxPrometheusExporter
valueFrom:
configMapKeyRef:
key: zookeeper-metrics-config.yml
name: zookeeper-metrics-config
replicas: 3
storage:
deleteClaim: false
size: 15Gi
type: persistent-claim
status:
conditions:
message: Exceeded timeout of 300000ms while waiting for Ingress resource kafka-cluster-kafka-bootstrap
in namespace kafka to be addressable
reason: TimeoutException
status: "True"
type: NotReady
listeners:
port: 9092
bootstrapServers: kafka-cluster-kafka-bootstrap.kafka.svc:9092
type: plain
port: 9093
bootstrapServers: kafka-cluster-kafka-bootstrap.kafka.svc:9093
type: tls
observedGeneration: 2
`
As you can see, cluster-operator don't create a external listener with port 9094
How can i resolve my problem?
Thanks a lot.
Beta Was this translation helpful? Give feedback.
All reactions