Please fill out the fields below so we can help you better. Note: you must provide your domain name to get help. Domain names for issued certificates are all made public in Certificate Transparency logs (e.g. crt.sh | example.com), so withholding your domain name here does not increase secrecy, but only makes it harder for us to provide help.
My domain is:
I ran this command:
It produced this output:
My web server is (include version):
The operating system my web server runs on is (include version):
My hosting provider, if applicable, is:
I can login to a root shell on my machine (yes or no, or I don't know):
I'm using a control panel to manage my site (no, or provide the name and version of the control panel):
The version of my client is (e.g. output of
certbot --version or
certbot-auto --version if you're using Certbot):
Using certbot and let's encrypt (thank you!) I have successfully created SSL certificates that I have used for connecting to my local rabbitmq deployment.This works fine!
According to the RabbitmqCluster operator TLS documentation, I need to enrich the certificate's Subject Alternative Name (SAN) with multiple attributes:
The certificate's Subject Alternative Name (SAN) must contain at least the following attributes: *.<RabbitMQ cluster name>-nodes.<namespace>.svc.<K8s cluster domain name> <RabbitMQ cluster name>.<namespace>.svc.<K8s cluster domain name>
If wildcards are not permitted, the certificate must provide a SAN attribute for each RabbitMQ node in the RabbitMQ cluster. For example, if you deploy a 3-node RabbitMQ cluster named myrabbit in namespace mynamespace with the default Kubernetes cluster domain cluster.local, the SAN must include at least the following attributes: myrabbit-server-0.myrabbit-nodes.mynamespace.svc.cluster.local myrabbit-server-1.myrabbit-nodes.mynamespace.svc.cluster.local myrabbit-server-2.myrabbit-nodes.mynamespace.svc.cluster.local myrabbit.mynamespace.svc.cluster.local
Note that the last SAN attribute is the client service DNS name. Depending on the service type used (spec.service.type), further SAN attributes may be required. For example, if using service type NodePort, the SAN must include the external IP address of each Kubernetes node.
Is it possible to create certificates that have such SAN attributes using let's encrypt?
If yes, could you please point me to the docs/examples on how to do it?