# How do I configure my own Ingress Controller?

**URL:** <https://community.okteto.com/t/how-do-i-configure-my-own-ingress-controller/887>\
**Category:** How Do I?\
**Tags:** installation\
**Created:** [June 18, 2023, 9:14pm UTC](https://community.okteto.com/t/how-do-i-configure-my-own-ingress-controller/887 "2023-06-18T21:14:23Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![pchico83](https://sea1.discourse-cdn.com/flex019/user_avatar/community.okteto.com/pchico83/32/25_2.png) [@pchico83](https://community.okteto.com/u/pchico83)\
**Post date:** [June 18, 2023, 9:14pm UTC](https://community.okteto.com/t/how-do-i-configure-my-own-ingress-controller/887/1 "2023-06-18T21:14:23Z")

</div>

You can disable the installation of the Okteto Nginx Ingress Controller with the following snippet in your Helm values file:

```yaml
ingress-nginx:
  enabled: false

okteto-nginx:
  enabled: false

defaultBackend:
  enabled: false

```

In that case, configure the following fields in the [ingress](https://www.okteto.com/docs/self-hosted/administration/configuration/#ingress) section:

- `ingress.oktetoIngressClass` with the ingress class you want to use for all the ingresses created during the Okteto installation.
- `ingress.class` with the ingress class you want to use for all the ingresses created in namespaces managed by Okteto.
- `ingress.ip` with the Cluster IP of your Ingress Controller.

If the Okteto Nginx Controller is disabled, the following features will stop working:

- Autowake Namespaces
- Error Pages
- Private Endpoints

## Default Certificate

Okteto’s [Automatic SSL](https://www.okteto.com/docs/core/endpoints/automatic-ssl/) and [Okteto AI](https://www.okteto.com/docs/okteto-ai/) features require your Ingress Controller to present a default certificate.

For example, when using the Ingress-Nginx Controller, you need to configure the [`--default-ssl-certificate` flag](https://kubernetes.github.io/ingress-nginx/user-guide/tls/#default-ssl-certificate) to serve a valid certificate.

Refer to your Ingress Controller’s documentation for specific configuration details.

## Kong Ingress Controller

If you are using Kong as your Ingress Controller, you need to add the following snippet:

```yaml
buildkit:
  ingress:
    annotations:
      konghq.com/protocol: "grpcs"
  service:
    annotations:
      konghq.com/protocol: "grpcs"
      konghq.com/read-timeout: "1800000"

```

This way, the Okteto Buildkit service will be exposed behind Kong using GRPCS with 30min read timeout, which gives you a 30min timeout to build each image.