AC:

• Use chrome service as an example: https://gitlab.cee.redhat.com/service/app-interface/-/blob/master/data/services/insights/chrome-service/namespaces/chrome-service-stage.yml?ref_type=heads and https://gitlab.cee.redhat.com/service/app-interface/-/blob/master/data/services/insights/chrome-service/deploy.yml?ref_type=heads
• Create a corresponding namespace for each cluster (crcs02ue1, hccs01ue1), specifically see https://gitlab.cee.redhat.com/service/app-interface/-/blob/master/data/services/insights/notifications/namespaces/hccs01ue1-notifications-stage.yml?ref_type=heads and https://gitlab.cee.redhat.com/service/app-interface/-/blob/master/data/services/insights/kessel/namespaces/hccs01ue1-kessel.yml?ref_type=heads for examples on how to define the namespace file for the hccs01ue1 cluster (especially the different environment clause). The namespace file should follow the

  {cluster name}-{service name}.yml
  

  naming convention

• The deploy.yaml will define a deployment target for both stage namespaces
• Be sure all parameters match those expected in https://github.com/RedHatInsights/widget-layout-backend/blob/master/deploy/clowdapp.yaml#L78-L101 
• Be sure to add deploy and namespace files to https://gitlab.cee.redhat.com/service/app-interface/-/blob/master/data/teams/insights/roles/platform-experience.yml?ref_type=heads 
• Should only be for stage deployment
• Verify deployment to stage env

Github repo: https://github.com/RedHatInsights/widget-layout-backend

App-interface onboarding epic: https://issues.redhat.com/browse/APPSRE-12910 (onboarding approval in slack)