Skip to content

updates for ci-prod release instructions #619

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
ganga1980 merged 2 commits into from
Aug 13, 2021
Merged

updates for ci-prod release instructions #619

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
0e9a5d7
updates for ci-prod release instructions
ganga1980 Aug 3, 2021
68ea507
Merge branch 'ci_dev' into gangams/ciprod-release-deployment-instruct…
ganga1980 Aug 13, 2021
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 4 additions & 6 deletions ReleaseProcess.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -13,14 +13,12 @@ Here are the high-level instructions to get the CIPROD`<MM><DD><YYYY>` image for
2. Make PR to ci_dev branch and once the PR approved, merge the changes to ci_dev
3. Latest bits of ci_dev automatically deployed to CIDEV cluster in build subscription so just validated E2E to make sure everthing works
4. If everything validated in DEV, make merge PR from ci_dev and ci_prod and merge once this reviewed by dev team
6. Update following pipeline variables under ReleaseCandiate with version of chart and image tag
- CIHELMCHARTVERSION <VersionValue> # For example, 2.7.4
- CIImageTagSuffix <ImageTag> # ciprod08072020 or ciprod08072020-1 etc.
7. Merge ci_dev and ci_prod branch which will trigger automatic deployment of latest bits to CIPROD cluster with CIPROD`<MM><DD><YYYY>` image to test and scale cluters, AKS, AKS-Engine
> Note: production image automatically pushed to CIPROD Public cloud ACR which will inturn replicated to Public cloud MCR.
5. Once the PR to ci_prod approved, please go-ahead and merge, and wait for ci_prod build successfully completed
6. Once the merged PR build successfully completed, update the value of AGENT_IMAGE_TAG_SUFFIX pipeline variable by editing the Release [ci-prod-release](https://github-private.visualstudio.com/microsoft/_release?_a=releases&view=mine&definitionId=38)
> Note - value format of AGENT_IMAGE_TAG_SUFFIX pipeline should be in `<MM><DD><YYYY>` for our releases
7. Create a release by selecting the targetted build version of the _docker-provider_Official-ci_prod release
8. Validate all the scenarios against clusters in build subscription and scale clusters


# 2. Perf and scale testing

Deploy latest omsagent yaml with release candidate agent image in to supported k8s versions and validate all the critical scenarios. In perticular, throughly validate the updates going as part of this release and also make sure no regressions. If this passes, deploy onto scale cluster and validate perf and scale aspects. Scale cluster in AME cloud and co-ordinate with agent team who has access to this cluster to deploy the release candiate onto this cluster.
Expand Down