Mention kustomize and RBAC in Ansible tutorial (#5796)

* Mention `kustomize` and RBAC in Ansible tutorial

Fixes #5731
Fixes #5730

Signed-off-by: Austin Macdonald <[email protected]>

* alphabetize link list for sanity

Signed-off-by: Austin Macdonald <[email protected]>

Author: asmacdo

website/content/en/docs/building-operators/ansible/tutorial.md

@@ -103,7 +103,7 @@ This memcached role will:
 - Set the Deployment size
 
 Note that the tasks in this Ansible role file are what actually defines the behavior of the spec and status of the memcached custom resource.
-As Kubernetes allows entry of arbitrary fields when creating resources, we don't need to actually create specific fields in the CRD. 
+As Kubernetes allows entry of arbitrary fields when creating resources, we don't need to actually create specific fields in the CRD.
 While we won't be doing this in this tutorial, it is recommended to also define these fields in the CRD, so that Kubernetes users
 can see the fields that will be used when using the custom resource.
 It is also good practice to set default values for variables used in Ansible
@@ -178,7 +178,18 @@ make install run
 
 By default, a new namespace is created with name `<project-name>-system`, ex. `memcached-operator-system`, and will be used for the deployment.
 
-Run the following to deploy the operator. This will also install the RBAC manifests from `config/rbac`.
+The scaffolded `Makefile` uses [`kustomize`][kustomize-docs] to apply
+custom configurations and generate manifests from the `config/`
+directory, which are piped to `kubectl`.
+
+```sh
+kustomize build config/default | kubectl apply -f -
+```
+
+Commonly, Operator authors may need to modify `config/rbac` in order to
+give their Operator the necessary permissions to reconcile.
+
+Run the following to customize the manifests and deploy the operator.
 
 ```sh
 make deploy
@@ -348,14 +359,15 @@ https://github.com/operator-framework/operator-sdk/issues/3447
 
 OLM will manage creation of most if not all resources required to run your operator, using a bit of setup from other operator-sdk commands. Check out the [OLM integration guide][tutorial-bundle].
 
-[legacy-quickstart-doc]:https://v0-19-x.sdk.operatorframework.io/docs/ansible/quickstart/
-[migration-guide]:/docs/building-operators/ansible/migration
-[install-guide]:/docs/building-operators/ansible/installation
-[image-reg-config]:/docs/olm-integration/cli-overview#private-bundle-and-catalog-image-registries
 [ansible-developer-tips]:/docs/building-operators/ansible/development-tips/
 [ansible-watches]:/docs/building-operators/ansible/reference/watches
 [custom-resources]:https://kubernetes.io/docs/concepts/extend-kubernetes/api-extension/custom-resources/
-[layout-doc]:/docs/building-operators/ansible/reference/scaffolding
 [doc-bundle]:https://github.com/operator-framework/operator-registry/blob/v1.16.1/docs/design/operator-bundle.md#operator-bundle
-[tutorial-bundle]:/docs/olm-integration/tutorial-bundle
 [doc-olm]:/docs/olm-integration/tutorial-bundle/#enabling-olm
+[image-reg-config]:/docs/olm-integration/cli-overview#private-bundle-and-catalog-image-registries
+[install-guide]:/docs/building-operators/ansible/installation
+[layout-doc]:/docs/building-operators/ansible/reference/scaffolding
+[legacy-quickstart-doc]:https://v0-19-x.sdk.operatorframework.io/docs/ansible/quickstart/
+[kustomize-docs]:https://kustomize.io/
+[migration-guide]:/docs/building-operators/ansible/migration
+[tutorial-bundle]:/docs/olm-integration/tutorial-bundle