service-ingress

Name: service-ingress
Availability: InStock
Author: chaterm

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

50|13|Updated Jan 19, 2026

Search Tags:#networking #kubernetes #cloud #service #k8s #ingress

Ready to run

npx skills add https://github.com/chaterm/terminal-skills --skill service-ingress

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: service-ingress
Source: https://github.com/chaterm/terminal-skills/tree/main/kubernetes/service-ingress
Command: npx skills add https://github.com/chaterm/terminal-skills --skill service-ingress

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill simplifies the management of how network traffic reaches your applications within a Kubernetes cluster, covering both internal service exposure and external access via Ingress.

Core Features & Use Cases

Service Types: Understand and configure ClusterIP, NodePort, LoadBalancer, and ExternalName services.
Ingress Configuration: Define rules for routing external HTTP/S traffic to internal services, including TLS termination.
Use Case: You need to expose a web application running in Kubernetes to the internet. This Skill helps you create an Ingress resource that directs traffic from a specific domain name to your application's Service, and configure TLS for secure HTTPS access.

Quick Start

Use the service-ingress skill to create a basic Ingress resource for the host 'example.com' that routes traffic to a service named 'my-service' on port 80.

Frequently Asked Questions about service-ingress

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

FAQPage Schema

How do I configure Kubernetes Ingress for host-based routing and TLS termination?▼

To configure Kubernetes Ingress, you define rules for routing external HTTP/S traffic to internal services, including setting up TLS termination for secure HTTPS access to your specified domain host.

What is the difference between ClusterIP, NodePort, and LoadBalancer Kubernetes services?▼

ClusterIP exposes services internally within the cluster, NodePort exposes them on a static port across all nodes, and LoadBalancer provisions an external cloud provider load balancer for public access.

How do I expose a web application running in Kubernetes to the internet?▼

You expose a web application by creating an Ingress resource that directs external traffic from a specific domain name to your application's Service, configuring TLS for secure HTTPS access.

Can I troubleshoot Kubernetes network connectivity issues within the cluster using this approach?▼

Yes, managing Kubernetes Service and Ingress resources facilitates troubleshooting of network connectivity issues within the cluster by validating service exposure and traffic routing configurations.

When should I use an ExternalName service in Kubernetes?▼

An ExternalName service in Kubernetes is used when you need to map a service to an external DNS name instead of routing traffic to internal cluster pods, acting as a proxy for external resources.

Does Kubernetes Ingress support path-based routing for multiple microservices?▼

Yes, Kubernetes Ingress supports path-based routing, allowing you to define rules that direct external HTTP/S traffic to different internal microservices based on the URL path.