Skip to content

Self-Service Container Deployment

Important

This guide applies only to the legacy App Central user interface. If you are using the new App Central design, refer to the Deploy images to STG and PRD environments section instead.

You can deploy approved container images to Staging (STG) and Production (PRD) directly from Game Warden. An image is considered approved when it has no unresolved Common Vulnerabilities and Exposures (CVEs) or when all findings have been remediated or formally risk-accepted with approved justifications.

Deploy Images

Warning

This procedure applies to deployments for simple container updates. For deployment requests beyond simple container updates (i.e. new variables, running scripts, etc), submit a support ticket in lieu of this procedure.

Prerequisites

  • Only users with the Customer Admin role can deploy images to STG and PRD environments. To request a permission update, submit a Support Ticket through the Game Warden app.

  • For the Deploy to staging button to be enabled, your container needs to be run through the Game Warden pipeline to include hardening and scanning. Any security findings surfaced by the Game Warden pipeline scanning tools must be remediated and approved by our security team. Once your container has cleared these gates, this button will turn blue and you can deploy your container to Game Warden’s staging environment.

  • For the Deploy to production button to be enabled, your container must meet the above requirements and be deployed to the staging environment.

  • If either deployment button is disabled (gray out), you can hover over the button for clarifying information.

Important

If neither deployment button is enabled and you see N/A, this means your container has not yet run through the Game Warden pipeline and has no scan results, and therefore cannot be approved for deployment yet. If this indication is unexpected, file a support ticket from the Game Warden app.

Deploying to STG or PRD

Start the deployment

Click Deploy to staging or Deploy to production for the target component.

Deployment initializing

A notification confirms the job has started. While it’s running, the button is disabled (gray out). Deployments typically take a few minutes. You can hover the gray button to see current status.

Check the result

  • On success, the hover message will indicate completion.
  • On failure, file a support ticket and include the component name, environment (STG/PRD), and timestamp.

Verify your app

Visit your application to validate its health and functionality.

FAQs

How do I deploy my app to additional Impact Levels (ILs)?

After your app is in PRD at a given IL, deploying to another IL requires:

Once your Deployment Passport is returned with the Authorizing Official’s signature, push to STG at the target IL for validation. After successful validation, you may push to PRD.

Do I need to move through lower ILs to reach my target IL?

No. If Game Warden holds the Authority to Operate (ATO) for your target IL, you can deploy directly to that IL’s Production—provided you meet all Game Warden requirements.

What’s the process to deploy to IL5 if I’m already at IL4?

Game Warden provisions the IL5 environments. You will complete an IL5 BoE and validate app functionality in IL5 STG.

Game Warden will then generate an IL5 Deployment Passport, brief the ISSM, and obtain signature. After approval, we deploy your app to IL5 PRD.

Note

You do not need to deploy to IL4 before IL5; many customers serve end users at different ILs.

If I run at IL4 and also want IL2, do I need separate STG/PRD environments?

Yes. IL2 and IL4 require separate STG and PRD environments to run side-by-side.