DOC-1585 Explain that Glue requires redpanda_iceberg_delete set to false at the cluster level

Author: kbatuigas

modules/manage/pages/iceberg/iceberg-topics-aws-glue.adoc

@@ -44,6 +44,12 @@ the default partitioning `(hour(redpanda.timestamp))` is in use, it will instead
 
 If you want to use partitioning, you must specify a custom partition specification using your own partition columns (columns that are not nested).
 
+=== Manual deletion of Iceberg tables
+
+The AWS Glue catalog integration requires Redpanda Iceberg tables to be manually deleted. To manually delete Iceberg tables, you must first set the cluster property config_ref:iceberg_delete,true,properties/cluster-properties[`iceberg_delete`] to `false` when you first configure the catalog integration. 
+
+When `iceberg_delete` is set to `false`, you can delete the Redpanda topic, and then delete the Iceberg table data in AWS S3. You are required to delete the Iceberg table data if you delete an Iceberg topic and then create a new topic with the same name.
+
 == Authorize access to AWS Glue
 
 ifndef::env-cloud[]
@@ -117,7 +123,9 @@ Run `rpk cluster config edit` to update these properties:
 +
 [,bash]
 ----
-iceberg_enabled: true 
+iceberg_enabled: true
+# Glue requires Redpanda Iceberg tables to be manually deleted
+iceberg_delete: false 
 iceberg_catalog_type: rest
 iceberg_rest_catalog_endpoint: https://glue.<glue-region>.amazonaws.com/iceberg
 iceberg_rest_catalog_authentication_mode: aws_sigv4