Design Crossplane XRD schema for managed RDS provisioning

[sarajkrishnasingh]

Starting Crossplane for workload-level AWS resources. First composition: RDS.

Proposed claim interface (PostgresDatabase):

apiVersion: platform.tcs.io/v1alpha1
kind: PostgresDatabase
metadata:
  name: my-app-db
spec:
  parameters:
    storageGB: 20
    instanceClass: db.t3.medium
    multiAZ: false
    backupRetentionDays: 7
    engineVersion: "15.4"
  writeConnectionSecretToRef:
    name: my-app-db-conn

Composition would handle: DBSubnetGroup, ParameterGroup, SecurityGroup, RDS instance, connection secret.

Feedback on schema before I write the XRD YAML.

[hamza-mohd]

Schema is clean. Two things:

1. Add deletionPolicy field defaulting to Orphan - losing production RDS on a kubectl delete would be catastrophic
2. Connection secret should have host, port, username, password, dbname as separate keys for apps that expect env vars

[arjunmehta-git]

On the multiAZ default - use a composition patch that reads platform.tcs.io/environment: production label from the claim namespace and forces multiAZ=true. Prevents dev teams accidentally provisioning expensive HA configs.

[winkletinkle]

The subnet group will be created per-claim. If two apps in the same namespace each claim a database, they'll collide on subnet group name. Use a naming convention that includes the claim namespace + name.