skills.rest
aldengolab
aldengolabCOMMUNITY
Explore all skills by this author →
𝕏@aldengolabGitHub

tailscale-k8s-ingress-https

Configure TLS termination for Kubernetes services using the Tailscale Ingress proxy.

Updated Aug 27, 2026
Search Tags:#kubernetes#tailscale#tls#https#provisioning#ingress#cert
One-click install
npx skills add https://github.com/aldengolab/lorist --skill tailscale-k8s-ingress-https
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: tailscale-k8s-ingress-https
Source: https://github.com/aldengolab/lorist/tree/main/skills/tailscale-k8s-ingress-https
Command: npx skills add https://github.com/aldengolab/lorist --skill tailscale-k8s-ingress-https

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

TLS termination for Kubernetes services via the Tailscale Ingress proxy is not automatically provisioning certificates, leading to errors such as tlsv1 alert internal error on raw IPs or timeouts on correct hostnames.

Core Features & Use Cases

  • TLS termination at the Tailscale proxy for Ingress-backed services, simplifying certificate management.
  • One-time certificate provisioning via tailscale cert for the host, with immediate HTTPS after provisioning.
  • Guidance for verification with tailscale serve status and DNS propagation notes.

Quick Start

Create the Ingress with ingressClassName tailscale and a tls stanza for your service, then provision the TLS certificate with tailscale cert for the hostname.

Frequently Asked Questions about tailscale-k8s-ingress-https

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

FAQPage Schema
How do I fix TLS termination errors on my Kubernetes Tailscale Ingress?▼

TLS termination errors on Tailscale Ingress are fixed by provisioning certificates with tailscale cert and configuring a TLS stanza in your Ingress resource. This resolves tlsv1 alert internal errors and timeouts caused by missing certificate setup.

How does TLS termination work with the Tailscale Ingress proxy in Kubernetes?▼

TLS termination with the Tailscale Ingress proxy works by terminating HTTPS at the proxy layer using ingressClassName tailscale. You provision a certificate with tailscale cert and apply a TLS stanza to secure the service.

Why is my Tailscale Ingress timing out on the correct hostname?▼

Timeouts on correct hostnames during Tailscale Ingress setup usually indicate DNS propagation has not completed or the TLS certificate is not yet provisioned. Run tailscale serve status to verify provisioning and wait for DNS to update.

What are the steps to provision a TLS certificate for a Kubernetes Tailscale Ingress?▼

To provision TLS for Tailscale Ingress, create the Ingress with ingressClassName tailscale and a TLS stanza, then run tailscale cert for your hostname. Verify the setup with tailscale serve status to confirm HTTPS is active.

Why am I getting a tlsv1 alert internal error when accessing my Tailscale service?▼

A tlsv1 alert internal error occurs when accessing raw IPs without a provisioned TLS certificate. Provision the certificate using tailscale cert for the hostname and access the service via the configured hostname instead of the IP address.

Do I need to manually provision certificates for Kubernetes Tailscale Ingress?▼

Yes, you need to manually run tailscale cert one time for your hostname to provision the TLS certificate. After this initial provisioning, HTTPS becomes immediately available and is managed through the Ingress TLS configuration.

Related Skills

Explore More Software Engineering Skills→
TitoPrauseeTitoPrausee

tailscale-docker

Configure Tailscale in Docker containers using userspace networking and SOCKS5 proxy.

Community
Intermediate
heimeshoffheimeshoff
1

tailscale-deploy

Deploy an F# application with a Tailscale sidecar using Docker Compose.

Community
Advanced
jeremylongshorejeremylongshore
2.6k

creating-kubernetes-deployments

Generate Kubernetes YAML manifests with health checks, autoscaling, and TLS.

Community
Advanced
romankovsvromankovsv

networking

Design AWS and Kubernetes networking patterns for VPC, Ingress, Istio, DNS, TLS, and PrivateLink.

Community
Advanced