document update paths and rate of hypershift updates #101
Conversation
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: cdoan1 The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
Kudos, SonarCloud Quality Gate passed!
|
| @@ -0,0 +1,35 @@ | |||
| # Updating Hypershift | |||
|
|
|||
| The ACM is packaged as an OCM Addon and deploy to the service cluster with fleet manager. | |||
There was a problem hiding this comment.
The ACM is packaged as an OCM Addon and deployed to the service cluster with fleet manager.
|
|
||
| The ACM is packaged as an OCM Addon and deploy to the service cluster with fleet manager. | ||
|
|
||
| ACM includes the multicluster engine operator (MCE) which is the component that really packages the hypershift operator and it's related images. ACM provides the policy functionality, and MCE provides all the cluster lifecycle functionality. |
There was a problem hiding this comment.
ACM includes the multicluster engine (MCE) which is the operator that provides the hypershift operator, the cluster lifecycle functionalities. ACM additionally provides the policy and governance functionalities.
|
|
||
| 2. Create a new ACM OCM Addon version | ||
|
|
||
| We build the ACM/MCE every 12 hours. Not all these builds pass bvt/svt. When they do, they can be promoted to OCM Addon. Currently, fleet manager deploys from our `beta` channel into `integration` and `staging`. The promotion is gated by approvals to MR against managed-tenant-bundles and managed-tenant. |
There was a problem hiding this comment.
ACM is built twice daily and when the build passes BVT and SVT, the can be packaged and promoted to OCM Addon beta channel. The promotion is gated by approvals to MR against managed-tenant-bundles and managed-tenant and upon approval, the ACM addon is deployed into the integration and staging environments.
|
|
||
| We build the ACM/MCE every 12 hours. Not all these builds pass bvt/svt. When they do, they can be promoted to OCM Addon. Currently, fleet manager deploys from our `beta` channel into `integration` and `staging`. The promotion is gated by approvals to MR against managed-tenant-bundles and managed-tenant. | ||
|
|
||
| * Right now, the rate of new ACM OCM Addon is on demand and manually, triggered when there is features that we need to make available to SD. This is basically the standard MT Addon update flow to the two MT repos. We have automation to create the MR for approval, just have to tweak. |
There was a problem hiding this comment.
Currently a new version of ACM OCM Addon is built manually and on demand when there are features or bug fixes for SD. This is the standard MT Addon update flow to the two MT repos. There is automation to create the MR for approval but some tweak is required.
|
|
||
| * Right now, the rate of new ACM OCM Addon is on demand and manually, triggered when there is features that we need to make available to SD. This is basically the standard MT Addon update flow to the two MT repos. We have automation to create the MR for approval, just have to tweak. | ||
|
|
||
| * The rate that each build of ACM/MCE pulls in a newer version of hypershift is also manual right now. Updates are through a MR to update a manifest of image SHA. We can automate this, just have not had the need yet. https://github.com/stolostron/backplane-pipeline/blob/2.2-integration/manifest.json#L243-L250 |
Description of the change(s):
Why do we need this PR:
Issue reference:
Test API/Unit - Success