RabbitMQ packaged by VMware - Configure and use Ingress

This chart supports Ingress resources. If an Ingress controller, such as nginx-ingress or traefik, is installed in the cluster, that Ingress controller can be used to serve the application.

To enable Ingress integration, set the *.ingress.enabled parameter to true.

The most common scenario is to have one host name mapped to the deployment. In this case, the *.ingress.hostname property can be used to set the host name. The *.ingress.tls parameter can be used to add the TLS configuration for this host.

However, it is also possible to have more than one host. To facilitate this, the *.ingress.extraHosts parameter (if available) can be set with the host names specified as an array. The *.ingress.extraTLS parameter (if available) can also be used to add the TLS configuration for extra hosts.

NOTE: For each host specified in the *.ingress.extraHosts parameter, it is necessary to set a name, path, and any annotations that the Ingress controller should know about. Not all annotations are supported by all Ingress controllers, but this annotation reference document lists the annotations supported by many popular Ingress controllers.

Adding the TLS parameter (where available) will cause the chart to generate HTTPS URLs, and the application will be available on port 443. The actual TLS secrets do not have to be generated by this chart. However, if TLS is enabled, the Ingress record will not work until the TLS secret exists.

Learn more about Ingress controllers.

check-circle-line exclamation-circle-line close-line
Scroll to top icon