VNET peering and DNS Records #1054
Labels
kind/chore
Non functional, often repeating tasks.
kind/toil
Issue/task that brings no real value to the end user. Can it be automated?
status/triage
Issue needs a triage from one of the codeowners
Hællæ Platform,
We are deploying new shared infrastructure for authorization to enable the updated implementation of the register component. While the register will continue running on the platform's AKS, it will need access to Azure resources managed by the Authorization team (specifically, the Database server, Service Bus, and Key Vault).
Since the public endpoint for the register's database is disabled, we propose peering the Authorization VNET and Platform VNET. The CIDR block in use is
10.202.0.0/20
.For your reference, here is the link to the VNET in question: Authorization VNET in Azure
Additionally, we request that the following domains point to IP address
4.235.120.208
api.auth.at22.altinn.cloud
auth.at22.altinn.cloud
In addtion, it seems like Jon Kjetil or Rune Larsen are not admins Owners in Altinn Products Authorization : Dev / Prod
Best regards,
Andreas ❤️
The text was updated successfully, but these errors were encountered: