-
Notifications
You must be signed in to change notification settings - Fork 1k
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.
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
Add docs page for Azure setup #1276
Merged
Merged
Changes from all commits
Commits
Show all changes
2 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
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
63 changes: 63 additions & 0 deletions
63
docs/getting-started/install-feast/kubernetes-azure-aks-with-terraform.md
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,63 @@ | ||
# Azure AKS \(with Terraform\) | ||
|
||
### Overview | ||
|
||
This guide installs Feast on Azure using our [reference Terraform configuration](https://github.com/feast-dev/feast/tree/master/infra/terraform/azure). | ||
|
||
{% hint style="info" %} | ||
The Terraform configuration used here is a greenfield installation that neither assumes anything about, nor integrates with, existing resources in your Azure account. The Terraform configuration presents an easy way to get started, but you may want to customize this set up before using Feast in production. | ||
{% endhint %} | ||
|
||
This Terraform configuration creates the following resources: | ||
|
||
* Kubernetes cluster on Azure AKS | ||
* Kafka managed by HDInsight | ||
* Postgres database for Feast metadata, running as a pod on AKS | ||
* Redis cluster, using Azure Cache for Redis | ||
* [spark-on-k8s-operator](https://github.com/GoogleCloudPlatform/spark-on-k8s-operator) to run Spark | ||
* Staging Azure blob storage container to store temporary data | ||
|
||
### 1. Requirements | ||
|
||
* Create an Azure account and [configure credentials locally](https://docs.microsoft.com/en-us/cli/azure/install-azure-cli) | ||
* Install [Terraform](https://www.terraform.io/) \(tested with 0.13.5\) | ||
* Install [Helm](https://helm.sh/docs/intro/install/) \(tested with v3.4.2\) | ||
|
||
### 2. Configure Terraform | ||
|
||
Create a `.tfvars` file under`feast/infra/terraform/azure`. Name the file. In our example, we use `my_feast.tfvars`. You can see the full list of configuration variables in `variables.tf`. At a minimum, you need to set `name_prefix` and `resource_group`: | ||
|
||
{% code title="my\_feast.tfvars" %} | ||
```typescript | ||
name_prefix = "feast" | ||
resource_group = "Feast" # pre-existing resource group | ||
``` | ||
{% endcode %} | ||
|
||
### 3. Apply | ||
|
||
After completing the configuration, initialize Terraform and apply: | ||
|
||
```bash | ||
$ cd feast/infra/terraform/azure | ||
$ terraform init | ||
$ terraform apply -var-file=my_feast.tfvars | ||
``` | ||
|
||
### 4. Connect to Feast using Jupyter | ||
|
||
After all pods are running, connect to the Jupyter Notebook Server running in the cluster. | ||
|
||
To connect to the remote Feast server you just created, forward a port from the remote k8s cluster to your local machine. | ||
|
||
```bash | ||
kubectl port-forward $(kubectl get pod -o custom-columns=:metadata.name | grep jupyter) 8888:8888 | ||
``` | ||
|
||
```text | ||
Forwarding from 127.0.0.1:8888 -> 8888 | ||
Forwarding from [::1]:8888 -> 8888 | ||
``` | ||
|
||
You can now connect to the bundled Jupyter Notebook Server at `localhost:8888` and follow the example Jupyter notebook. | ||
|
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should this be here? It's GKE?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
yes it should've been added to this page before so I just added it in as part of this diff