# Configure Cluster Ingress

{% hint style="warning" %}
Manually configuration of Cluster Ingress is not necessary if [External IP Allowlisting](broken://pages/5N9KV1CKzaWO5ZMejy9U) is done.
{% endhint %}

When connecting tools like Tableau or JDBC drivers to an e6data cluster, [Ingress](#what-is-ingress-in-kubernetes) must first be configured in a customer's Kubernetes cluster. Below are a few tutorials to securely configure ingress in different scenarios.

1. [Configuring ALB Ingress in Kubernetes](/product-documentation/connectors-and-drivers/configure-cluster-ingress/alb-ingress-in-kubernetes.md)
2. [Configuring GCE Ingress in Kubernetes](/product-documentation/connectors-and-drivers/configure-cluster-ingress/gce-ingress-in-kubernetes.md)
3. [Configuring Ingress-Nginx in Kubernetes](/product-documentation/connectors-and-drivers/configure-cluster-ingress/ingress-nginx-in-kubernetes.md)

## What is Ingress in Kubernetes? <a href="#what-is-ingress-in-kubernetes" id="what-is-ingress-in-kubernetes"></a>

In Kubernetes, an Ingress is an API object that provides external access to [Services](#what-is-a-service-in-kubernetes) within a cluster. It acts as a layer 7 (HTTP/HTTPS) load balancer and allows you to define routing rules to direct incoming traffic to different services based on the URL path or domain.

More info: [Ingress - Official Kubernetes Documentation](< https://kubernetes.io/docs/concepts/services-networking/ingress/>)

## What is a Service in Kubernetes?

In Kubernetes, a Service is an abstraction that defines a logical set of pods and a policy by which to access them. It provides a consistent way to access and communicate with your application's pods, regardless of their dynamic nature (pods can be created, terminated, or scaled up/down).

More info: [Service - Official Kubernetes Documentation](https://kubernetes.io/docs/concepts/services-networking/service/)


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.e6data.com/product-documentation/connectors-and-drivers/configure-cluster-ingress.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.