Production Deployment

Production deployment, by default once a day, takes the latest version that has passed extended test and deploys it to production.

Implement the following Make targets:

Usage

If you’ve created your application with corectl from a software template the following workflow will be already configured.

name: Prod

on:
  workflow_dispatch:
  schedule:
    - cron: '35 5 * * 1,5'

permissions:
  contents: read
  id-token: write

jobs:
  get-latest-version:
    uses: coreeng/p2p/.github/workflows/p2p-get-latest-image-prod.yaml@v1
    with:
      image-name: knowledge-platform

  prod:
    needs: [get-latest-version]
    uses: coreeng/p2p/.github/workflows/p2p-workflow-prod.yaml@v1
    with:
      version: ${{ needs.get-latest-version.outputs.version }}

This task will get the latest version that’s on the prod registry and execute the prod deployment task.

Subsections of Production Deployment

Prod Deploy

The purpose of P2P prod is to

  • Deploy to production

Deploy Application

Deploy to the following namespace

<app_name>-prod

Or if you have multiple apps in the same tenancy

<tenant>-<app-name>-prod