Payments release workspace
The platform owner at fictional Cedar Payments requests a release workspace for an internal settlement preview. Use only the fictional configuration supplied in the tasks. Deliver a namespace, settings, credentials, a two-replica Deployment, a ClusterIP Service and an Ingress. Retain all earlier resources.
A payments release needs a complete application boundary, not just one running Pod. You'll create its namespace, separate ordinary settings from fictional credentials, deploy a controller-managed application and connect its Service and HTTP route. Each step continues from the previous result and keeps the object identities stable. The final Ingress declares a route; a production environment would also need an installed controller, working DNS and its normal release review. This local project checks the resources and references rather than claiming to provision those external systems. Follow configuration names through the Pod template before exposing traffic, because a missing reference can prevent the application from starting.
kubectl create namespace settlement-east-team
A worked first action on this original project fixture.