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.

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

Azure kubernetes install docs #4532

Draft
wants to merge 5 commits into
base: main
Choose a base branch
from
Draft
Show file tree
Hide file tree
Changes from all commits
Commits
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
1 change: 1 addition & 0 deletions docs/install/kubernetes/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -34,6 +34,7 @@ You will need a Kubernetes environment. The deployment has currently been tested
- [AWS EKS](aws_terraform.md)
- [Digital Ocean](digital-ocean.md)
- MicroK8s
- [Azure AKS](azure.md)

It should run on any Kubernetes platform, but may require some changes for vendor specific Ingress setup.

Expand Down
59 changes: 59 additions & 0 deletions docs/install/kubernetes/azure.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,59 @@
---
navTitle: Azure AKS Installation
meta:
description: Learn how to install FlowFuse on AWS EKS with setup details for EKS, Nginx Ingress, AWS SES, and RDS PostgreSQL integration.
tags:
- flowfuse
- nodered
- azure
- aks
- nginx ingress
- helm
- kubernetes
---

# Azure AKS Specific details

This document includes details for installing FlowFuse on Azure AKS

## Nginx Ingress

We recommend using the <a href="https://kubernetes.github.io/ingress-nginx/" target="_blank">Nginx Ingress controller</a> as this is the one we test with and we have run into limits on the number of Instances with other Ingress Controllers.

```bash
helm repo add ingress-nginx https://kubernetes.github.io/ingress-nginx
helm repo update
helm --kubeconfig=./k8s-flowforge-kubeconfig.yaml install nginx-ingress \
ingress-nginx/ingress-nginx --namespace ingress-nginx \
--create-namespace \
--set controller.publishService.enabled=true \
--set controller.ingressClassResource.default=true \
--set controller.config.proxy-body-size="0"
--wait

```

The `controller.config.proxy-body-size="0"` removes the `1m` default payload limit
from the nginx ingress proxy. You can change this to say `5m` which will match the
Node-RED default value.


### HTTPS with Nginx Ingress

Azure's LoadBalancer does not support doing TLS termination so HTTPS certificates will either need to up added to AKS as Kubernetes Secrets or make use of
Certificate Manager to provision certificates either from LetsEncrypt or other ACME Certificate Authorities.

## Persistent Storage

If making use of the Persistent Storage feature you will need to provide a StorageClass that support MultiPod mounting.

e.g. Azure Files backed Persistent Volumes


You should also set the `nobrl` Mount Option to ensure things like SQLite databases work correctly if using the Azure Files back Persistent Volumes.

## User Azure Database for PostgreSQL

By default the helm chart will install a local copy of PostgreSQL 14.

But you may make use of Azure's hosted PostgreSQL solution, but you will need to provision the user and empty database before doing the Helm install.