Replies: 1 comment
-
The RabbitMQ team does not maintain this helm chart. We have a RabbitMQ cluster operator that has TLS support. Here are some examples/docs that you can check out: |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hi
i am using helm char to deploy rabbitmq in cluster
https://github.com/bitnami/charts/blob/master/bitnami/rabbitmq/values.yaml
using
Enable encryption to rabbitmq
ref: https://www.rabbitmq.com/ssl.html
tls:
enabled: true
failIfNoPeerCert: false
sslOptionsVerify: verify_none
existingSecret:xxxxx
existingSecretFullChain: true
i am already having NLB and using ingress i can communicate to 5672 for communication but want to enable tls communication over 5671 with port ampqs and want to take leverage of certificate rotation by Lets-encrypt in cluster. Can you guide me how can i enable it
i have tried this echo "apiVersion: configuration.konghq.com/v1beta1
kind: TCPIngress
metadata:
name: rabbit-release-rabbitmq
annotations:
kubernetes.io/ingress.class: kong
spec:
entryPoints:
- amqps
routes:
- match: HostSNI(
xxxxxxx.com
)rules:
backend:
serviceName: rabbit-release-rabbitmq
servicePort: 5671
tls:
hosts:
passthrough: true
" | kubectl apply -f -
if i change the servicePort: 5672
then i can receive data over ampqs from client as well . is this correct way to handle traffic over tls ?
Beta Was this translation helpful? Give feedback.
All reactions