Release 0.3.1 Step 3: Create and Test Release Candidate 0

Description

This issue defines the scope of publishing a release candidate for the purposes of testing. These steps will need to be executed for at least one RC but this issue should be copied and repeated as needed to create additional release candidates as issues are encountered and resolved.

1. Use release-it to tag all EdgeOps repos with a new release candidate name. Naming structure for RC tags is [release-number]-[sequential RC number]. Wait for all pipelines to release new tagged artifacts to the registry1 staging repo.

Usage: npx release-it

For a minor release (0.3.0 - 0.3.1):

• select prepatch (0.3.1-0)
  • yes to tag
  • yes to commit
  • yes to push

For a major release (0.3.0 - 0.4.0):

• select preminor (0.4.0)
  • yes to tag
  • yes to commit
  • yes to push

2. In the edge orchestrator and edge controller Iron Bank repos:
   • Create new RC branches
   • Change STAGED_TAG to [release-number]-[RC#] in hardening_manifest
   • Update tags in hardening_manifest to reflect the RC version, this should be handled by renovates tickets.
   • Create MRs to merge the RC branches to develop and assign to the Iron Bank team
   • Wait for Iron Bank to merge the branch to develop and publish new image tags to Iron Bank
3. If changes have been made to the ISO image, send the new RC image to MITRE to install onto the EOD in the Microlab
4. After MITRE rebuilds the EOD with the new image, validate the EOD state matches expected acceptance criteria:
   • All expected images and versions are staged
   • All expected services are running
   • The babu container starts and bootstraps the KinD cluster successfully using all of the RC versions of artifacts
5. Initiate a deployment from the Microlab EOD to the Microlab EdgeLine. Validate these acceptance criteria pertaining to the deployment:
   • All expected Crossplane objects are created on the EOD cluster
   • All playbooks complete successfully with no errors
   • EdgeLine blades have functional operating systems registered in a Proxmox cluster
   • Expected number and types of VMs have been created in the Proxmox cluster
   • Big Bang deploys fully and successfully on the RKE2 cluster

Acceptance Criteria:

• RC tags created and artifacts published:
  • proxmox-provider
  • edge-operator
  • iso-builder
  • edge-controller
  • edge-orchestrator
  • crossplane-provider
• Iron Bank repos branched, updated and tagged:
  • babu container
  • edge controller container
• Updated ISO (if needed):
  • Image sent to MITRE to install in Microlab (if needed)
  • Microlab EOD rebuilt by MITRE with new image
• Deployment tested from Microlab EOD to Microlab EdgeLine
  • Test outcome is documented in this issue's comments