fix(k8s,docs): scale ddb-cluster to single instance, pin minio to storage namespace, document 3-CP topology in USAGE

k8s/data/ddb-cluster.yaml

@@ -7,8 +7,10 @@ metadata:
     app: postgresql
     layer: data
 spec:
-  # 3-node cluster for HA
-  instances: 3
+  # Single instance — cp-1 is the only schedulable node in the 3-CP topology
+  # (.163/.166 are dedicated control planes with no workload scheduling/storage).
+  # Postgres standby HA is traded away; control-plane/etcd HA is unaffected.
+  instances: 1
 
   # PostgreSQL 16.2
   imageName: ghcr.io/cloudnative-pg/postgresql:16.2

k8s/infrastructure/minio/buckets.yaml

@@ -4,7 +4,7 @@ apiVersion: minio.min.io/v1alpha1
 kind: Bucket
 metadata:
   name: riotpiao-models
-  namespace: minio
+  namespace: storage
 spec:
   name: riotpiao-models
   versioning:
@@ -20,7 +20,7 @@ apiVersion: minio.min.io/v1alpha1
 kind: Policy
 metadata:
   name: policy-ollama
-  namespace: minio
+  namespace: storage
 spec:
   name: policy-ollama
   statements:
@@ -42,7 +42,7 @@ apiVersion: minio.min.io/v1alpha1
 kind: User
 metadata:
   name: user-ollama
-  namespace: minio
+  namespace: storage
 spec:
   accessKey: ollama-access-key
   secretKey: ollama-secret-key-changeme  # Override via Secret

k8s/infrastructure/minio/kustomization.yaml

@@ -1,6 +1,6 @@
 apiVersion: kustomize.config.k8s.io/v1beta1
 kind: Kustomization
-namespace: minio
+namespace: storage
 resources:
   - minio-tenant.yaml
   - minio-service.yaml