> For the complete documentation index, see [llms.txt](https://docs.openg2p.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.openg2p.org/~/changes/xKUM0sBXFkyR8F24yAMq/deployment/base-infrastructure/openg2p-cluster/cluster-setup/istio.md).

# Istio

Istio Setup

Istio is a power traffic mesh management tool. It also provides an ingress gateway for the Kubernetes cluster.

## Installation

### Operator Setup

* The following setup can be done from the client machine. This installs Istio Operator, Istio Service Mesh, Istio Ingressgateway components.
* From [kubernetes/istio](https://github.com/OpenG2P/openg2p-deployment/tree/main/kubernetes/istio) directory, run;

  ```bash
  istioctl operator init
  kubectl apply -f istio-operator.yaml
  ```

  * Wait for `istiod` and `ingressgateway` pods to start.
* Or, for Rancher cluster, run:

  ```bash
  kubectl apply -f istio-operator-no-ingress.yaml
  ```

  * Wait for `istiod` to start and `ingressgateway` pods to get deleted if any.
  * Run the following:

    ```bash
    kubectl apply -f istio-ef-spdy-upgrade.yaml
    ```

### Namespace Setup

(Skip this section for Rancher cluster)

Once the above Operator setup is done, gateways need to be set up on each namespace. This assumes that the namespace (and relevant Rancher project) are created.

* Edit and run this to define the variables:

  ```
  export NS=dev
  export WILDCARD_HOSTNAME='*.dev.your.org'
  ```
* Run this apply gateways

  ```bash
  envsubst < istio-gateway.yaml | kubectl apply -f -
  ```

## Multiple ingress gateways

By default the installation scripts enable two Istio Ingress gateways -  **public** and **private**. The public gateway is disabled by default. You may enable the same while opening up services to the public by following the steps given [below](#enabling-public-gateway).  To create more private gateways, refer [here](#creating-private-gateways).

{% hint style="warning" %}
Having only one private gateway implies that all users can open URLs in all namespaces. Access control to services may be accomplished by authentication/authorization of the respective services via Keycloak
{% endhint %}

### Enabling public gateway

TBD.

### Creating private gateways

TBD.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## 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, and the optional `goal` query parameter:

```
GET https://docs.openg2p.org/~/changes/xKUM0sBXFkyR8F24yAMq/deployment/base-infrastructure/openg2p-cluster/cluster-setup/istio.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.