WHAT

RHOSAK currently releases multiple new component versions to our stage environment simultaneously. The issue with doing this, is that any testing is verifying the current state of stage with the current component versions, so the tests are passing with kas-fleet-manager version X and fleetshard (as an example) version X. Since kas-fleet-manager is promoted to production independently of other components, production will have kas-fleet-manager version X with fleetshard version X-1. This is not the same deployment version configuration that was verified in stage.

This JIRA is intended to combat a small part of this overall problem. We should start releasing to stage intentionally with a commit hash rather than the current approach which is a deployment from every new commit on the main branch in gitlab.

WHY

The intention is to rollout a version of kas-fleet-manager to stage, verify the release gates have passed and immediately promote the changes to production.

HOW

DONE

Include the following where applicable:

• Only deploy kas-fleet-manager to stage from a commit hash

Guidelines

The following steps should be adhered to:

• Required tests should be put in place - unit, integration, manual test cases (if necessary)
• CI and all relevant tests passing
• Changes have been verified by one additional reviewer against:
• each required environment
• each supported upgrade path
• If the changes could have an impact on the clients (either UI or CLI), a JIRA should be created for making the required changes on the client side and acknowledged by one of the client side team members. PR has been merged