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
Copy file name to clipboardExpand all lines: site/kubernetes/operator/using-operator.md
+23-18Lines changed: 23 additions & 18 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -8,20 +8,20 @@ If RabbitMQ Cluster Kubernetes Operator is not installed,
8
8
see the [installation guide](/kubernetes/operator/install-operator.html). For instructions on getting started quickly, see the [quickstart guide](/kubernetes/operator/quickstart-operator.html).
9
9
This guide is structured in the following sections:
10
10
11
-
*[Confirm Service Availability](#service-availability).
12
-
*[Apply Pod Security Policies](#psp).
13
-
*[Create a RabbitMQ Instance](#create).
14
-
*[Existing examples](#examples).
15
-
*[Configure a RabbitMQ Instance](#configure).
16
-
*[Update a RabbitMQ Instance](#update).
17
-
*[Set a Pod Disruption Budget](#set-pdb).
18
-
*[Configure TLS](#tls).
19
-
*[Find Your RabbitmqCluster Service Name and Admin Credentials](#find).
20
-
*[Verify the Instance is Running](#verify-instance).
21
-
*[Use the RabbitMQ Service in Your App](#use).
22
-
*[Monitor RabbitMQ Clusters](#monitoring).
23
-
*[Delete a RabbitMQ Instance](#delete).
24
-
*[Pause Reconciliation for a RabbitMQ Instance](#pause).
11
+
*[Confirm Service Availability](#service-availability)
12
+
*[Apply Pod Security Policies](#psp)
13
+
*[Create a RabbitMQ Instance](#create)
14
+
*[Existing examples](#examples)
15
+
*[Configure a RabbitMQ Instance](#configure)
16
+
*[Update a RabbitMQ Instance](#update)
17
+
*[Set a Pod Disruption Budget](#set-pdb)
18
+
*[Configure TLS](#tls)
19
+
*[Find Your RabbitmqCluster Service Name and Admin Credentials](#find)
20
+
*[Verify the Instance is Running](#verify-instance)
21
+
*[Use the RabbitMQ Service in Your App](#use)
22
+
*[Monitor RabbitMQ Clusters](#monitoring)
23
+
*[Delete a RabbitMQ Instance](#delete)
24
+
*[Pause Reconciliation for a RabbitMQ Instance](#pause)
25
25
26
26
## <aid='service-availability'class='anchor'href='#service-availability'>Confirm Service Availability</a>
27
27
@@ -943,7 +943,10 @@ For more information about concepts mentioned above, see:
Transport Layer Security (TLS) is a protocol for encrypting network traffic. <ahref="/ssl.html">RabbitMQ supports TLS</a>, and the cluster operator simplifies the process of configuring a RabbitMQ cluster with <ahref="#one-way-tls">TLS</a> or <ahref="#mutual-tls">mutual TLS (mTLS)</a> encrypted traffic between clients and the cluter, as well as supporting <ahref="https://github.com/rabbitmq/cluster-operator/tree/main/docs/examples/mtls-inter-node">encrypting RabbitMQ inter-node traffic with mTLS</a>. A <ahref="/ssl.html#certificates-and-keys">basic overview of TLS</a> is helpful for understanding this guide.
946
+
Transport Layer Security (TLS) is a protocol for encrypting network traffic. <ahref="/ssl.html">RabbitMQ supports TLS</a>, and the cluster operator simplifies the process of configuring a RabbitMQ cluster with [TLS](#one-way-tls) or
947
+
[mutual TLS (mTLS)](#mutual-tls) encrypted traffic between clients and the cluter, as well
948
+
as supporting [encrypting RabbitMQ inter-node traffic with mTLS](https://github.com/rabbitmq/cluster-operator/tree/main/docs/examples/mtls-inter-node).
949
+
A [basic overview of TLS](/ssl.html#certificates-and-keys) is helpful for understanding this guide.
947
950
948
951
### <aid='one-way-tls'class='anchor'href='#one-way-tls'>TLS encrypting traffic between clients and RabbitMQ</a>
949
952
@@ -991,15 +994,16 @@ Mutual TLS (mTLS) enhances TLS by requiring that the server verify the identity
991
994
992
995
<imgsrc="/img/mTLS.png"/>
993
996
994
-
In addition to the <ahref="#one-way-tls">configuration required to support TLS</a>, configuring mutual TLS requires the RabbitMQ cluster to be configured with the CA certificate used to sign the client certificate and key pair, `ca.pem`. Create a Kuberntes secret with key `ca.crt` containing this secret
997
+
In addition to the [configuration required to support TLS](#one-way-tls), configuring mutual TLS requires the RabbitMQ cluster to be configured with the CA certificate
998
+
used to sign the client certificate and key pair, `ca.pem`. Create a Kuberntes secret with key `ca.crt` containing this secret
or create this secret using a tool such as <ahref="https://cert-manager.io/">Cert Manager</a>.
1001
1005
1002
-
Once this secret and the `tls-secret` exist, a RabbitMQ cluster cluster can be deployed following the <ahref="https://github.com/rabbitmq/cluster-operator/tree/main/docs/examples/mtls">mTLS example</a>.
1006
+
Once this secret and the `tls-secret` exist, a RabbitMQ cluster cluster can be deployed following the [mTLS example](https://github.com/rabbitmq/cluster-operator/tree/main/docs/examples/mtls).
1003
1007
1004
1008
<preclass="lang-yaml">
1005
1009
apiVersion: rabbitmq.com/v1beta1
@@ -1013,7 +1017,8 @@ spec:
1013
1017
caSecretName: ca-secret
1014
1018
</pre>
1015
1019
1016
-
In order to enforce client verification, RabbitMQ must be configured to reject clients that do not present certificates. This can be done by enabling <ahref="/ssl.html#peer-verification">TLS peer verification</a> using the `ssl_options.fail_if_no_peer_cert` option in the additional config:
1020
+
In order to enforce client verification, RabbitMQ must be configured to reject clients that do not present certificates. This can be done by enabling [TLS peer verification](ssl.html#peer-verification) using
1021
+
the `ssl_options.fail_if_no_peer_cert` option in the additional config:
0 commit comments