Deploy Updates to APIM Production

Oct 13, 2025 by magicalceylontours.com 135 views

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

Tuesday: Prod-deploy

Deploying updates to the production environment is a crucial step in ensuring the stability and security of the Altinn platform. On Tuesdays, we focus on deploying updates to APIM production, platform components, and the frontend.

Deploy Updates to APIM Production

Before deploying updates to APIM production, we need to check if any updates have been made to the #authorization and #access-management components in the past week. If no updates have been made, we can skip deploying to APIM production.

- [ ] Deploy updates to APIM production (if updated since last deploy)
  - [ ] Check [APIM deploys to TT02](https://dev.azure.com/brreg/altinn-studio-ops/_build?definitionId=125) for updates to `#authorization` and `#access-management`. If none of them have been deployed the last week, no production APIM deploy is needed.
  - [ ] Deploy products with changes [to APIM production](https://dev.azure.com/brreg/altinn-studio-ops/_build?definitionId=128).

Deploy Platform Components

We need to deploy the following platform components to production:

Authorization
Delegation Events
Access Management

- [ ] Deploy[^1] all platform components to production[^2].
  - [ ] Deploy [Authorization] to production.
  - [ ] Deploy [Delegation Events] to production.
  - [ ] Deploy [Access Management] to production.

Verify Deployments

After deploying the platform components, we need to verify that they have started without errors. We can do this by checking the cluster 01 new pods and cluster 02 new pods in the Azure portal.

- [ ] Verify [cluster 01 new pods](https://portal.azure.com/#@ai-dev.no/resource/subscriptions/1ab2d164-1861-4ff8-be8c-069c3ee3b70a/resourceGroups/altinnplatform-prod-rg/providers/Microsoft.ContainerService/managedClusters/platform-prod-01-aks/workloads) or [cluster 02 new pods](https://portal.azure.com/#@ai-dev.no/resource/subscriptions/1ab2d164-1861-4ff8-be8c-069c3ee3b70a/resourceGroups/altinnplatform-prod-rg/providers/Microsoft.ContainerService/managedClusters/platform-prod-02-aks/workloads) startup without errors.

Verify Function App Deployment

We also need to verify that the function app deployment has started without errors.

- [ ] Verify [function app deployment](https://portal.azure.com/#@ai-dev.no/resource/subscriptions/1ab2d164-1861-4ff8-be8c-069c3ee3b70a/resourceGroups/altinnplatform-prod-rg/providers/Microsoft.Web/sites/altinn-prod-delegation-func/appServices).

Verify No Errors Reported

We need to verify that no errors have been reported for the components in the Slack channels #alerts-prod and #alerts-prod-critical.

- [ ] Verify no errors reported for the components in Slack channels [#alerts-prod](https://altinndevops.slack.com/archives/C014H7WPSUB) or [#alerts-prod-critical](https://altinndevops.slack.com/archives/C012108PYBV).

Post-Deploy Approval

After verifying that the deployments have started without errors, we need to approve the post-deployment.

- [ ] Post-deploy [Authorization] and [Access Management] if everything looks good.
  - [ ] Post-deploy [Delegation Events] if everything looks good.

Wednesday: TT02-deploy

On Wednesdays, we focus on deploying updates to the TT02 environment. We need to deploy updates to APIM TT02, platform components, and the frontend.

Deploy Updates to APIM TT02

Before deploying updates to APIM TT02, we need to check if any updates have been made to the #authorization and #access-management components in the past week. If no updates have been made, we can skip deploying to APIM TT02.

- [ ] Deploy updates to APIM TT02 (if updated since last deploy)
  - [ ] Check [APIM deploys to AT](https://dev.azure.com/brreg/altinn-studio-ops/_build?definitionId=124) for updates to `#authorization` and `#access-management`. If none of them have been deployed the last week, no TT02 APIM deploy is needed.
  - [ ] Deploy products with changes [to TT02 APIM](https://dev.azure.com/brreg/altinn-studio-ops/_build?definitionId=125).

Deploy Platform Components

We need to deploy the following platform components to TT02:

Authorization
Delegation Events
Access Management

- [ ] Deploy[^1] all platform components to TT02[^3].
  - [ ] Deploy [Authorization] to TT02.
  - [ ] Deploy [Delegation Events] to TT02.
  - [ ] Deploy [Access Management] to TT02.

Verify Deployments

After deploying the platform components, we need to verify that they have started without errors. We can do this by checking the cluster 01 new pods and cluster 02 new pods in the Azure portal.

- [ ] Verify [cluster 01 new pods](https://portal.azure.com/#@ai-dev.no/resource/subscriptions/dd6d3e08-a70f-4f71-8847-781ddc5d8468/resourceGroups/altinnplatform-tt02-rg/providers/Microsoft.ContainerService/managedClusters/platform-tt02-01-aks/workloads) or [cluster 02 new pods](https://portal.azure.com/#@ai-dev.no/resource/subscriptions/dd6d3e08-a70f-4f71-8847-781ddc5d8468/resourceGroups/altinnplatform-tt02-rg/providers/Microsoft.ContainerService/managedClusters/platform-tt02-02-aks/workloads) startup without errors.

Verify Function App Deployment

We also need to verify that the function app deployment has started without errors.

- [ ] Verify [function app deployment](https://portal.azure.com/#@ai-dev.no/resource/subscriptions/dd6d3e08-a70f-4f71-8847-781ddc5d8468/resourceGroups/altinnplatform-tt02-rg/providers/Microsoft.Web/sites/altinn-tt02-delegation-func/appServices).

Verify Automated Tests

We need to verify that the automated tests for Authorization and Access Management have passed.

- [ ] Verify [Authorization K6 automated test](https://dev.azure.com/brreg/altinn-studio/_build?definitionId=414) results.
  - [ ] Verify [Authorization Bruno automated test](https://dev.azure.com/brreg/altinn-studio/_build?definitionId=480) results.
  - [ ] Verify [Access Management K6 automated test](https://dev.azure.com/brreg/altinn-studio/_build?definitionId=412) results.
  - [ ] Verify [Access Management Bruno automated test](https://dev.azure.com/brreg/altinn-studio/_build?definitionId=475) results.

Verify No Errors Reported

We need to verify that no errors have been reported for the components in the Slack channels #alerts-prod and #alerts-prod-critical.

- [ ] Verify no errors reported for the components in Slack channels [#alerts-prod](https://altinndevops.slack.com/archives/C014H7WPSUB) or [#alerts-prod-critical](https://altinndevops.slack.com/archives/C012108PYBV) (Yes, TT02 alerts also goes here).

Post-Deploy Approval

After verifying that the deployments have started without errors, we need to approve the post-deployment.

- [ ] Post-deploy [Authorization] and [Access Management] if everything looks good.
  - [ ] Post-deploy [Delegation Events] if everything looks good.

Thursday: Patching

On Thursdays, we focus on patching the dependencies in the Altinn platform. We need to go through all the GitHub pull requests from the dependency bots in all the repositories.

Go Through GitHub Pull Requests

We need to go through the following repositories and check for any pull requests from the dependency bots:

Authorization
Access Management
Access Management Frontend

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

- [ ] [Authorization](https://github.com/Altinn/altinn-authorization/pulls)
- [ ] [Access Management](https://github.com/Altinn/altinn-access-management/pulls)
- [ ] [Access Management Frontend](https://github.com/Altinn/altinn-access-managment-frontend/pulls)

Deploy Routine

The deploy routine for the Altinn platform is as follows:

Deploy updates to APIM production on Tuesdays
Deploy updates to APIM TT02 on Wednesdays
Deploy platform components to production on Tuesdays
Deploy platform components to TT02 on Wednesdays
Deploy frontend to production on Tuesdays
Deploy frontend to TT02 on Wednesdays
Patch

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

Q: What is the deploy routine for the Altinn platform?

A: The deploy routine for the Altinn platform is as follows:

Deploy updates to APIM production on Tuesdays
Deploy updates to APIM TT02 on Wednesdays
Deploy platform components to production on Tuesdays
Deploy platform components to TT02 on Wednesdays
Deploy frontend to production on Tuesdays
Deploy frontend to TT02 on Wednesdays
Patch dependencies on Thursdays

Q: What is the purpose of deploying updates to APIM production and TT02?

A: Deploying updates to APIM production and TT02 ensures that the Altinn platform is up-to-date with the latest features and security patches. This helps to prevent vulnerabilities and ensures that the platform is stable and secure.

Q: What are the platform components that need to be deployed?

A: The platform components that need to be deployed are:

Authorization
Delegation Events
Access Management

Q: What is the purpose of verifying deployments?

A: Verifying deployments ensures that the platform components have started without errors and are functioning as expected. This helps to prevent downtime and ensures that the platform is stable and secure.

Q: What is the purpose of verifying automated tests?

A: Verifying automated tests ensures that the platform components are functioning as expected and that there are no errors or bugs. This helps to prevent downtime and ensures that the platform is stable and secure.

Q: What is the purpose of patching dependencies?

A: Patching dependencies ensures that the Altinn platform is up-to-date with the latest security patches and features. This helps to prevent vulnerabilities and ensures that the platform is stable and secure.

Q: Who is responsible for deploying updates to APIM production and TT02?

A: The deployment team is responsible for deploying updates to APIM production and TT02.

Q: Who is responsible for verifying deployments and automated tests?

A: The deployment team is responsible for verifying deployments and automated tests.

Q: Who is responsible for patching dependencies?

A: The deployment team is responsible for patching dependencies.

Q: What are the benefits of following the deploy routine?

A: The benefits of following the deploy routine include:

Ensuring that the Altinn platform is up-to-date with the latest features and security patches
Preventing downtime and ensuring that the platform is stable and secure
Ensuring that the platform components are functioning as expected
Preventing vulnerabilities and ensuring that the platform is stable and secure

Q: What are the consequences of not following the deploy routine?

A: The consequences of not following the deploy routine include:

Downtime and instability of the platform
Vulnerabilities and security risks
Errors and bugs in the platform components
Inability to deploy updates and patches

Q: How often should the deploy routine be followed?

A: The deploy routine should be followed on a regular basis, typically on Tuesdays and Wednesdays for deploying updates to APIM production and TT02, and on Thursdays for patching dependencies.

Q: What are the best practices for following the deploy routine?

A: The best practices for following the deploy routine include:

Following the deploy routine on a regular basis
Verifying deployments and automated tests
Patching dependencies regularly
Ensuring that the platform components are functioning as expected
Preventing downtime and ensuring that the platform is stable and secure