Search Kubernetes Ingress resources.

kubectl-ingress-search

Search Ingress resources.

Installation

  1. Download from Releases page.
  2. cp kubectl-ingress-search /usr/local/bin/
  3. use kubectl-ingress-search or kubectl ingress search

Usage

list all ingress in default namespace:

$ kubectl ingress search
  NAMESPACE |                  NAME                   |         HOST          |   PATH    |                  BACKEND                   
------------+-----------------------------------------+-----------------------+-----------+--------------------------------------------
  default   | ingress-resource-backend                |                       | /icons    | k8s.example.com/StorageBucket/icon-assets  
  default   | ingress-wildcard-host                   | foo.bar.com           | /bar      | Service/service1:80                        
  default   | ingress-wildcard-host                   | *.foo.com             | /foo      | Service/service2:80                        
  default   | minimal-ingress                         |                       | /testpath | Service/test:80                            
  default   | name-virtual-host-ingress               | foo.bar.com           | /         | Service/service1:80                        
  default   | name-virtual-host-ingress               | bar.foo.com           | /         | Service/service2:80                        
  default   | name-virtual-host-ingress-no-third-host | first.bar.com         | /         | Service/service1:80                        
  default   | name-virtual-host-ingress-no-third-host | second.bar.com        | /         | Service/service2:80                        
  default   | name-virtual-host-ingress-no-third-host |                       | /         | Service/service3:80                        
  default   | simple-fanout-example                   | foo.bar.com           | /foo      | Service/service1:4200                      
  default   | simple-fanout-example                   | foo.bar.com           | /bar      | Service/service2:8080                      
  default   | tls-example-ingress                     | https-example.foo.com | /         | Service/service1:80                        

by namespace

$ kubectl ingress search -n test
  NAMESPACE |      NAME       | HOST |   PATH    |     BACKEND      
------------+-----------------+------+-----------+------------------
  test      | minimal-ingress |      | /testpath | Service/test:80  

all namespaces:

$ kubectl ingress search -A
  NAMESPACE |                  NAME                   |         HOST          |   PATH    |                  BACKEND                   
------------+-----------------------------------------+-----------------------+-----------+--------------------------------------------
  default   | ingress-resource-backend                |                       | /icons    | k8s.example.com/StorageBucket/icon-assets  
  default   | ingress-wildcard-host                   | foo.bar.com           | /bar      | Service/service1:80                        
  default   | ingress-wildcard-host                   | *.foo.com             | /foo      | Service/service2:80                        
  default   | minimal-ingress                         |                       | /testpath | Service/test:80                            
  default   | name-virtual-host-ingress               | foo.bar.com           | /         | Service/service1:80                        
  default   | name-virtual-host-ingress               | bar.foo.com           | /         | Service/service2:80                        
  default   | name-virtual-host-ingress-no-third-host | first.bar.com         | /         | Service/service1:80                        
  default   | name-virtual-host-ingress-no-third-host | second.bar.com        | /         | Service/service2:80                        
  default   | name-virtual-host-ingress-no-third-host |                       | /         | Service/service3:80                        
  default   | simple-fanout-example                   | foo.bar.com           | /foo      | Service/service1:4200                      
  default   | simple-fanout-example                   | foo.bar.com           | /bar      | Service/service2:8080                      
  default   | tls-example-ingress                     | https-example.foo.com | /         | Service/service1:80                        
  test      | minimal-ingress                         |                       | /testpath | Service/test:80                            

by service

$ kubectl ingress search -s service2

img.png

by name

$ kubectl ingress search --name host

img.png

by host

$ kubectl ingress search --host bar

img.png

by path

$ kubectl ingress search --path bar

img.png

by backend

$ kubectl ingress search -b k8s

img.png

regexp

$ kubectl ingress search --name 'vir.*host' -m regexp

img.png

auto merge

