Skip to content

Commit b717ecf

Browse files
Using Kubernetes Operator: cosmetics
1 parent c060f7b commit b717ecf

File tree

1 file changed

+23
-18
lines changed

1 file changed

+23
-18
lines changed

site/kubernetes/operator/using-operator.md

Lines changed: 23 additions & 18 deletions
Original file line numberDiff line numberDiff line change
@@ -8,20 +8,20 @@ If RabbitMQ Cluster Kubernetes Operator is not installed,
88
see the [installation guide](/kubernetes/operator/install-operator.html). For instructions on getting started quickly, see the [quickstart guide](/kubernetes/operator/quickstart-operator.html).
99
This guide is structured in the following sections:
1010

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)
2525

2626
## <a id='service-availability' class='anchor' href='#service-availability'>Confirm Service Availability</a>
2727

@@ -943,7 +943,10 @@ For more information about concepts mentioned above, see:
943943

944944
## <a id='tls' class='anchor' href='#tls'>(Optional) Configure TLS</a>
945945

946-
Transport Layer Security (TLS) is a protocol for encrypting network traffic. <a href="/ssl.html">RabbitMQ supports TLS</a>, and the cluster operator simplifies the process of configuring a RabbitMQ cluster with <a href="#one-way-tls">TLS</a> or <a href="#mutual-tls">mutual TLS (mTLS)</a> encrypted traffic between clients and the cluter, as well as supporting <a href="https://github.com/rabbitmq/cluster-operator/tree/main/docs/examples/mtls-inter-node">encrypting RabbitMQ inter-node traffic with mTLS</a>. A <a href="/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. <a href="/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.
947950

948951
### <a id='one-way-tls' class='anchor' href='#one-way-tls'>TLS encrypting traffic between clients and RabbitMQ</a>
949952

@@ -991,15 +994,16 @@ Mutual TLS (mTLS) enhances TLS by requiring that the server verify the identity
991994

992995
<img src="/img/mTLS.png"/>
993996

994-
In addition to the <a href="#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
995999

9961000
<pre class='lang-bash'>
9971001
kubectl create secret generic ca-secret --from-file=ca.crt=ca.pem
9981002
</pre>
9991003

10001004
or create this secret using a tool such as <a href="https://cert-manager.io/">Cert Manager</a>.
10011005

1002-
Once this secret and the `tls-secret` exist, a RabbitMQ cluster cluster can be deployed following the <a href="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).
10031007

10041008
<pre class="lang-yaml">
10051009
apiVersion: rabbitmq.com/v1beta1
@@ -1013,7 +1017,8 @@ spec:
10131017
caSecretName: ca-secret
10141018
</pre>
10151019

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 <a href="/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:
10171022

10181023
<pre class="lang-yaml">
10191024
spec:

0 commit comments

Comments
 (0)