Automated commit at Wed Apr 3 20:00:00 CEST 2024

This commit is contained in:
Mischa van den Burg 2024-04-03 20:00:00 +02:00
parent 54a43adb3b
commit c2afe41269
6 changed files with 82 additions and 0 deletions

View File

@ -0,0 +1,12 @@
[[Local Testing of Azure Verified Modules]]
[[Benefits of Azure Verified Modules]]
## Links:
[[An Introduction to Azure Verified Modules (AVM) (youtube.com)]]
202404020954

View File

@ -0,0 +1,29 @@
- modules have an owner within microsoft
- you can raise a support ticket on the modules
- modules are aligned with a unified IaC strategy that's formed within Microsoft
- Aligned with Well Architected Framework
- Currently supports Bicep & Terraform, but may support other tooling in the future as well (Crossplane? Pulumi?)]
- Advantage: IaC setup is multi-lingual by default
- Uses the same paramater interfaces (see following point)
- Some Azure resources have different implementations of configuration. Such as Customer Managed Keys. The Azure Verified Modules create an interface over this that is the same across all modules, so you can use the same parameters and don't have to worry about the different implementations on the ARM side
- [Interfaces | Azure Verified Modules](https://azure.github.io/Azure-Verified-Modules/specs/shared/interfaces/)
Our opinionated way within the company should be to align with the WAF. AVM does this out of the box. **Azure Verified Modules = Well Architected Framework in Code. **
# Security
For the security pillar, the AVM use the Microsoft Cloud Security Benchmark (MCSB) and Microsoft Defender for Cloud (MDFC) to align input parameter/variables.
![[Pasted image 20240402111716.png]]
## Links:
202404031930

8
content/Blueprint.md Normal file
View File

@ -0,0 +1,8 @@
The health protocol conceived of by Bryan Johnson.
## Links:
202404021413

View File

@ -24,6 +24,9 @@
[[Generating TLS certificate for testing on Kubernetes]]
## Certificates
[[Kubernetes users are simply holders of TLS Certificates]]
## Other

View File

@ -0,0 +1,13 @@
Users don't exist in the cluster as a resource. Certificates are generated and a single user will use those certificates to authenticate with the API server.
he cloud provider will handle issuing these certificates when the credentials / kubeconfig is retrieved.
The client certificate will be signed by the cluster CA, and the CN is the username.
![[Pasted image 20240401105713.png]]
## Links:
202404011056

View File

@ -0,0 +1,17 @@
`az deployment sub what-if -f main.test.bicep -l northeurope -p resourceGroupName=mischa-aci-test`
## Generating the Docs
When updating code, the README must be auto generated. This is done with a powershell script.
First you need to dot source it, then run it:
`. Set-AVMModule.ps1`
`Set-AVMModule -ModuleFolderPath ./avm/res/container-instance/container-group/`
## Links:
202404031425