feat(helm): add ingress configuration and TLS certificate for RabbitMQ

Signed-off-by: zhenyus <zhenyus@mathmast.com>

freeleaps/helm-pkg/3rd/rabbitmq/patch/certificate.yaml

@@ -0,0 +1,13 @@
+apiVersion: cert-manager.io/v1
+kind: Certificate
+metadata:
+  name: alpha.rabbitmq.freeleaps.mathmast.com-cert
+  namespace: freeleaps-alpha
+spec:
+  commonName: alpha.rabbitmq.freeleaps.mathmast.com
+  dnsNames:
+    - alpha.rabbitmq.freeleaps.mathmast.com
+  issuerRef:
+    name: mathmast-dot-com
+    kind: ClusterIssuer
+  secretName: alpha.rabbitmq.freeleaps.mathmast.com-cert

freeleaps/helm-pkg/3rd/rabbitmq/values.alpha.yaml

@@ -317,4 +317,12 @@ metrics:
           summary: Too many connections (instance {{ "{{ $labels.instance }}" }})
           description: |
               RabbitMQ instance has too many connections (> 1000)
-              VALUE = {{ "{{ $value }}" }}\n  LABELS: {{ "{{ $labels }}" }}
+              VALUE = {{ "{{ $value }}" }}\n  LABELS: {{ "{{ $labels }}" }}
+ingress:
+  enabled: true
+  path: /
+  pathType: ImplementationSpecific
+  hostname: alpha.rabbitmq.freeleaps.mathmast.com
+  tls: true
+  existingSecret: "alpha.rabbitmq.freeleaps.mathmast.com-cert"
+  ingressClassName: "nginx"