$ kubectl ingress search --auto-merge --host foo.bar
+-----------+---------------------------+-------------+------+-----------------------+
| NAMESPACE |           NAME            |    HOST     | PATH |        BACKEND        |
+-----------+---------------------------+-------------+------+-----------------------+
| default   | ingress-wildcard-host     | foo.bar.com | /bar | Service/service1:80   |
+           +---------------------------+             +------+                       +
|           | name-virtual-host-ingress |             | /    |                       |
+           +---------------------------+             +------+-----------------------+
|           | simple-fanout-example     |             | /foo | Service/service1:4200 |
+           +                           +             +------+-----------------------+
|           |                           |             | /bar | Service/service2:8080 |
+-----------+---------------------------+-------------+------+-----------------------+

highlight duplicate services

$ kubectl ingress search -H

img.png

arguments

$ kubectl-ingress-search -h
kubectl-ingress-search search Ingress resources to match given pattern(s).
It prints matched Ingress in table format.
More info: https://github.com/mozilazg/kubectl-ingress-search

Usage:
  kubectl-ingress-search [flags]

Examples:

$ kubectl ingress search
$ kubectl ingress search --service test
$ kubectl ingress search --name test
$ kubectl ingress search --host example.com
$ kubectl ingress search --path /test
$ kubectl ingress search --no-header
$ kubectl ingress search --match-mode exact
$ kubectl ingress search --match-mode regexp
$ kubectl ingress search --case-sensitive


Flags:
  -A, --all-namespaces                if present, list the requested object(s) across all namespaces. Namespace in current context is ignored even if specified with --namespace
      --auto-merge                    auto merge table cells
  -b, --backend string                search by backend
  -I, --case-sensitive                case sensitive pattern match
  -h, --help                          help for kubectl-ingress-search
  -H, --highlight-duplicate-service   highlight duplicate service
      --host string                   search by host
      --kubeconfig string             path to the kubeconfig file to use for CLI requests
  -m, --match-mode string             exact match or regexp match. One of (exact|regexp) (default "exact")
      --name string                   search by name
  -n, --namespace string              if present, the namespace scope for this CLI request (default "default")
      --no-header                     don't show table header
  -p, --path string                   search by path
  -s, --service string                search by service
  -V, --version                       show version and exit

Similar Resources

nginx exporter for Prometheus copy code from ingress-nginx use for monit nginx

nginx exporter for Prometheus  copy code from ingress-nginx use for monit nginx

nginx_exporter 介绍 从ingress-nginx官方代码中的expoter迁移出来 用来监控虚拟机上的nginx的expoter 基于官方 controller-v0.49.3 版本移植的代码 软件架构 nginx_socket 通过lua模块monitor.lua 将nginx l

Dec 8, 2021

nginx exporter for Prometheus copy code from ingress-nginx use for monit nginx

nginx exporter for Prometheus copy code from ingress-nginx use for monit nginx

nginx_exporter 介绍 从ingress-nginx官方代码中的expoter迁移出来 用来监控虚拟机上的nginx的expoter 基于官方 controller-v0.49.3 版本移植的代码 软件架构 nginx_socket 通过lua模块monitor.lua 将nginx l

Dec 20, 2021

An implementation of an Ingress controller for NGINX and NGINX Plus

🚀 Help make the NGINX Ingress Controller better by participating in our survey!

Dec 9, 2022

expose controller, when deployment created service and ingress will be created

expose-controller expose controller, when deployment created service and ingress will be created How to test git clone repository cd expose-controller

Dec 23, 2021

A kubernetes plugin which enables dynamically add or remove GPU resources for a running Pod

A kubernetes plugin which enables dynamically add or remove GPU resources for a running Pod

GPU Mounter GPU Mounter is a kubernetes plugin which enables add or remove GPU resources for running Pods. This Introduction(In Chinese) is recommende

Jan 5, 2023

A curated list of awesome Kubernetes tools and resources.

