Fix field names

Author: JakeSCahill

modules/manage/pages/kubernetes/k-configure-helm-chart.adoc

@@ -242,7 +242,7 @@ spec:
     config:
       extraClusterConfiguration:
         iceberg_rest_catalog_client_secret:
-          secretRef:
+          secretKeyRef:
             name: iceberg-config
             key: iceberg_rest_catalog_client_secret
 ----
@@ -265,7 +265,7 @@ Helm::
   config:
     extraClusterConfiguration:
       iceberg_rest_catalog_client_secret:
-        secretRef:
+        secretKeyRef:
           name: iceberg-config
           key: iceberg_rest_catalog_client_secret
 ----
@@ -283,19 +283,19 @@ helm upgrade --install redpanda redpanda/redpanda \
 helm upgrade --install redpanda redpanda/redpanda \
   --namespace <namespace> \
   --create-namespace \
-  --set config.extraClusterConfiguration.iceberg_rest_catalog_client_secret.secretRef.name=iceberg-config \
-  --set config.extraClusterConfiguration.iceberg_rest_catalog_client_secret.secretRef.key=iceberg_rest_catalog_client_secret
+  --set config.extraClusterConfiguration.iceberg_rest_catalog_client_secret.secretKeyRef.name=iceberg-config \
+  --set config.extraClusterConfiguration.iceberg_rest_catalog_client_secret.secretKeyRef.key=iceberg_rest_catalog_client_secret
 ----
 
 ====
 --
 ======
 
-This method supports both `secretRef` and `configMapRef`:
+This method supports both `secretKeyRef` and `configMapKeyRef`:
 
-- Use `secretRef` for sensitive data like access keys or credentials.
+- Use `secretKeyRef` for sensitive data like access keys or credentials.
 
-- Use `configMapRef` for shared, non-sensitive values such as URIs or feature flags.
+- Use `configMapKeyRef` for shared, non-sensitive values such as URIs or feature flags.
 
 You can apply this approach to any Redpanda configuration key, making your deployments more secure, modular, and easier to manage at scale.