Skip to content

Twingate

Twingate

Category: Networking Type: Cluster Service Tags: zero-trust · vpn · twingate Editable: Yes

Overview

Twingate is a Zero Trust Network Access (ZTNA) solution that replaces traditional VPNs with a modern, identity-based access model. The Twingate Kubernetes Operator integrates your cluster into a Twingate network, enabling private, authenticated access to cluster services for users and devices — without exposing services publicly or managing firewall rules. Access is controlled per-user and per-service through the Twingate admin console.

For setup instructions, see the Twingate Kubernetes Operator Getting Started guide.

How It Works

Cluster Service — Installed once per cluster by an administrator. Once active, the cluster connects to your Twingate network and cluster services can be accessed by authorised users without exposing them publicly.

Prerequisites

  • A Twingate account with an active network
  • An API key, Network Slug, and Remote Network ID from the Twingate admin console
  • Network Slug is visible in the Twingate admin console URL
  • Remote Network ID is shown in the URL when you select a Remote Network in the admin console

Installation

  1. Gather your credentials from the Twingate admin console
  2. Open Terra and navigate to the Plugin Marketplace
  3. Search for "twingate"
  4. Click Install
  5. Fill in the configuration fields below
  6. Click Confirm to deploy

After deployment, follow the Twingate operator guide to configure Resources and access policies.

Configuration

Install-Time Fields

Field Details
api_key string · Required
Twingate API Key from the admin console
network string · Required
Twingate Network Slug (visible in the admin console URL)
remote_network_id string · Required
Twingate Remote Network ID (from the URL when selecting a Remote Network)

Notes

  • This plugin is editable — you can rotate the API key and update network settings after install via Terra
  • After installation, define Twingate Resource objects to specify which cluster services are accessible to which users
  • Twingate uses a connector running in the cluster to broker connections; the connector must have outbound internet access to reach the Twingate control plane
  • Users access cluster services through the Twingate client app (desktop or mobile) — no VPN client configuration is required
plugins/twingate/terra.yaml
 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13
14
15
16
17
18
19
20
21
resource_id: twingate
name: twingate
icon: https://raw.githubusercontent.com/juno-fx/Terra-Official-Plugins/refs/heads/main/plugins/twingate/scripts/assets/twingate.png
description: Zero Trust VPN. Make sure you have all the required information from here https://github.com/Twingate/kubernetes-operator/wiki/Getting-Started.
category: Networking
tags:
  - zero-trust
  - vpn
  - twingate
  - cluster-level
editable: true
fields:
  - name: api_key
    description: Twingate API Key
    required: true
  - name: network
    description: Network Slug. This is in the URL of the Twingate admin console.
    required: true
  - name: remote_network_id
    description: Twingate Network ID. This is in the URL of the Twingate admin console when you select a Remote Network.
    required: true