Deploy & Patching W17

by ADMIN 22 views

=====================================

Tuesday: Prod-deploy

Deploy updates to APIM production

Before deploying updates to APIM production, we need to check if there have been any updates to the #authorization and #access-management components in the last week. If none of them have been deployed, we can skip the production APIM deploy.

We can check the APIM deploys to TT02 by visiting the APIM deploys to TT02 page. If there have been no updates to either of these components in the last week, we can proceed with the production APIM deploy.

To deploy the updates to APIM production, we need to follow these steps:

  1. Check the APIM deploys to TT02 page for updates to #authorization and #access-management.
  2. If there have been no updates to either of these components in the last week, proceed with the production APIM deploy.
  3. Deploy the updated components to APIM production.

Deploy platform components to production

We also need to deploy all platform components to production. This includes:

  • Authorization
  • Delegation Events
  • Access Management

To deploy these components, we need to follow these steps:

  1. Deploy Authorization to production.
  2. Deploy Delegation Events to production.
  3. Deploy Access Management to production.
  4. Verify that the new pods in cluster 01 and cluster 02 have started without errors.
  5. Verify that the function app deployment has completed successfully.
  6. Grab a coffee and take a break!
  7. Verify that there are no errors reported for the components in the Slack channels #alerts-prod and #alerts-prod-critical.
  8. Post-deploy Authorization and Access Management if everything looks good.
  9. Post-deploy Delegation Events if everything looks good.

Deploy frontend to production

If a new release was made and deployed to TT02 last week, we need to deploy the frontend to production.

To deploy the frontend, we need to follow these steps:

  1. Check the Access Management Frontend Releases page to see if a new release was made last week and deployed to TT02.
  2. If a new release was made and deployed to TT02, deploy the new release to production.
  3. Verify that the new revision of the container app has started without error.

Update the automatic issue template

If any of the above steps or links need correction, we need to update the automatic issue template.

Wednesday: TT02-deploy

Deploy updates to APIM TT02

Before deploying updates to APIM TT02, we need to check if there have been any updates to the #authorization and #access-management components in the last week. If none of them have been deployed, we can skip the TT02 APIM deploy.

We can check the APIM deploys to TT02 by visiting the APIM deploys to TT02. If there have been no updates to either of these components in the last week, we can proceed with the TT02 APIM deploy.

To deploy the updates to APIM TT02, we need to follow these steps:

  1. Check the APIM deploys to TT02 page for updates to #authorization and #access-management.
  2. If there have been no updates to either of these components in the last week, proceed with the TT02 APIM deploy.
  3. Deploy the updated components to APIM TT02.

Deploy platform components to TT02

We also need to deploy all platform components to TT02. This includes:

  • Authorization
  • Delegation Events
  • Access Management

To deploy these components, we need to follow these steps:

  1. Deploy Authorization to TT02.
  2. Deploy Delegation Events to TT02.
  3. Deploy Access Management to TT02.
  4. Verify that the new pods in cluster 01 and cluster 02 have started without errors.
  5. Verify that the function app deployment has completed successfully.
  6. Grab a coffee and take a break!
  7. Verify that there are no errors reported for the components in the Slack channels #alerts-prod and #alerts-prod-critical.
  8. Post-deploy Authorization and Access Management if everything looks good.
  9. Post-deploy Delegation Events if everything looks good.

Deploy frontend to TT02

If a draft release with changes is waiting for deploy, we need to deploy the frontend to TT02.

To deploy the frontend, we need to follow these steps:

  1. Check the Access Management Frontend Releases page to see if a release draft is waiting.
  2. If a release draft is waiting, publish the draft as the next release as v{year}.{releaseNumber}.
  3. Deploy the new release of the Access Management Frontend to TT02.
  4. Verify that the new revision of the container app has started without error.
  5. Verify that the Cypress automated tests have completed successfully.

Update the automatic issue template

If any of the above steps or links need correction, we need to update the automatic issue template.

Thursday: Patching

Go through all github pull-requests from the dependency bots in all repos

We need to go through all github pull-requests from the dependency bots in all repos, including:

  • Authorization
  • Access Management
  • Access Management Frontend

To do this, we need to follow these steps:

  1. Go to the Authorization page.
  2. Go to the Access Management page.
  3. Go to the Access Management Frontend page.

Deployrutine

