Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Added Deploy to Azure buttons for the Samples #593

Merged
merged 1 commit into from
Jun 2, 2023
Merged

Added Deploy to Azure buttons for the Samples #593

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
16 changes: 8 additions & 8 deletions samples/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -2,11 +2,11 @@

These samples demonstrate relevant Bicep patterns and show how to best consume the bicep modules from this project in your own deployments.

Filename | Description
-------- | -----------
[SampleAppMain.bicep](SampleAppMain.bicep) | When consuming the AKS Construction Bicep as a module, doing so from your own Bicep file is recommended. This sample shows using `environment mapping`, `custom naming` and basic conditional logic for using the module.
[SystemPresetExample.bicep](SystemPresetExample.bicep) | The AKS Construction Bicep uses preset configurations for the system pool. Where you wish to deviate from these recommended presets, you can provide your own custom preset. This sample shows how to achieve that.
[Multi-Cluster with Peered vNets](peered-vnet/main.bicep) | When more control is required on the Networking and Resource Groups, you can deploy at the subscription scope.
[Shared ACR](shared-acr/main.bicep) | Where an existing Azure Container Registry exists in a different resource group, this sample shows how to create the scoped 'ACR Pull' role assignment that the AKS cluster requires.
[NetworkForByo.bicep](networkforbyo.bicep) | When using the BYO network configuration you'll usually be deploying to a subscription with a peered virtual network already deployed with the correct subnets. This bicep file bridges the gap where you don't yet have that virtual network, but want to BYO network.
[Deployment Stages](deploy-stages/README.md) | Creating a staged deployment with an existing Managed Identity, Network Subnet and ACR, this configuration demonstrates how to pass the BYO Identity into AKS-Construction for Azure Subscriptions with restricted RBAC.
Filename | Description | Deploy
-------- | ----------- | -----------
[SampleAppMain.bicep](SampleAppMain.bicep) | When consuming the AKS Construction Bicep as a module, doing so from your own Bicep file is recommended. This sample shows using `environment mapping`, `custom naming` and basic conditional logic for using the module. | [![Deploy to Azure](https://aka.ms/deploytoazurebutton)](https://portal.azure.com/#create/Microsoft.Template/uri/https%3A%2F%2Fraw.git.ttaallkk.top%2Foliverlabs%2FAKS-Construction%2Foliver%2Fportal-deploy%2Fsamples%2FSampleAppMain.json) _(via Azure portal UI)_
[SystemPresetExample.bicep](SystemPresetExample.bicep) | The AKS Construction Bicep uses preset configurations for the system pool. Where you wish to deviate from these recommended presets, you can provide your own custom preset. This sample shows how to achieve that. | [![Deploy to Azure](https://aka.ms/deploytoazurebutton)](https://portal.azure.com/#create/Microsoft.Template/uri/https%3A%2F%2Fraw.git.ttaallkk.top%2Foliverlabs%2FAKS-Construction%2Foliver%2Fportal-deploy%2Fsamples%2FSystemPresetExample.json) _(via Azure portal UI)_
[Multi-Cluster with Peered vNets](peered-vnet/main.bicep) | When more control is required on the Networking and Resource Groups, you can deploy at the subscription scope. | [![Deploy to Azure](https://aka.ms/deploytoazurebutton)](https://portal.azure.com/#create/Microsoft.Template/uri/https%3A%2F%2Fraw.git.ttaallkk.top%2Foliverlabs%2FAKS-Construction%2Foliver%2Fportal-deploy%2Fsamples%2Fpeered-vnet%2Fmain.json) _(via Azure portal UI)_
[Shared ACR](shared-acr/main.bicep) | Where an existing Azure Container Registry exists in a different resource group, this sample shows how to create the scoped 'ACR Pull' role assignment that the AKS cluster requires. | [![Deploy to Azure](https://aka.ms/deploytoazurebutton)](https://portal.azure.com/#create/Microsoft.Template/uri/https%3A%2F%2Fraw.git.ttaallkk.top%2Foliverlabs%2FAKS-Construction%2Foliver%2Fportal-deploy%2Fsamples%2Fshared-acr%2Fmain.json) _(via Azure portal UI)_
[NetworkForByo.bicep](networkforbyo.bicep) | When using the BYO network configuration you'll usually be deploying to a subscription with a peered virtual network already deployed with the correct subnets. This bicep file bridges the gap where you don't yet have that virtual network, but want to BYO network. | [![Deploy to Azure](https://aka.ms/deploytoazurebutton)](https://portal.azure.com/#create/Microsoft.Template/uri/https%3A%2F%2Fraw.git.ttaallkk.top%2Foliverlabs%2FAKS-Construction%2Foliver%2Fportal-deploy%2Fsamples%2Fnetworkforbyo.json) _(via Azure portal UI)_
[Deployment Stages](deploy-stages/README.md) | Creating a staged deployment with an existing Managed Identity, Network Subnet and ACR, this configuration demonstrates how to pass the BYO Identity into AKS-Construction for Azure Subscriptions with restricted RBAC. |
Loading