-
Notifications
You must be signed in to change notification settings - Fork 1.5k
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
[azure-docs] docs on setting up AKS agent
- Loading branch information
Showing
3 changed files
with
60 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,40 @@ | ||
# Dagster+ on Azure - Quickstart Guide | ||
|
||
This guide will walk you through deploying a Dagster+ agent on an Azure Kubernetes Service (AKS) cluster. | ||
|
||
This guide is intended to be a quickstart, and you should always defer to organization-specific guidelines for creating and managing new infrastructure. | ||
|
||
We'll start from a brand new organization in Dagster+, and finish with a full hybrid deployment of Dagster+ using Azure infrastructure. | ||
|
||
## Prerequisites | ||
|
||
To complete the steps in this guide, you'll need: | ||
|
||
- The azure CLI installed on your machine. You can download it [here](https://docs.microsoft.com/en-us/cli/azure/install-azure-cli). | ||
- `kubectl` installed on your machine. You can download it [here](https://kubernetes.io/docs/tasks/tools/install-kubectl/). | ||
- `helm` installed on your machine. You can download it [here](https://helm.sh/docs/intro/install/). | ||
- An existing AKS cluster. If you need to create a new AKS cluster, refer to the [Azure documentation](https://learn.microsoft.com/en-us/azure/aks/learn/quick-kubernetes-deploy-portal?tabs=azure-cli). | ||
- A Dagster+ organization, with an agent token for that organization. | ||
|
||
## Step 1: Generate a Dagster+ agent token. | ||
|
||
<GenerateAgentToken /> | ||
|
||
## Step 2: Log in to your AKS cluster. | ||
|
||
We'll use the azure CLI to log in to your AKS cluster. Run the following command and follow the prompts to log in. | ||
|
||
```bash | ||
az login | ||
az aks get-credentials --resource-group <your-resource-group> --name <your-aks-cluster> | ||
``` | ||
|
||
We should now be able to verify our installation by running a command that tells us the current context of our kubectl installation. We'd expect it to output the name of the AKS cluster. | ||
|
||
```bash | ||
kubectl config current-context | ||
``` | ||
|
||
## Step 3: Install the Dagster+ agent on the AKS cluster. | ||
|
||
Next, we'll install the agent helm chart. You should be able to follow the guide [here](/concepts/deployment/agents/kubernetes/configuring-running-kubernetes-agent) to install the agent on the AKS cluster. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,10 @@ | ||
# Deploying Dagster+ hybrid on Azure | ||
|
||
This guide will walk you through deploying Dagster+ on Azure. We'll start from a brand new organization in Dagster+, and finish with a full hybrid deployment of Dagster+ using Azure infrastructure. | ||
|
||
<ArticleList> | ||
<ArticleListItem | ||
title="Step 1: Deploy an Azure Kubernetes Service (AKS) agent" | ||
href="/dagster-plus/deployment/azure/aks-agent" | ||
></ArticleListItem> | ||
</ArticleList> |