Skip to main content
Version: 1.27

Air-Gapped Network Environments
EnterpriseSelf-Hosted

Okteto Enterprise can be installed in air-gapped environments—isolated networks without internet access. This guide explains how to install, configure and use a self-hosted Okteto instance entirely offline. For personalized assistance, feel free to talk to us to guide you during the installation.

Step 1: Disable Okteto Telemetry​

By default, Okteto sends telemetry data to help us understand usage patterns and prioritize improvements. In air-gapped environments, you can disable telemetry by adding the following to your Okteto Helm configuration:

telemetry:
  enabled: false

Disabling telemetry ensures that no usage analytics are sent from the Okteto CLI.

Step 2: Set Up a Private Registry for Required Images​

By default, all the images needed to deploy the Okteto Platform, and the images used by the Okteto CLI, are hosted in DockerHub. In air-gapped environments, you’ll need to host these images in your private registry.

Push Images to your Private Registry​

For simplicity, we recommend using the same repository names and tags in your private registry.

info

Since Okteto doesn’t support imagePullSecrets, ensure your Kubernetes cluster is pre-configured to access your private registry.

Required Images for Okteto Platform Installation

Push the following images to your private registry for the Okteto Chart installation:

  • okteto/backend:1.26.0
  • okteto/frontend:1.26.0
  • okteto/buildkit:1.26.0 and okteto/buildkit:1.26.0-rootless
  • okteto/registry:1.26.0
  • okteto/pipeline-runner:1.26.0
  • okteto/daemon:1.26.0
  • registry.k8s.io/ingress-nginx/controller-chroot:v1.11.2
  • ghcr.io/stakater/reloader:v1.0.119
  • bitnami/redis:7.4.0-debian-12-r1

For each Okteto CLI version, push the following images to your private registry:

  • okteto/okteto:3.1.0
info

For Okteto Chart 1.26.0, we recommend enforcing the usage of Okteto CLI 3.1.0 in your developer's machines to reduce maintenance overhead

Step 3: Update Helm Configuration​

These configurations ensure Okteto can pull required images from your private registry during deployment. Once your images are pushed to your private registry, update your Okteto Helm configuration as follows:

globals:
  registry: <<your-registry-url>>

cli:
  image:
    registry: <<your-registry-url>>

ingress-nginx:
  global:
    image:
      registry: <<your-registry-url>>

okteto-nginx:
  global:
    image: <<your-registry-url>>

reloader:
  reloader:
    deployment:
      image:
        name: <<your-registry-url>>/stakater/reloader

redis:
  global:
    imageRegistry: <<your-registry-url>>

Step 4: Install or Upgrade Okteto​

Run the following command to install Okteto for the first time or to upgrade an existing instance:

helm upgrade --install okteto okteto/okteto -f config.yaml --namespace=okteto --create-namespace --version=1.26.0

Need help with your installation? Contact us for expert guidance.