Productionisation
Prepare these items before the service’s PRP, PRX or PRD deployment steps are scheduled with Crime Release Management. This guide covers CPP CCM AKS services deployed through Helmsman or Flux.
Fix the deployment versions and route
Record the container image repository and versioned tag, chart version and configuration commit or release branch for each target environment. Confirm the selected image and chart are available in the registry used by that environment. Publishing to non-live alone does not establish availability in live.
For Helmsman, record the release branches from cpp-aks-deploy and cpp.pipeline and the approved parameters for cpp-aks-deploy. For Flux, record the configuration commit, target cluster/stack Kustomization, HelmRelease and image-tag substitution or override.
Use the Path to Live deployment instructions for the CCM deployment. The approved release note supplies the actual branches, stack and pipeline options.
Prepare production dependencies
For Helmsman, check the common service values under ansible/group_vars, then the overrides under prp, prx or prd and that environment’s stack directory. The file pattern is <service>_values.yaml.j2; environment and stack values override the common values.
For Flux, check the service’s apps/base/services HelmRelease, apps/environments patch, apps/overlays/stacks overrides and target cluster’s flux-cluster-vars.yaml / apps.yaml in cpp-flux-config. Confirm these settings for each environment in the release:
- required databases, schema migrations and application permissions
- the secret references, runtime identities and access grants the service uses
- the hostname, gateway route, TLS configuration and authentication required by its callers
- any outbound firewall rules or third-party IP allow-list entries
- resource requests, limits, replica and autoscaling settings, and the service’s health probes
The infrastructure and connectivity guide identifies the CPP provisioning repositories and secret mechanisms. Use CPP egress guidance for an outbound allow-list and monitoring and health for the probe settings.
For persistent data, record the backup settings, restore procedure and data-recovery owner. Keep database migration and rollback steps with the application release instructions. A previous application image is not a database rollback plan.
Complete the release instructions
Use the CPP release-note template with Crime Release Management. Raise a separate Halo RFC for each of PRP, PRX and PRD being changed, link each RFC to that environment’s steps and obtain its approval before implementation. Record:
- implementation steps, their order and the person responsible for each step
- the tests and expected results after deployment in each environment
- the need for shuttering, the services affected and the restoration steps
- the Dynatrace maintenance window and the monitoring checks after deployment
- the failure conditions that stop the release, the decision owner and the exact rollback steps
Provide the evidence from operational acceptance and release testing. Follow the release’s recorded stop and rollback conditions during implementation; any change to the plan must be coordinated with the release manager.