Back to Azure Resource templates index <–
Azure Linux Container Instances basic deployment with public end point.
Template Locations
Infrastructure As Code Advisor (Beta)
WAF-compliance
The WAF-compliance advisor validates templates based on the Well Architected Framework practices. Every day a GitHub Action updates the templates compliance data and lists the recomendations.
Sustainbility Advisor
The sustainability advisor is based on the Sogeti Cloud Reference Architecture with sustainble practices. These sustainble practices cover application code, cloud infrastructures and data. The global Sogeti community is continously evolving the sustainble practices and every day new and tuned are added. For cloud infrastructures the sustainble practices are automatically validated and reported below.
note: when 100% it can be that there is no sustainble practices yet for this Cloud infrastructure.
Online documentation
Template reference
Service description
Related Azure Resources
| Resource | Description | Automation |
|---|---|---|
| Azure Container Registry | Azure Container Registry, a private registry for hosting container images. Store Docker-formatted images for all types of container deployments. | ARM |
Related Pipelines
| Resource | Description | Type |
|---|---|---|
| Azure Container Instance release pipeline | Deploy an Azure Container Instance. |
Used by Landing zone(s)
| Landing zone name |
|---|
| AKS Landing zone by Sogeti community |
Requirements
- Resource group must been created with a valid name and location.
Input values
- tagBillingIdentifier: Cost Center.
- image:Container image to deploy. Should be of the form accountName/imagename:tag for images stored in Docker Hub or a fully qualified URI for a private registry like the Azure Container Registry.
- port:Port to open on the container and the public IP address.
- cpuCores:The number of CPU cores to allocate to the container. Must be an integer.
- memoryInGb:The amount of memory to allocate to the container in gigabytes.
Output values
- containerIPv4Address
- containerPrincipalId
Additional information
containerPrincipalId can be used to give access to a Key Vault.
Compliance Advisor details
Resource Health Result
| Message | ResourceType | Severity |
|---|---|---|
| Location for the resource should not be hardcoded, it should be parameterized and should refer from Resource Group's location i.e. [resourceGroup().location] | Microsoft.ContainerInstance/containerGroups | 2 |
| Your current API Version i.e.2018-10-01 for the resource Microsoft.ContainerInstance/containerGroups is outdatedconsider updating to new recent version available i.e. 2023-05-15-preview or 2023-05-01 | Microsoft.ContainerInstance/containerGroups | 2 |
| To help other contributors understand the purpose of the resource, specify comments for each resource in the template | Microsoft.ContainerInstance/containerGroups | 1 |
| It is recommended to parameterized your tag and make it as object type | Microsoft.ContainerInstance/containerGroups | 1 |
TemplateParameterHealthResult
| Message | Severity |
|---|---|
| Define default values for parameters that aren't sensitive. By specifying a default value, it's easier to deploy the template, and users of your template see an example of an appropriate value i.e. tagBillingIdentifierRead More | 1 |
| It is recommended to make your parameter as camel case, wherever possible for i.e. acicustomnameRead More | 1 |
| Define default values for parameters that aren't sensitive. By specifying a default value, it's easier to deploy the template, and users of your template see an example of an appropriate value i.e. acicustomnameRead More | 1 |
| It is recommended to make your parameter as camel case, wherever possible for i.e. imageRead More | 1 |
| It is recommended to make your parameter as camel case, wherever possible for i.e. portRead More | 1 |
| It is recommended to add description for your parameters i.e. for dnsLabelRead More | 1 |
| Define default values for parameters that aren't sensitive. By specifying a default value, it's easier to deploy the template, and users of your template see an example of an appropriate value i.e. dnsLabelRead More | 1 |
| It is recommended to add description for your parameters i.e. for imageRegistryUsernameRead More | 1 |
| Define default values for parameters that aren't sensitive. By specifying a default value, it's easier to deploy the template, and users of your template see an example of an appropriate value i.e. imageRegistryUsernameRead More | 1 |
| It is recommended to add description for your parameters i.e. for imageRegistryPasswordRead More | 1 |
| Define default values for parameters that aren't sensitive. By specifying a default value, it's easier to deploy the template, and users of your template see an example of an appropriate value i.e. environmentVarNameRead More | 1 |
| Define default values for parameters that aren't sensitive. By specifying a default value, it's easier to deploy the template, and users of your template see an example of an appropriate value i.e. environmentVarValueRead More | 1 |
TemplateVariableHealthResult
| Message | Severity |
|---|---|
| It is recommended to make your variable as camel case, wherever possible for e.g. environmentRead More | 1 |
| It is recommended to make your variable as camel case, wherever possible for e.g. locationRead More | 1 |
TemplateOthersHealthResult
| Message | Severity |
|---|---|
| Current schema version is not valid, Please change the version year to 2019-04-01 or greater | 2 |