connect-kubernetes-outpost

Deploy a SubImage Outpost via Helm or Docker to connect private APIs through an outbound Tailscale tunnel.

Updated Apr 30, 2026
One-click install
npx skills add https://github.com/subimagesec/skills --skill connect-kubernetes-outpost
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: connect-kubernetes-outpost
Source: https://github.com/subimagesec/skills/tree/main/plugins/subimage-setup/skills/connect-kubernetes-outpost
Command: npx skills add https://github.com/subimagesec/skills --skill connect-kubernetes-outpost

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you deploy a SubImage Outpost so SubImage can reach internal services and private APIs that are not accessible from the public internet.

Core Features & Use Cases

  • Private Network Access: Establishes an outbound Tailscale tunnel from a private network back to SubImage.
  • Deployment Paths: Supports both Helm-based Kubernetes installs and standalone Docker runs.
  • Use Cases: Ideal for private Kubernetes clusters, on-prem tools, and internal SaaS systems such as Jamf, BigFix, Kandji, SnipeIT, CrowdStrike, LastPass, and Semgrep.

Quick Start

Ask me to deploy a SubImage Outpost for your private API and I will gather the tenant ID, registration key, proxy target, TLS setting, and preferred deployment path before generating the configuration.

Frequently Asked Questions about connect-kubernetes-outpost

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I connect private Kubernetes APIs to an external service without exposing them to the public internet?

You can connect private APIs by deploying a SubImage Outpost that establishes an outbound Tailscale tunnel, allowing external services to reach internal targets without opening inbound firewall ports.

Can I use Helm to deploy an outbound tunnel for on-prem services?

Yes, Helm is fully supported for deploying the Outpost on Kubernetes clusters, and standalone Docker deployments are also available for on-prem services.

What configuration details are required to set up a Tailscale tunnel for internal SaaS targets?

Configuring the tunnel requires a tenant ID, outpost registration key, proxy target URL, TLS verification setting, and a matching hostname to verify the connection.

Does the SubImage Outpost work with internal SaaS tools like Jamf or CrowdStrike?

Yes, the Outpost is designed to work with internal SaaS tools like Jamf, CrowdStrike, LastPass, and Semgrep by proxying requests through the Tailscale tunnel.

How do I verify TLS when proxying requests to private APIs through an outbound tunnel?

You configure TLS verification by specifying a TLS verification setting and providing a matching hostname during the Outpost configuration to ensure secure connections.