Strimzi
Warning while creating ingress listener: Translation failed: invalid ingress spec: service #6794
Replies: 1 comment 6 replies
-
|
I was facing this same exact issue, and in my case this was caused by the type of ingress. If you are trying to use nginx-ingress for this purpose, you must have ssl passthrough enabled (on nginx-ingress controller). If you do not have this, then your ingress will never reconcile (because 'regular' ingresses do not work on ClusterIP.). nginx-ingress with ssl-passthrough are an exception to this rule (as mentioned in the nginx documentation here Another thing I am seeing in this log is that the the 'from' column under events references loadbalancer-controller, and not nginx. To make sure nginx-ingress is used, you might need to add the required annotation to your host. Here is an example of the cluster configuration that we got running with nginx-ingress with ssl-passthrough enabled. apiVersion: kafka.strimzi.io/v1beta2
kind: Kafka
metadata:
name: kafka-cluster
annotations:
strimzi.io/node-pools: enabled
strimzi.io/kraft: enabled
spec:
kafka:
version: 3.8.0
metadataVersion: 3.8-IV0
listeners:
- name: plain
port: 9092
type: internal
tls: false
- name: tls
port: 9093
type: loadbalancer
tls: true
authentication:
type: tls
- name: public
port: 9095
type: ingress
tls: true
authentication:
type: tls
configuration:
brokers:
- broker: 0
host: broker-0.yourdomain.com
annotations:
kubernetes.io/ingress.class: "nginx"
bootstrap:
host: bootstrap.yourdomain.com
annotations:
kubernetes.io/ingress.class: "nginx" |
Beta Was this translation helpful? Give feedback.
-
|
@scholzj in my case I did see the annotations for ssl-passthrough appear, but I did not get the kubernetes.io/ingress.class: "nginx" annotation, causing the kubernetes cluster to try and add an ingress with its default type instead of using nginx-ingress. (nginx-ingress is not our default as we have more ingressclasses available). In the example outputs of the original post in this thread I also see that the ingress.class annotation is not present, so seems that @vaibhavk-cldcvr was running into the same issue here and might have had their issue fixed by adding this annotation manually. Perhaps I can try to reproduce this with a fresh setup. If I manage to reproduce it I will share it here, and if not will let you know as well ;) |
Beta Was this translation helpful? Give feedback.
-
|
I created a new nodePool and KafkaCluster with the same settings, but without the ingress class annotation. Result is the same as mentioned by @vaibhavk-cldcvr , so I think his problem was caused by the ingressclass not being set to nginx as well. My assumption is that this issue does not occur when your default ingress is set to nginx (and I think that almost everyone uses it as their default). and the configuration I used to set up this Kafka cluster: apiVersion: kafka.strimzi.io/v1beta2
kind: KafkaNodePool
metadata:
name: test-dual-role
labels:
strimzi.io/cluster: test-cluster
spec:
replicas: 1
roles:
- controller
- broker
storage:
type: jbod
volumes:
- id: 0
type: persistent-claim
size: 20Gi
class: standard-rwo
kraftMetadata: shared
deleteClaim: true
---
apiVersion: kafka.strimzi.io/v1beta2
kind: Kafka
metadata:
name: test-cluster
annotations:
strimzi.io/node-pools: enabled
strimzi.io/kraft: enabled
spec:
kafka:
version: 3.8.0
metadataVersion: 3.8-IV0
listeners:
- name: plain
port: 9092
type: internal
tls: false
- name: tls
port: 9093
type: loadbalancer
tls: true
authentication:
type: tls
- name: public
port: 9095
type: ingress
tls: true
authentication:
type: tls
configuration:
# brokerCertChainAndKey:
# secretName: kafka-le-certificate
# certificate: tls.crt
# key: tls.key
brokers:
- broker: 0
host: broker-0.testkafka.acceptance.evresys.nl
# annotations:
# kubernetes.io/ingress.class: "nginx"
bootstrap:
host: bootstrap.testkafka.acceptance.evresys.nl
# annotations:
# kubernetes.io/ingress.class: "nginx"
authorization:
type: simple
superUsers:
- evresys
config:
offsets.topic.replication.factor: 1
transaction.state.log.replication.factor: 1
transaction.state.log.min.isr: 1
default.replication.factor: 1
min.insync.replicas: 1
entityOperator:
topicOperator: {}
userOperator: {}I use strimzi installed via Would you like me to create a new issue for this @scholzj ? Really like the project and would love to help out in whatever way possible (e.g. updating documentation, unfortunately not very skilled in java) |
Beta Was this translation helpful? Give feedback.
-
|
I think the annotation is not used anymore for some time. There is a field in the Ingress resource. |
Beta Was this translation helpful? Give feedback.
-
|
You are correct, just stumbled across pull request 4715 Which deprecates this annotation in favor of the class field. Sorry about that, will try to do my homework a bit better next time ;) For the sake of completeness I will post the updated solution here. apiVersion: kafka.strimzi.io/v1beta2
kind: KafkaNodePool
metadata:
name: test-dual-role
labels:
strimzi.io/cluster: test-cluster
spec:
replicas: 1
roles:
- controller
- broker
storage:
type: jbod
volumes:
- id: 0
type: persistent-claim
size: 20Gi
class: standard-rwo
kraftMetadata: shared
deleteClaim: true
---
apiVersion: kafka.strimzi.io/v1beta2
kind: Kafka
metadata:
name: test-cluster
annotations:
strimzi.io/node-pools: enabled
strimzi.io/kraft: enabled
spec:
kafka:
version: 3.8.0
metadataVersion: 3.8-IV0
listeners:
- name: plain
port: 9092
type: internal
tls: false
- name: tls
port: 9093
type: loadbalancer
tls: true
authentication:
type: tls
- name: public
port: 9095
type: ingress
tls: true
authentication:
type: tls
configuration:
class: nginx # set your ingress class here
brokers:
- broker: 0
host: broker-0.testkafka.somedomain.com
bootstrap:
host: bootstrap.testkafka.somedomain.com
authorization:
type: simple
superUsers:
- evresys
config:
offsets.topic.replication.factor: 1
transaction.state.log.replication.factor: 1
transaction.state.log.min.isr: 1
default.replication.factor: 1
min.insync.replicas: 1
entityOperator:
topicOperator: {}
userOperator: {}
|
Beta Was this translation helpful? Give feedback.
-
Don't worry about that 😉. |
Beta Was this translation helpful? Give feedback.
-
Hello, this question is related to ingress type listener
my kafka config
Ingress type listener creates bootstrap service of type ClusterIP
when I describe the ingress created by this, I get this warning
Does this warning mean, traffic is prevented from going to service behind ingress? or why is it creating ClusterIP service instead of nodeport or loadbalancer?
Beta Was this translation helpful? Give feedback.
All reactions