Before the service can be deployed, there are numerous dependencies and configuration files that must be defined for both in-cluster use and in App Interface to facilitate the full deployment and lifecycle of the service.

Note that FedRAMP has its own App Interface separate from commercial, as well as some other services like Vault, and requires FedRAMP Access.

Done Criteria

• Ensure all resources/dependencies needed to run the service are added to the namespace file in App Interface (namespace file may need to be created first as well)
• Ensure any secrets needed are added to the FedRAMP Vault and defined in the App interface
• Configure any network policies to reach other namespaces needed
• We should model our file structure and definitions to match commercial as best as possible to simplify processes
• Prod cannot be deployed without FedRAMP approval via the Annual Assessment and proper change management