DOC-1229 Document feature: Package Operator CRDs with Operator Helm Chart (#1172)

Author: JakeSCahill

modules/ROOT/nav.adoc

@@ -65,7 +65,6 @@
 *** xref:deploy:deployment-option/self-hosted/kubernetes/k-production-workflow.adoc[Deployment Workflow]
 *** xref:deploy:deployment-option/self-hosted/kubernetes/k-requirements.adoc[Requirements and Recommendations]
 *** xref:deploy:deployment-option/self-hosted/kubernetes/k-tune-workers.adoc[Tune Worker Nodes]
-*** xref:deploy:deployment-option/self-hosted/kubernetes/k-25.1-beta.adoc[Try v25.1]
 *** xref:deploy:deployment-option/self-hosted/kubernetes/kubernetes-deploy.adoc[Deploy Redpanda]
 *** xref:deploy:deployment-option/self-hosted/kubernetes/k-deploy-connectors.adoc[Deploy Connectors]
 *** xref:deploy:deployment-option/self-hosted/kubernetes/k-high-availability.adoc[High Availability]

modules/deploy/pages/deployment-option/self-hosted/kubernetes/aks-guide.adoc

@@ -125,6 +125,12 @@ To delete your Kubernetes cluster:
 az aks delete --name <cluster-name> --resource-group redpandaResourceGroup
 ----
 
+To remove the convenience alias created during the quickstart:
+
+```bash
+unalias internal-rpk
+```
+
 include::deploy:partial$kubernetes/guides/troubleshoot.adoc[leveloffset=+1]
 
 include::deploy:partial$kubernetes/guides/next-steps.adoc[leveloffset=+1]

modules/deploy/pages/deployment-option/self-hosted/kubernetes/eks-guide.adoc

@@ -369,6 +369,12 @@ To delete your Kubernetes cluster:
 eksctl delete cluster --name <cluster-name>
 ----
 
+To remove the convenience alias created during the quickstart:
+
+```bash
+unalias internal-rpk
+```
+
 include::deploy:partial$kubernetes/guides/troubleshoot.adoc[leveloffset=+1]
 
 include::deploy:partial$kubernetes/guides/next-steps.adoc[leveloffset=+1]

modules/deploy/pages/deployment-option/self-hosted/kubernetes/k-25.1-beta.adoc

@@ -50,44 +50,9 @@ TIP: If you are already using the Redpanda Helm chart and want to migrate to the
 [[helm-and-redpanda-operator]]
 === Redpanda Operator
 
-The Redpanda Operator is designed for production-grade Redpanda deployments, offering enhanced lifecycle management, automation, and GitOps compatibility. It supports two deployment modes controlled by the `chartRef.useFlux` flag.
+The Redpanda Operator is designed for production-grade Redpanda deployments, offering enhanced lifecycle management, automation, and GitOps compatibility.
 
-==== Redpanda-managed mode
-
-(Default: `chartRef.useFlux: false`)
-
-The Redpanda Operator manages and reconciles Redpanda resources directly, without involving Flux. This mode works as follows:
-
-. The Redpanda Operator creates both `HelmRelease` and `HelmRepository` resources but suspends them, keeping Flux inactive.
-+
-NOTE: Although these resources are created in a suspended state, the Redpanda Operator still requires the Flux CRDs to be installed.
-. The Redpanda Operator directly reconciles Redpanda resources, performing tasks such as installations, updates, and cleanup, normally handled by Flux.
-. If `useFlux` is later re-enabled, the Redpanda Operator unsuspends the Flux resources, and Flux resumes lifecycle management.
-
-==== Flux-managed mode
-
-(Enabled with `chartRef.useFlux: true`)
-
-The Redpanda Operator delegates reconciliation to https://fluxcd.io/flux/concepts/[Flux^] controllers. The workflow is as follows:
-
-. The Redpanda Operator defines the necessary CRDs for Redpanda. A Redpanda resource represents a Redpanda cluster, configured through the Redpanda Helm chart values.
-. When the Redpanda Operator detects changes to Redpanda resources, it triggers Flux to reconcile the corresponding HelmRelease resource.
-. Flux uses the HelmRelease resource to manage the lifecycle of the Redpanda Helm chart, applying updates as needed.
-
-Example configuration to specify the deployment mode in Redpanda's custom resource:
-
-[,yaml]
-----
-apiVersion: cluster.redpanda.com/v1alpha2
-kind: Redpanda
-metadata:
-  name: redpanda
-spec:
-  chartRef:
-    useFlux: false
-----
-
-image::shared:operator-flux-relationship.png[CRDs for the Redpanda Operator include Flux CRDs. If you are running in Flux-managed mode, Flux manages the Redpanda Helm chart through the HelmRelease resource.]
+The Redpanda Operator directly reconciles Redpanda resources, performing tasks such as installations, updates, and cleanup.
 
 === Helm
 

modules/deploy/pages/deployment-option/self-hosted/kubernetes/k-deployment-overview.adoc

@@ -55,22 +55,9 @@ helm install cert-manager jetstack/cert-manager \
 +
 The Redpanda Helm chart enables TLS by default and uses cert-manager to manage TLS certificates.
 
-. Install the Redpanda Operator CRDs:
-+
-include::deploy:partial$kubernetes/install-crds.adoc[]
-
 . Deploy the Redpanda Operator.
 +
-[,bash,subs="attributes+"]
-----
-helm repo add redpanda https://charts.redpanda.com
-helm upgrade --install redpanda-controller redpanda/operator \
-  --namespace <namespace> \
-  --create-namespace \
-  --version {latest-operator-version} \ <1>
-----
-+
-<1> This flag specifies the exact version of the Redpanda Operator Helm chart to use for deployment. By setting this value, you pin the chart to a specific version, which prevents automatic updates that might introduce breaking changes or new features that have not been tested in your environment.
+include::deploy:partial$kubernetes/deploy-operator.adoc[]
 
 . Ensure that the Deployment is successfully rolled out:
 +

modules/deploy/pages/deployment-option/self-hosted/kubernetes/k-production-deployment.adoc

@@ -149,23 +149,9 @@ helm install cert-manager jetstack/cert-manager --set crds.enabled=true --namesp
 +
 TLS is enabled by default. The Redpanda Helm chart uses cert-manager to manage TLS certificates by default.
 
-. Install the Redpanda Operator custom resource definitions (CRDs):
-+
-include::deploy:partial$kubernetes/install-crds.adoc[]
-
 . Deploy the Redpanda Operator:
 +
-[,bash,subs="attributes+"]
-----
-helm repo add redpanda https://charts.redpanda.com
-helm repo update redpanda
-helm upgrade --install redpanda-controller redpanda/operator \
-  --namespace <namespace> \
-  --create-namespace \
-  --version {latest-operator-version} <1>
-----
-+
-<1> This flag specifies the exact version of the Redpanda Operator Helm chart to use for deployment. By setting this value, you pin the chart to a specific version, which prevents automatic updates that might introduce breaking changes or new features that have not been tested in your environment.
+include::deploy:partial$kubernetes/deploy-operator.adoc[]
 
 . Ensure that the Deployment is successfully rolled out:
 +
@@ -548,6 +534,11 @@ minikube delete
 --
 ======
 
+To remove the convenience alias created during the quickstart:
+
+```bash
+unalias internal-rpk
+```
 
 include::deploy:partial$kubernetes/guides/troubleshoot.adoc[leveloffset=+1]
 

modules/deploy/pages/deployment-option/self-hosted/kubernetes/local-guide.adoc

@@ -0,0 +1,36 @@
+ifdef::latest-operator-version[]
+[,bash,subs="attributes+"]
+----
+helm repo add redpanda https://charts.redpanda.com
+helm repo update
+helm upgrade --install redpanda-controller redpanda/operator \
+  --namespace <namespace> \
+  --create-namespace \
+  --version {latest-operator-version} \ <1>
+  --set crds.enabled=true <2>
+----
++
+<1> This flag specifies the exact version of the Redpanda Operator Helm chart to use for deployment. By setting this value, you pin the chart to a specific version, which prevents automatic updates that might introduce breaking changes or new features that have not been tested in your environment.
+<2> This flag ensures that the CRDs are installed as part of the Redpanda Operator deployment.
++
+:note-caption: Older versions of the Redpanda Operator
++
+[NOTE]
+========
+The `--set crds.enabled=true` flag is only supported in Redpanda Operator **v25.1.1 and later**.
+
+If you deploy an earlier version (such as v2.4.x), you must install the CRDs separately. See the xref:25.1@ROOT:deploy:deployment-option/self-hosted/kubernetes/k-production-deployment.adoc[v2.4.x deployment documentation] for more information.
+========
+endif::[]
+ifndef::latest-operator-version[]
+[,bash,subs="attributes+"]
+----
+helm repo add redpanda https://charts.redpanda.com
+helm repo update
+helm upgrade --install redpanda-controller redpanda/operator \
+  --namespace <namespace> \
+  --create-namespace \
+  --set crds.enabled=true <1>
+----
+<1> This flag ensures that the CRDs are installed as part of the Redpanda Operator deployment.
+endif::[]

modules/deploy/partials/kubernetes/deploy-operator.adoc

@@ -31,24 +31,9 @@ helm install cert-manager jetstack/cert-manager \
 +
 The Redpanda Helm chart uses cert-manager to enable TLS and manage TLS certificates by default.
 
-. Install the Redpanda Operator custom resource definitions (CRDs):
-+
-include::deploy:partial$kubernetes/install-crds.adoc[]
-
 . Deploy the Redpanda Operator:
 +
-[,bash,subs="attributes+"]
-----
-helm repo add redpanda https://charts.redpanda.com
-helm repo update
-helm upgrade --install redpanda-controller redpanda/operator \
-  --namespace <namespace> \
-  --create-namespace \
-  --timeout 1h \
-  --version {latest-operator-version} <1>
-----
-+
-<1> This flag specifies the exact version of the Redpanda Operator Helm chart to use for deployment. By setting this value, you pin the chart to a specific version, which prevents automatic updates that might introduce breaking changes or new features that have not been tested in your environment.
+include::deploy:partial$kubernetes/deploy-operator.adoc[]
 
 . Ensure that the Deployment is successfully rolled out:
 +