The deployrutine is as follows:

  • Det som skal deployes til PROD skal ha vært ute i TT02 i en uke.
  • Før man deployer må man sørge for at man ikke introduserer nye feil, så da må man sjekke par steder:

Sjekk Slack-kanalene

Before deploying to production, we need to check the Slack channels #alerts-prod and #alerts-prod-critical to see if there are any errors or issues related to the component that is about to be deployed.

Sjekk failures i portal.azure.com

We also need to check the failures in portal.azure.com to see if there are any errors or issues related to the component that is about to be deployed.

Pre-deploy approval

Before deploying, we need to get approval from the team.

Post-deploy approval

After deploying, we need to get approval from the team.

Sjekk pods i portal.azure.com

After deploying, we need to check the pods in portal.azure.com to see if they have started without errors.

Post-deploy approval

After checking the pods, we need to get approval from the team.

Update the automatic issue template

If any of the above steps or links need correction, we need to update the automatic issue template.

=====================================

Q: What is the deployrutine for deploying to production?

A: The deployrutine is as follows:

  • Det som skal deployes til PROD skal ha vært ute i TT02 i en uke.
  • Før man deployer må man sørge for at man ikke introduserer nye feil, så da må man sjekke par steder:

Q: What are the steps to deploy updates to APIM production?

A: To deploy updates to APIM production, you need to follow these steps:

  1. Check the APIM deploys to TT02 page for updates to #authorization and #access-management.
  2. If there have been no updates to either of these components in the last week, proceed with the production APIM deploy.
  3. Deploy the updated components to APIM production.

Q: What are the steps to deploy platform components to production?

A: To deploy platform components to production, you need to follow these steps:

  1. Deploy Authorization to production.
  2. Deploy Delegation Events to production.
  3. Deploy Access Management to production.
  4. Verify that the new pods in cluster 01 and cluster 02 have started without errors.
  5. Verify that the function app deployment has completed successfully.
  6. Grab a coffee and take a break!
  7. Verify that there are no errors reported for the components in the Slack channels #alerts-prod and #alerts-prod-critical.
  8. Post-deploy Authorization and Access Management if everything looks good.
  9. Post-deploy Delegation Events if everything looks good.

Q: What are the steps to deploy frontend to production?

A: To deploy frontend to production, you need to follow these steps:

  1. Check the Access Management Frontend Releases page to see if a new release was made last week and deployed to TT02.
  2. If a new release was made and deployed to TT02, deploy the new release to production.
  3. Verify that the new revision of the container app has started without error.

Q: What are the steps to deploy updates to APIM TT02?

A: To deploy updates to APIM TT02, you need to follow these steps:

  1. Check the APIM deploys to TT02 page for updates to #authorization and #access-management.
  2. If there have been no updates to either of these components in the last week, proceed with the TT02 APIM deploy.
  3. Deploy the updated components to APIM TT02.

Q: What are the steps to deploy platform components to TT02?

A: To deploy platform components to TT02, you need to follow these steps:

  1. Deploy Authorization to TT02.
  2. Deploy Delegation Events to TT02.
  3. Deploy Access Management to TT02.
  4. Verify that the new pods in cluster 01 and cluster 02 have started without errors.
  5. Verify that the function deployment has completed successfully.
  6. Grab a coffee and take a break!
  7. Verify that there are no errors reported for the components in the Slack channels #alerts-prod and #alerts-prod-critical.
  8. Post-deploy Authorization and Access Management if everything looks good.
  9. Post-deploy Delegation Events if everything looks good.

Q: What are the steps to deploy frontend to TT02?

A: To deploy frontend to TT02, you need to follow these steps:

  1. Check the Access Management Frontend Releases page to see if a release draft is waiting.
  2. If a release draft is waiting, publish the draft as the next release as v{year}.{releaseNumber}.
  3. Deploy the new release of the Access Management Frontend to TT02.
  4. Verify that the new revision of the container app has started without error.
  5. Verify that the Cypress automated tests have completed successfully.

Q: What are the steps to update the automatic issue template?

A: If any of the above steps or links need correction, you need to update the automatic issue template.

Q: What are the steps to go through all github pull-requests from the dependency bots in all repos?

A: To go through all github pull-requests from the dependency bots in all repos, you need to follow these steps:

  1. Go to the Authorization page.
  2. Go to the Access Management page.
  3. Go to the Access Management Frontend page.