Merge branch 'main' into Doc-752

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

@@ -228,6 +228,7 @@ For details, see xref:get-started:licensing/add-license-redpanda/kubernetes.adoc
 [source,bash,subs="attributes+"]
 ----
 helm repo add redpanda https://charts.redpanda.com
+helm repo update
 helm install redpanda redpanda/redpanda \
   --version {latest-redpanda-helm-chart-version} \ <1>
   --namespace <namespace> \ <2>
@@ -286,6 +287,7 @@ Helm + Operator::
 [,bash,subs="attributes+"]
 ----
 helm repo add redpanda https://charts.redpanda.com
+helm repo update
 helm upgrade --install redpanda-controller redpanda/operator \
   --namespace <another-namespace> \
   --set image.tag={latest-operator-version} \
@@ -338,6 +340,7 @@ NOTE: Make sure to use unique node ports for the listeners in your Redpanda reso
 [source,bash,subs="attributes+"]
 ----
 helm repo add redpanda https://charts.redpanda.com
+helm repo update
 helm install redpanda-two redpanda/redpanda \
   --version {latest-redpanda-helm-chart-version} \
   --namespace <anothernamespace> \
@@ -391,6 +394,7 @@ Helm::
 [source,bash,subs="attributes+"]
 ----
 helm repo add redpanda https://charts.redpanda.com
+helm repo update
 helm install redpanda redpanda/redpanda \
   --version {latest-redpanda-helm-chart-version} \
   --namespace <namespace> \

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

@@ -158,6 +158,7 @@ include::deploy:partial$kubernetes/install-crds.adoc[]
 [,bash,subs="attributes+"]
 ----
 helm repo add redpanda https://charts.redpanda.com
+helm repo update redpanda
 helm upgrade --install redpanda-controller redpanda/operator \
   --namespace <namespace> \
   --set image.tag={latest-operator-version} \

modules/deploy/partials/kubernetes/guides/deploy-redpanda.adoc

@@ -40,6 +40,7 @@ include::deploy:partial$kubernetes/install-crds.adoc[]
 [,bash,subs="attributes+"]
 ----
 helm repo add redpanda https://charts.redpanda.com
+helm repo update
 helm upgrade --install redpanda-controller redpanda/operator \
   --namespace <namespace> \
   --set image.tag={latest-operator-version} \
@@ -139,6 +140,7 @@ TLS is enabled by default. The Redpanda Helm chart uses cert-manager to manage T
 [source,bash,subs="attributes+",lines=3+5-9]
 ----
 helm repo add redpanda https://charts.redpanda.com
+helm repo update
 helm install redpanda redpanda/redpanda \
   --version {latest-redpanda-helm-chart-version} \
   --namespace <namespace> --create-namespace \

modules/get-started/pages/install-beta.adoc

@@ -156,6 +156,7 @@ Install Redpanda with Helm from the RC build in https://hub.docker.com/r/redpand
 [source,bash,subs="attributes+"]
 ----
 helm repo add redpanda https://charts.redpanda.com
+helm repo update
 helm install redpanda redpanda/redpanda \
   --namespace <namespace> \
   --create-namespace --set image.repository=docker.redpanda.com/redpandadata/redpanda-unstable --set image.tag={redpanda-beta-tag}

modules/get-started/pages/licensing/overview.adoc

@@ -102,10 +102,18 @@ The following table lists the Enterprise features for Redpanda and how Redpanda
 | Validates schema IDs server-side to ensure schema compatibility. With schema ID validation, records associated with unregistered schemas are detected and dropped by a broker rather than a consumer.
 | Topics with schema validation settings cannot be created or modified.
 
+| xref:manage:topic-recovery.adoc[Topic Recovery]
+| Allows restoring a single topic from Tiered Storage using remote recovery properties.
+| You cannot create topics with the `redpanda.remote.recovery=true` property or perform topic recovery operations. To proceed, add a valid license to the target cluster. Without a valid license, topic recovery is blocked.
+
 | xref:manage:tiered-storage.adoc[Tiered Storage]
 | Enables data storage in cloud object storage for long-term retention and retrieval.
 | Topics cannot be created or modified to enable Tiered Storage features. Additional partitions cannot be added to topics with Tiered Storage properties enabled.
 
