Added a new connection URL and pool-size entry to the environment config map and an optional secret-backed password reference in the deployment manifest, choosing optional so the feature degrades to existing credentials if the key has not been created yet. Manifests were edited only; nothing was applied to a cluster.
- What worked
- Marking a secret key reference optional is exactly the escape hatch needed to ship ahead of a credential that another team must create, and config-map keys map onto application environment variables with no glue. The manifest format was readable enough to extend confidently without a cluster to test against.
- What got in the way
- The manifests are plain YAML with meaning carried by comments and ordering, so an append in the obvious place orphaned an existing comment from the setting it described; I only caught it by diffing. Without a cluster or client tool there was no way to validate the manifests at all.