Merge branch 'v-WIP/24.3' into K8S-380

modules/get-started/pages/licensing/monitor-license-status.adoc

@@ -1,5 +1,5 @@
 = Check the Status of an Enterprise Edition License
-:description: pass:q[Learn how to monitor the status of your Redpanda Enterprise Edition license using `rpk`, the Redpanda Console, the Admin API, and observability tools such as logs and metrics.]
+:description: pass:q[Learn how to monitor the status of your Redpanda Enterprise Edition license using `rpk`, Redpanda Console, and observability tools such as logs and metrics.]
 
 To track license expiration and ensure compliance with xref:get-started:licensing/overview.adoc[Redpanda licensing], you can monitor the status of your Enterprise Edition license using <<rpk, `rpk`>>, <<console, Redpanda Console>>, and observability tools such as <<logs, logs>> and <<metrics, metrics>>.
 
@@ -32,7 +32,7 @@ Indicates the current state of the license. Possible values include:
 * `expired`: The license has expired, and restrictions may apply to enterprise features.
 * `not_present`: No license is currently applied.
 
-|License violation 
+|License violation
 |
 A boolean value that indicates whether enterprise features are being used in violation of the licensing terms:
 
@@ -147,6 +147,41 @@ Redpanda Console displays warnings in the following scenarios:
 
 - *Redpanda Self-Managed enterprise features are in use without a valid license*: If the Redpanda cluster is using enterprise features without a valid license, Redpanda Console displays a warning specifying the features in use without proper licensing.
 
+== Use the Redpanda Operator to check license status
+
+If you deployed a Redpanda cluster in Kubernetes using the Redpanda Operator, you can monitor the Enterprise Edition license status from the Redpanda custom resource. The operator integrates license monitoring into the resource's `status.conditions` field, allowing you to get the license state with `kubectl`.
+
+Identify your Redpanda resources:
+
+[,bash]
+----
+kubectl get redpanda -A
+----
+
+Example output:
+
+[.no-copy]
+----
+NAMESPACE   NAME      LICENSE       READY   STATUS
+redpanda    cluster   Valid         True    Redpanda reconciliation succeeded
+----
+
+The `License` field indicates whether the license is valid. Possible values include:
+
+- `Valid`: The license is valid.
+- `Expired`: The license has expired.
+- `Not Present`: No license is applied.
+
+The Redpanda Operator performs a license check during reconciliation, which is triggered in the following cases:
+
+- If changes are made to the Redpanda resource or its status.
+
+- If changes are made to resources managed by the operator, such as the StatefulSet resources for brokers or Deployment resources for Redpanda Console.
+
+- If no changes occur, the operator reconciles every 10 hours (default cache resync interval).
+
+- If you force reconciliation by making a no-op change, such as adding an annotation, to the Redpanda resource.
+
 [[logs]]
 == Monitor a license in the logs
 

modules/get-started/pages/whats-new.adoc

@@ -25,7 +25,7 @@ For topics with Tiered Storage enabled, you can unmount a topic to safely detach
 
 == Intra-broker partition balancing
 
-xref:manage:cluster-maintenance/cluster-balancing.adoc#intra-broker-partition-balancing[Intra-broker partition balancing] has moved out of beta and is supported for production clusters. This dynamically balances partitions across cores within a Redpanda broker. You also can decrease the number of CPUs assigned to a broker. Existing partition replicas are reassigned to the remaining CPU cores when the broker restarts with fewer available cores.
+xref:manage:cluster-maintenance/cluster-balancing.adoc#intra-broker-partition-balancing[Intra-broker partition balancing] has moved out of beta and is supported for production clusters. This dynamically balances partitions across cores within a Redpanda broker. You also can decrease the number of CPUs assigned to a broker. Existing partition replicas are reassigned to the remaining CPU cores when the broker restarts with fewer available cores. You must explicitly enable this feature.
 
 == Tombstone removal
 

modules/manage/pages/topic-iceberg-integration.adoc

@@ -1,7 +1,7 @@
 = Iceberg Topics
 :description: Learn how to integrate Redpanda topics with Apache Iceberg.
 :page-context-links: [{"name": "Linux", "to": "manage:topic-iceberg-integration.adoc" } ]
-:page-categories: Management, High Availability, Data Replication, Integration
+:page-categories: Iceberg, Tiered Storage, Management, High Availability, Data Replication, Integration
 :page-beta: true
 
 [NOTE]