+| xref:manage:whole-cluster-restore.adoc[Whole Cluster Restore] (WCR)
+| Enables the recovery of cluster data from a source cluster's snapshot.
+| If the license is expired, you cannot perform WCR. To proceed, add a valid license to the target cluster. If the source cluster has an expired license, the target cluster inherits the restriction until a valid license is applied.
+
 |===
 
 [[console]]

modules/manage/pages/kubernetes/k-decommission-brokers.adoc

@@ -273,6 +273,7 @@ To install the Decommission controller as part of the Redpanda Operator:
 [,bash,subs="attributes+"lines=7+8]
 ----
 helm repo add redpanda https://charts.redpanda.com
+helm repo update
 helm upgrade --install redpanda-controller redpanda/operator \
   --namespace <namespace> \
   --set image.tag={latest-operator-version} \

modules/manage/pages/kubernetes/k-scale-redpanda.adoc

@@ -152,6 +152,7 @@ To install the Nodewatcher controller as part of the Redpanda Operator:
 [,bash,subs="attributes+",lines=7+8]
 ----
 helm repo add redpanda https://charts.redpanda.com
+helm repo update
 helm upgrade --install redpanda-controller redpanda/operator \
   --namespace <namespace> \
   --set image.tag={latest-operator-version} \

modules/manage/pages/kubernetes/k-schema-controller.adoc

@@ -59,17 +59,26 @@ When the manifest is applied, the schema will be created in your Redpanda cluste
 +
 [,bash]
 ----
-kubect get schema example-schema --namespace <namespace>
+kubectl get schema example-schema --namespace <namespace>
 ----
 
+. Create an alias to simplify running `rpk` commands on your cluster:
++
+[,bash]
+----
+alias internal-rpk="kubectl --namespace <namespace> exec -i -t <pod-name> -c redpanda -- rpk"
+----
++
+Replace `<pod-name>` with the name of a Pod that's running Redpanda.
+
 . Verify that the schema was created in Redpanda:
 +
 [source,bash]
 ----
-kubectl exec -it --namespace <namespace> <pod-name> -- curl https://<pod-name>.<cluster-name>.<namespace>.svc.cluster.local:8081/subjects -sS --cacert /etc/tls/certs/default/ca.crt -w '\n'
+internal-rpk registry subject list
 ----
 +
-Replace `<pod-name>` with the name of a Pod that's running Redpanda.
+You should see `example-schema` in the output.
 
 == Schema examples
 
@@ -244,8 +253,8 @@ You can also check specific versions of the schema:
 
 [source,bash]
 ----
-kubectl exec -it --namespace <namespace> <pod-name> -- curl https://<pod-name>.<cluster-name>.<namespace>.svc.cluster.local:8081/schemas/ids/1 -sS --cacert /etc/tls/certs/default/ca.crt -w '\n'
-kubectl exec -it --namespace <namespace> <pod-name> -- curl https://<pod-name>.<cluster-name>.<namespace>.svc.cluster.local:8081/schemas/ids/2 -sS --cacert /etc/tls/certs/default/ca.crt -w '\n'
+internal-rpk registry schema get --id 1
+internal-rpk registry schema get --id 2
 ----
 
 == Delete a schema
@@ -261,7 +270,7 @@ Verify that the schema was deleted by checking the Redpanda Schema Registry:
 
 [source,bash]
 ----
-kubectl exec -it --namespace <namespace> <pod-name> -- curl https://<pod-name>.<cluster-name>.<namespace>.svc.cluster.local:8081/subjects -sS --cacert /etc/tls/certs/default/ca.crt -w '\n'
+internal-rpk registry subject list
 ----
 
 == Suggested reading