Awesome Kubernetes Resources A curated list of awesome Kubernetes tools and resources. Inspired by awesome list and donnemartin/awesome-aws. The Fiery

Jan 2, 2023

A cli that exposes your local resources to kubernetes

A cli that exposes your local resources to kubernetes

ktunnel Expose your local resources to kubernetes 📝 Table of Contents About Getting Started Usage Documentation Contributing Authors Acknowledgments

Jan 7, 2023

Annotated and kubez-autoscaler-controller will maintain the HPA automatically for kubernetes resources.

Kubez-autoscaler Overview kubez-autoscaler 通过为 deployment / statefulset 添加 annotations 的方式,自动维护对应 HorizontalPodAutoscaler 的生命周期. Prerequisites 在 kuber

Jan 2, 2023

nano-gpu-agent is a Kubernetes device plugin for GPU resources allocation on node.

nano-gpu-agent is a Kubernetes device plugin for GPU resources allocation on node.

Nano GPU Agent About this Project Nano GPU Agent is a Kubernetes device plugin implement for gpu allocation and use in container. It runs as a Daemons

Dec 29, 2022
Bootstrap curated Kubernetes stacks. Logging, metrics, ingress and more - delivered with gitops.

Gimlet Stack Bootstrap curated Kubernetes stacks. Logging, metrics, ingress and more - delivered with gitops. You can install logging aggregators, met

Dec 1, 2021
An Ingress controller for Kubernetes using NGINX as a reverse proxy and load balancer

NGINX Ingress Controller Overview ingress-nginx is an Ingress controller for Kubernetes using NGINX as a reverse proxy and load balancer. Learn more a

Nov 15, 2021
kubectl plugin for generating nginx-ingress compatible basic-auth secrets on kubernetes clusters

kubectl-htpasswd kubectl plugin for easily generating hashed basic auth secrets. Supported hash algorithms bcrypt Examples Create the secret on the cl

Jul 17, 2022
Kubernetes-native automatic dashboard for Ingress
Kubernetes-native automatic dashboard for Ingress

ingress-dashboard Automatic dashboard generation for Ingress objects. Features: No JS Supports OIDC (Keycloak, Google, Okta, ...) and Basic authorizat

Oct 20, 2022
Sesame: an Ingress controller for Kubernetes that works by deploying the Envoy proxy as a reverse proxy and load balancer

Sesame Overview Sesame is an Ingress controller for Kubernetes that works by dep

Dec 28, 2021
A k8s vault webhook is a Kubernetes webhook that can inject secrets into Kubernetes resources by connecting to multiple secret managers
A k8s vault webhook is a Kubernetes webhook that can inject secrets into Kubernetes resources by connecting to multiple secret managers

k8s-vault-webhook is a Kubernetes admission webhook which listen for the events related to Kubernetes resources for injecting secret directly from sec

Oct 15, 2022
Traefik-redirect-operator is created to substitute manual effort of creating an ingress and service type External.
Traefik-redirect-operator is created to substitute manual effort of creating an ingress and service type External.

Overview Traefik Redirect Operator is used to help creating a combination of Ingress of Traefik controller along with Service's ExternalName type. The

Sep 22, 2021
Simple HPA base NGINX Ingress

Simple HPA Base Ingress Access Log Support NGINX Ingress How to Use Requirement Kubernetes NGINX Ingress Quick Start 1. Deploy Change deploy.yamlENV,

Dec 12, 2022
A Pulumi NGINX Ingress Controller component

Pulumi NGINX Ingress Controller Component This repo contains the Pulumi NGINX Ingress Controller component for Kubernetes. This ingress controller use

Aug 10, 2022
Docker Swarm Ingress service based on OpenResty with automatic Let's Encrypt SSL provisioning

Ingress Service for Docker Swarm Swarm Ingress OpenResty is a ingress service for Docker in Swarm mode that makes deploying microservices easy. It con

Jun 23, 2022