> [!CAUTION]
> You are currently viewing version 1.3 of the Apigee hybrid documentation. **This version is end of life.** You should upgrade to a newer version. For more information, see [Supported versions](https://docs.cloud.google.com/apigee/docs/hybrid/supported-platforms.md.txt#supported-versions).

<button class="button button-with-icon cloud-select-dropdown__button button-primary" aria-haspopup="true">Version 1.3 (unsupported)</button>

- Supported versions:
- [v1.17 (latest)](https://docs.cloud.google.com/apigee/docs/hybrid/v1.17/enable-non-sni.md.txt)
- [v1.16](https://docs.cloud.google.com/apigee/docs/hybrid/v1.16/enable-non-sni.md.txt)
- [v1.15](https://docs.cloud.google.com/apigee/docs/hybrid/v1.15/enable-non-sni.md.txt)
- [v1.14](https://docs.cloud.google.com/apigee/docs/hybrid/v1.14/enable-non-sni.md.txt)
- [List of supported versions](https://docs.cloud.google.com/apigee/docs/hybrid/supported-platforms.md.txt#supported-versions)
- Unsupported versions:
- [v1.13](https://docs.cloud.google.com/apigee/docs/hybrid/v1.13/enable-non-sni.md.txt)
- [v1.12](https://docs.cloud.google.com/apigee/docs/hybrid/v1.12/enable-non-sni.md.txt)
- [v1.11](https://docs.cloud.google.com/apigee/docs/hybrid/v1.11/enable-non-sni.md.txt)
- [v1.10](https://docs.cloud.google.com/apigee/docs/hybrid/v1.10/enable-non-sni.md.txt)
- [v1.9](https://docs.cloud.google.com/apigee/docs/hybrid/v1.9/enable-non-sni.md.txt)
- [v1.8](https://docs.cloud.google.com/apigee/docs/hybrid/v1.8/enable-non-sni.md.txt)
- [v1.7](https://docs.cloud.google.com/apigee/docs/hybrid/v1.7/enable-non-sni.md.txt)
- [v1.6](https://docs.cloud.google.com/apigee/docs/hybrid/v1.6/enable-non-sni.md.txt)
- [v1.5](https://docs.cloud.google.com/apigee/docs/hybrid/v1.5/enable-non-sni.md.txt)
- [v1.4](https://docs.cloud.google.com/apigee/docs/hybrid/v1.4/enable-non-sni.md.txt)
- [v1.3](https://docs.cloud.google.com/apigee/docs/hybrid/v1.3/enable-non-sni.md.txt)
- [v1.2](https://docs.cloud.google.com/apigee/docs/hybrid/v1.2/enable-non-sni.html)
- [v1.1](https://docs.cloud.google.com/apigee/docs/hybrid/v1.1/enable-non-sni.html)


This topic explains how to enable non-SNI clients, HTTP clients, and a combination of both
for use with Apigee hybrid.

## How to configure a non-SNI client

This section explains how to enable support for non-SNI ([Server Name Indication](https://en.wikipedia.org/wiki/Server_Name_Indication)) clients in Apigee hybrid. A non-SNI client uses port 443 and is required if you want to integrate hybrid runtime instances with Google [Cloud Load Balancing](https://cloud.google.com/load-balancing/docs) or for clients that do not support SNI.

1. Create an ApigeeRoute custom resource definition (CRD). Be sure that `enableNonSniClient` is set to `true`:

   ```
   apiVersion: apigee.cloud.google.com/v1alpha1
   kind: ApigeeRoute
   metadata:
     name: route_name
     namespace: apigee
   spec:
     hostnames:
     - "*"
     ports:
     - number: 443
       protocol: HTTPS
       tls:
         credentialName: credential_name
         mode: SIMPLE
         #optional
         minProtocolVersion: TLS_AUTO
     selector:
       app: istio-ingressgateway
     enableNonSniClient: true
   ```


   Where:
   - <var translate="no">route_name</var> is the name you give to the CRD.
   - <var translate="no">credential_name</var> is the name of a Kubernetes Secret deployed to the cluster that contains TLS credentials for your virtualhost.
   - `hostname` must be set to the wildcard "\*". **Note:**Do not create two ApigeeRoute objects with a wildcard "\*" hostname.
2. Open your overrides file and make the change described in the next step.
3. For each environment group, add the ApigeeRoute name to the `additionalGateways` property. For example:

   ```
   virtualhosts:
     - name: default
       sslCertPath: ./certs/fullchain.pem
       sslKeyPath: ./certs/privkey.pem
       additionalGateways: ["route_name"]
   ```
4. Save the CRD file. For example: `ApigeeRoute.yaml`
5. Apply the CRD to the cluster:

   ```
   kubectl apply -f ApigeeRoute.yaml -n apigee
   ```
6. Apply the change to `virtualhosts`:

   ```
   $APIGEECTL_HOME/apigeectl apply -f overrides.yaml --settings virtualhosts --env $ENVIRONMENT
   ```

## Usage notes

- **What happens if the cluster has more than one org?**


  Since the ingress is at the cluster level for a given port (443), and there can only
  be one key/cert pair for the ApigeeRoute CRD, all orgs must share the same key/cert pair.
- **What happens if the cluster has more than one environment group. Will it work
  if the virtual hosts share the same key/cert pair?**


  All hostnames across all environment groups must use the same key/cert pair.
- **Why are we creating an ApigeeRoute instead of Gateway?**


  ApigeeRoutes can be validated by Apigee; however,
  [Gateway](https://istio.io/latest/docs/reference/config/networking/gateway/) (the Istio CRD) cannot be.
  Technically, even Gateway can work, but we can prevent potential configuration mistakes
  (through a validation webhook).

## Enable HTTP clients


This section explains support for HTTP clients for use with Apigee hybrid.

> [!NOTE]
> **Note:** We do not recommend enabling port 80. All transmission, especially API traffic, should be over TLS (1.2 or higher).

1. Create an ApigeeRoute custom resource definition (CRD). For example:

   ```
   apiVersion: apigee.cloud.google.com/v1alpha1
   kind: ApigeeRoute
   metadata:
     name: route_name
     namespace: apigee
   spec:
     hostnames:
     - "*"
     ports:
     - number: 80
       protocol: HTTP
     selector:
       app: istio-ingressgateway
     enableNonSniClient: true
   ```


   Where:
   - <var translate="no">route_name</var> is the name you give to the CRD.
   - `hostnames` must be set to the wildcard "\*". **Note:**Do not create two ApigeeRoute objects with a wildcard "\*" hostname.
2. Open your overrides file and make the change described in the next step.
3. For each environment group, add the ApigeeRoute name to the `additionalGateways` property. For example:

   ```
   virtualhosts:
     - name: default
       sslCertPath: ./certs/fullchain.pem
       sslKeyPath: ./certs/privkey.pem
       additionalGateways: ["route_name"]
   ```
4. Save the CRD file. For example: `ApigeeRoute.yaml`
5. Apply the CRD to the cluster:

   ```
   kubectl apply -f ApigeeRoute.yaml -n apigee
   ```
6. Apply the change to `virtualhosts`:

   ```
   $APIGEECTL_HOME/apigeectl apply -f overrides.yaml --settings virtualhosts --env $ENVIRONMENT
   ```

## Enable support for both non-SNI and HTTP clients


This section explains how to enable **both** non-SNI (port 443) and HTTP (port 80) clients
for use with Apigee hybrid.

> [!NOTE]
> **Note:** We do not recommend enabling port 80. All transmission, especially API traffic, should be over TLS (1.2 or higher).

1. Create an ApigeeRoute custom resource definition (CRD). For example:

   ```
   apiVersion: apigee.cloud.google.com/v1alpha1
   kind: ApigeeRoute
   metadata:
     name: route_name
     namespace: apigee
   spec:
     hostnames:
     - "*"
     ports:
     - number: 443
       protocol: HTTPS
       tls:
         credentialName: credential_name
         mode: SIMPLE
         #optional
         minProtocolVersion: TLS_AUTO
     - number: 80
       protocol: HTTP
     selector:
       app: istio-ingressgateway
     enableNonSniClient: true
   ```


   Where:
   - <var translate="no">route_name</var> is the name you give to the CRD.
   - `hostnames` must be set to the wildcard "\*". **Note:**Do not create two ApigeeRoute objects with a wildcard "\*" hostname.
   - <var translate="no">credential_name</var> is the name of a Kubernetes Secret deployed to the cluster that contains TLS credentials for your virtualhost.
2. Open your overrides file and make the change described in the next step.
3. For each environment group, add the ApigeeRoute name to the `additionalGateways` property. For example:

   ```
   virtualhosts:
     - name: default
       sslCertPath: ./certs/fullchain.pem
       sslKeyPath: ./certs/privkey.pem
       additionalGateways: ["route_name"]
   ```
4. Save the CRD file. For example: `ApigeeRoute.yaml`
5. Apply the CRD to the cluster:

   ```
   kubectl apply -f ApigeeRoute.yaml -n apigee
   ```
6. Apply the change to `virtualhosts`:

   ```
   $APIGEECTL_HOME/apigeectl apply -f overrides.yaml --settings virtualhosts --env $ENVIRONMENT
   ```