skills.rest
villadalmine
villadalmineCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

gateway

Route cluster HTTP and HTTPS traffic through a shared Cilium Gateway.

1|Updated Apr 3, 2026
Search Tags:#kubernetes#tls#gateway-api#ingress#httproute#cilium#grpcroute
One-click install
npx skills add https://github.com/villadalmine/infra --skill gateway-villadalmine
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: gateway
Source: https://github.com/villadalmine/infra/tree/main/.agents/skills/gateway
Command: npx skills add https://github.com/villadalmine/infra --skill gateway-villadalmine

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you publish and manage cluster web traffic through one shared gateway instead of creating separate load balancers for every service. It centralizes routing, TLS termination, and namespace-based onboarding so new applications can be exposed consistently and safely.

Core Features & Use Cases

  • Shared ingress for all HTTP and HTTPS services behind a single Cilium Gateway.
  • Route management for HTTPRoute and GRPCRoute resources across namespaces.
  • TLS termination at the gateway with a wildcard certificate for cluster.home.
  • Clean onboarding for new services such as ArgoCD, Pi-hole web UI, Grafana, and other internal apps.
  • Use case: expose a new Kubernetes service by adding an HTTPRoute that points to the shared gateway, while Pi-hole and cert-manager continue handling DNS and certificates.

Quick Start

Ask me to publish a new cluster service on the shared gateway and I will generate the routing and deployment steps needed for that service.

Frequently Asked Questions about gateway

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

FAQPage Schema
How do I route HTTP and HTTPS traffic through a shared Kubernetes gateway instead of separate load balancers?▼

You can route cluster HTTP and HTTPS traffic through a shared Cilium Gateway by creating HTTPRoute or GRPCRoute resources that reference the gateway, centralizing TLS termination and namespace-spanning service onboarding behind a single entry point.

What do I need to set up before using Cilium Gateway API for shared ingress in Kubernetes?▼

Setting up shared ingress with Cilium Gateway API requires LB-IPAM pinned addresses, cert-manager wildcard certificates, Pi-hole wildcard DNS, and correct parentRefs, backendRefs, and allowedRoutes settings to function properly.

How do I expose a new Kubernetes service on a shared Cilium Gateway using HTTPRoute?▼

To expose a new service, create an HTTPRoute that points to the shared gateway using parentRefs and backendRefs, while Pi-hole handles wildcard DNS and cert-manager manages TLS termination for the cluster domain.

Can I use GRPCRoute resources across multiple namespaces with a single Cilium Gateway?▼

Yes, a shared Cilium Gateway supports GRPCRoute and HTTPRoute resources across namespaces, allowing new applications to be exposed consistently through namespace-spanning service onboarding and allowedRoutes settings.

How does wildcard TLS termination work with a shared Kubernetes gateway for internal apps?▼

Wildcard TLS termination is handled at the gateway using cert-manager to provision wildcard certificates for the cluster domain, enabling secure HTTPS access to internal apps like ArgoCD, Grafana, and Pi-hole web UI.

Related Skills

Explore More Software Engineering Skills→
villadalminevilladalmine
1

cert-manager

Issues and manages TLS certificates for private Kubernetes domains.

Community
Advanced
missBergmissBerg
3

eg-route

Generate HTTP, gRPC, TCP, UDP, and TLS routing manifests for Envoy Gateway.

Community
Advanced
KaiserWhoLearnsKaiserWhoLearns

ssl-certificate-management

Automate SSL/TLS certificate provisioning, renewal, and monitoring across infrastructure.

Community
Advanced
chatermchaterm
50

service-ingress

Configures Kubernetes Service and Ingress resources for network exposure and TLS termination.

Community
Intermediate