Azure / Azure/azure-rest-api-specs

Bicep config for AKS addonProfiles

Open
#17,563 4 comments 5 reactions 0 assignees View on GitHub
AKS Service Attention
Dominant language
TypeSpec
Stars
3.1k
Forks
5.9k
Avg merge
2d 22h
Merged PRs (30d)
444

Description

I have look the in [Bicep doc for AKS](https://docs.microsoft.com/en-us/azure/templates/microsoft.containerservice/managedclusters?tabs=bicep) but there no details about the addonProfiles configuration in Bicep, it is difficult for a newbie to configutre it correctly, for instance :

```sh
addonProfiles: {
omsagent: {
config: {
logAnalyticsWorkspaceResourceID: logAnalyticsWorkspaceId
}
enabled: true
}
azurepolicy: {
enabled: true
}
// ingress-appgw ?
ingressApplicationGateway:{
enabled:true
config:{
applicationGatewayId: stg.properties.accessTier
}
}
virtual-node {
// What to configure here ?
}
openServiceMesh: {
enabled: true
config: {}
}
gitops {
// What to configure here ?
}
azure-keyvault-secrets-provider {
// What to configure here ?
}

}
```

Contributor guide

Open the contributing guide

Research direction

Start with the linked AKS Bicep documentation and the addonProfiles example in the issue. Identify the supported addon names and configuration fields, then document their Bicep shapes and examples so a newcomer can configure each listed addon correctly.

Written by the indexing model from the issue text.

Assessment

Tech stack
azure
Domain
cloud, documentation
Issue type
Documentation
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.