Adding a New Product

Create namespaces/<bu>/<product>/product.yaml:

Multiple namespaces can be declared in the same product.yaml file, but each namespace must have a unique name. The namespace key must match the namespace declared in the values file for any service deployments.

Access to the cluster and namespaces is determined by the access section of the product.yaml file. The group key must match a group in the cluster’s RBAC configuration, and the role key must be one of the following: view, edit, or admin. The clusters key is a list of clusters where the access applies.

Example product.yaml:

product: my-product
bu: octo
owner:
  team: my-team
  slack: "#my-team-channel"
  source: https://github.com/ministryofjustice/container-platform-environments

environments:
  - name: dev
    cluster: container-platform-octo-nonlive
    namespace: my-product-dev
    is_production: false
  - name: prod
    cluster: container-platform-octo-live
    namespace: my-product-prod
    is_production: true

access:
  - group: my-team
    role: edit
    clusters:
      - container-platform-octo-nonlive
      - container-platform-octo-live

Merge to main. The baseline ApplicationSet picks it up and creates namespaces, NetworkPolicies, and RoleBindings automatically.

This page was last reviewed on 4 August 2026. It needs to be reviewed again on 4 February 2027 by the page owner #cloud-platform-notify .