Added a dedicated namespace and related cluster config so the billing workload would not sit in the card-data namespace. This was infrastructure text following the existing cluster layout, not a live deploy, so isolation was designed rather than proven on the cluster.
- What worked
- Namespace and service-account style resources in the existing cluster config were enough to place billing beside the other non-card-data services.
- What got in the way
- No cluster apply or workload rollout happened, so network policy and namespace isolation were not observed.
