Custom Ingress support for Grid deployment

Automate TurboScale supports custom ingress controllers during grid installation, enabling you to seamlessly integrate your existing ingress setup with the platform. This avoids creating a redundant ingress controller if you have already configured one for other applications. By default, Automate TurboScale creates an nginx-ingress controller. However, you can configure the grid to utilize your existing infrastructure if you already have an ingress in place.

Supported Ingress types

Currently, Automate TurboScale supports two types of custom ingress:

1. nginx-based Ingress
2. alb-based Ingress (Application Load Balancer)

Configuration for nginx-based Ingress

To integrate with an existing nginx ingress, provide the following parameters during the Helm installation:

helm install <other-flags> --set ingress-service="" --set ingress-namespace="" --set ingress-class=""

• ingress-service: Name of the existing ingress service.
• ingress-namespace: The namespace where the ingress is deployed.
• ingress-class: The ingress class (e.g., nginx) to be used.

Configuration for alb-based Ingress

For an alb-based ingress, users can configure their ingress with the following Helm parameters:

helm install <other-flags> --set loadbalancer-url="" --set loadbalancer-name="" --set loadbalancer-type="" --set loadbalancer-groupname="" --set loadbalancer-scheme="" --set ingress-service=""  --set ingress-namespace="" --set ingress-class=""

• loadbalancer-url: The URL of the load balancer.
• loadbalancer-name: The name of the load balancer.
• loadbalancer-type: The type of load balancer (e.g., CNAME).
• loadbalancer-groupname: The name of the load balancer group.
• loadbalancer-scheme: The type of load balancer scheme (e.g., internal or internet-facing).
• ingress-service: Name of the existing ingress service.
• ingress-namespace: The namespace where the ingress is deployed.
• ingress-class: The ingress class used.

Limitations with alb Ingress

A known limitation of using alb-based ingress is that the grid supports only HTTP connections, not HTTPS. Consider this constraint when planning deployments with alb.

This flexibility in ingress support ensures that you can seamlessly integrate your existing ingress infrastructure with our grid deployment process.