| title | Deploy Azure resources with Meshery | ||
|---|---|---|---|
| description | Learn how to deploy and manage Azure resources through Kubernetes with Meshery, utilizing ASO operator to enhance cloud resource management | ||
| model | azure | ||
| params |
|
||
| categories |
|
||
| aliases |
|
Meshery now supports managing Azure resources declaratively through Kubernetes by integrating with Azure Service Operator (ASO). With this capability, you can visually design, deploy, and manage a variety of Azure resources—such as Storage Accounts, Key Vaults, SQL Servers, and more—directly from Meshery’s UI. In this tutorial, you’ll install the ASO operator (without CRD pattern configurations, as Meshery will handle them), create a Service Principal and a Kubernetes secret with your Azure credentials, and use Meshery to provision Azure resources seamlessly into your subscription.
Before you begin, ensure you have the following:
- Meshery Installed A self-hosted Meshery instance running on your Kubernetes cluster (in-cluster or out-of-cluster).
- Kubernetes Cluster
A running Kubernetes cluster (v1.16+) with
kubectlconfigured. - Azure Subscription An active Azure subscription where Storage Accounts will be provisioned.
- Azure CLI
Installed and authenticated (
az login) in your local shell. - cert-manager Installed in your Kubernetes cluster (required by Azure Service Operator).
If you do not already have a Service Principal (SP) for Meshery, create one using the Azure CLI:
az ad sp create-for-rbac -n azure-service-operator --role contributor --scopes /subscriptions/<AZURE_SUBSCRIPTION_ID>
This command outputs the following credentials:
appId: Application ID (Client ID)displayName: Service Principal Namename: Azure Service Principal URLpassword: Client Secrettenant: Tenant ID
To export them, manually enter:
export AZURE_CLIENT_ID=<appId> export AZURE_CLIENT_SECRET=<password> export AZURE_TENANT_ID=<tenant> export AZURE_SUBSCRIPTION_ID=<subscriptionId>
If you haven’t already connected your cluster to Meshery, run:
mesheryctl system start
Then open the Meshery UI (default: http://localhost:9081) and ensure your cluster appears under Lifecycle → Connections.
Create a cert-manager that is necessary for deployment of Azure Service operator
kubectl apply -f https://github.com/jetstack/cert-manager/releases/download/v1.14.1/cert-manager.yaml
Apply the official ASO operator manifest (Meshery will manage CRDs):
kubectl apply -f https://github.com/Azure/azure-service-operator/releases/download/v2.13.0/azureserviceoperator_v2.13.0.yaml
Azure Service Operator requires a Kubernetes secret with your Azure identity:
kubectl create secret generic azure-credentials --namespace azureserviceoperator-system --from-literal=AZURE_CLIENT_ID=$AZURE_CLIENT_ID --from-literal=AZURE_CLIENT_SECRET=$AZURE_CLIENT_SECRET --from-literal=AZURE_TENANT_ID=$AZURE_TENANT_ID --from-literal=AZURE_SUBSCRIPTION_ID=$AZURE_SUBSCRIPTION_ID
- Click Start from template. Start From Template
- Search for the Azure Service Operator design. Search Azure Operator
- Once found, click on the Azure Service Operator design, after that, click on Clone to add it to your canvas. Clone Azure Operator
- Update the secret aso-controller-settings in the design template. The details are also mentioned in the catalog. Configure Secret Settings
- Click Actions → Deploy. Deploy Azure Operator
- Click on Components and start by searching Azure Storage and putting the Storage Account to design area. Select Components Search Storage Account
- Configure the Storage Account to fit your needs. Config Storage Account
- Click Actions → Deploy. Deploy Storage Account
- Azure Portal: Confirm the new Storage Account appears in your specified resource group.
You have successfully:
- Created an Azure Service Principal for Meshery
- Connected your Kubernetes cluster to Meshery
- Installed the Azure Service Operator (Meshery managed CRDs)
- Created a Kubernetes secret for Azure credentials
- Designed and deployed Azure resources using Meshery’s Kanvas
If you want to learn more about Azure Service Operator, visit the official ASO documentation.