You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We have enabled multiple listeners in the redpanda and disabled the advertised listener for mtlstest listener. In the generated redpanda configuration the the internall listener is removed from redpanda configuration for disabled advertised listener: mtlstest.
What did you expect to happen?
The listener port is removed from LB port mappingsr, no advertised listener is added for the disabled listener, but an internal listener is added for disabled listener.
But we need multiple options for managing advertised listeners' visibility:
Disable the external port mapping in LB but keep the advertised listener for use cases as custom ingress controllers/application gateways.
Disable the external listener: no port mapping in LB, no advertised listener
How can we reproduce it (as minimally and precisely as possible)?. Please include values file.
The external listener is disabled for mildest listener
external:
default:
enabled: true# -- The port used for external client connections.port: 9094# prefixTemplate: ""# -- If undefined, `listeners.kafka.external.default.port` is used.advertisedPorts:
- 443tls:
# enabled: truecert: external# default is "sasl"authenticationMethod: "sasl"mtlstest:
enabled: false# -- The port used for external client connections.port: 9194# prefixTemplate: ""# -- If undefined, `listeners.kafka.external.default.port` is used.advertisedPorts:
- 443tls:
enabled: truecert: externalrequireClientAuth: true# default is "sasl"authenticationMethod: "mtls_identity"
The redpanda generated configuration: The internal mtlstest listener is removed from redpanda configuration, but we want only to remove from LB configuration and keep the advertised listeners.
We don't currently expose a way to control which listeners appear within the Service port list.
The easiest way to work around this right now would be to disable the external Service entirely and manage the Service yourself.
external:
enabled: false
---
# Some other yaml file that you kubectl apply -fapiVersion: v1kind: Servicemetadata:
annotations: {}labels: {}name: my-custom-servicespec:
ports: [] # Your Ports hereselector: {} # You can copy the selectors that the chart users or copy labels from commonLabels.type: ClusterIP
What happened?
We have enabled multiple listeners in the redpanda and disabled the advertised listener for mtlstest listener. In the generated redpanda configuration the the internall listener is removed from redpanda configuration for disabled advertised listener: mtlstest.
What did you expect to happen?
The listener port is removed from LB port mappingsr, no advertised listener is added for the disabled listener, but an internal listener is added for disabled listener.
But we need multiple options for managing advertised listeners' visibility:
How can we reproduce it (as minimally and precisely as possible)?. Please include values file.
The redpanda generated configuration: The internal
mtlstest
listener is removed from redpanda configuration, but we want only to remove from LB configuration and keep the advertised listeners.Anything else we need to know?
5.8.12
Which are the affected charts?
Redpanda
Chart Version(s)
5.8.12
Cloud provider
AKS
JIRA Link: K8S-407
The text was updated successfully, but these errors were encountered: