Menene Ingress kuma yaya yake tuƙa zirga-zirgar waje zuwa Services?

Question

IT Interview Practice · Accepted Answer

**Ingress** wani abu ne na Kubernetes da ke bayyana **dokokin tuƙawar HTTP/HTTPS** — yana daidaita sunayen host da URL paths zuwa **Services** na baya. **Ingress Controller** ne ke cika shi (nginx, Traefik, cloud gateways) kuma yana ba ka ƙofar shiga ɗaya, TLS termination, da tuƙawar host/path maimakon LoadBalancer ga kowane service.

## Matsalar da Ingress ke warwarewa

```text
Fito da service da yawa da type: LoadBalancer na nufin LB na cloud DA YAWA (da IP na jama'a)
— tsada, kuma babu tuƙawar hostname/path da aka raba ko TLS.
Ingress yana ba da ƙofar shiga ƊAYA da ke tuƙawa ta host & path zuwa ClusterIP Services na ciki.
```

## Yadda yake haɗuwa

```text
      Internet
         │
   ┌─────┴──────────────┐
   │ Ingress Controller │  (Pod, misali nginx; galibi bayan LoadBalancer ƊAYA)
   │  yana karanta dokokin Ingress│
   └─────┬──────────────┘
         │ yana tuƙawa ta host / path
   ┌─────┼───────────────┬───────────────┐
   ▼                     ▼               ▼
 Service: web        Service: api    Service: admin  (duk ClusterIP)
   │                     │               │
 Pods                  Pods            Pods

Ingress (dokoki)  ≠  Ingress Controller (proxy mai gudana da ke tilasta su)
```

## Manifest na Ingress

```yaml
apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
  name: app-ingress
  annotations:
    nginx.ingress.kubernetes.io/rewrite-target: /
spec:
  ingressClassName: nginx
  tls:
    - hosts: [shop.example.com]
      secretName: shop-tls        # TLS cert/key da aka ajiye a Secret
  rules:
    - host: shop.example.com
      http:
        paths:
          - path: /api
            pathType: Prefix
            backend:
              service:
                name: api
                port: { number: 80 }
          - path: /
            pathType: Prefix
            backend:
              service:
                name: web
                port: { number: 80 }
```

```text
shop.example.com/api/... → Service "api" → api Pods
shop.example.com/...     → Service "web" → web Pods
Ana yanke TLS a controller ta amfani da cert cikin Secret "shop-tls".
```

## Muhimman batutuwa

```text
• DOLE ne ka gudanar da Ingress Controller — abin Ingress kaɗai ba ya yin komai.
• ingressClassName yana zaɓar wanne controller ke sarrafa dokokin.
• Ingress na HTTP/HTTPS (L7) ne kawai. Ga tsantsar TCP/UDP yi amfani da Service ko Gateway API.
• Sabon Gateway API shine magaji mai tasowa da tuƙawa mai wadata, wanda ya danganci matsayi.
```

```bash
kubectl get ingress                  # jera dokoki, hosts, adireshi
kubectl describe ingress app-ingress # duba backends & abubuwan da suka faru
```

## Me ya sa yake da muhimmanci

Ingress shine daidaitacciyar hanya don fito da aikace-aikacen HTTP/HTTPS zuwa duniyar waje a kan Kubernetes, don haka fahimtar sa ilimin hanyar sadarwa ne mai mahimmanci ga injiniyoyi na tsaka-tsaki. Matsalar da yake warwarewa takamaimai ce kuma na yawaita: fito da service da yawa ta `type: LoadBalancer` na nufin samar da load balancer na cloud daban da IP na jama'a ga kowane service — tsada kuma ba tare da tuƙawar hostname da aka raba ko TLS ba — yayin da **Ingress** ke ba ka ƙofar shiga ɗaya wanda ke tuƙawa ta **host da path** zuwa ClusterIP Services na ciki ya kuma yanke **TLS** a tsakiya. Bambancin da ke tafka wa mutane shine tsakanin **abin Ingress** (dokokin tuƙawa na bayyanawa) da **Ingress Controller** (ainihin proxy mai gudana — nginx, Traefik, cloud gateway — da ke kallon waɗannan dokoki ya kuma tilasta su); dokokin ba sa yin komai ba tare da controller da aka girka ba, kuma `ingressClassName` yana zaɓar wanne controller ke sarrafa su. Fahimtar cewa Ingress yana aiki a **L7 (HTTP/HTTPS kawai)** — don haka tsantsar TCP/UDP yana buƙatar Service ko sabon Gateway API — kuma cewa **Gateway API** shine magaji mai tasowa, mai bayyanawa, yana nuna ilimi na yanzu na ainihin duniya. Saboda kusan kowane aikace-aikace da ke fuskantar mai amfani a Kubernetes yana buƙatar tuƙawar host/path da TLS daga ƙofar shiga ɗaya, kuma saboda bambancin abu-da-controller wani tushen ruɗani ne mai yawaita a duka hira da aiki, fahimtar Ingress sosai na tushe ne don fito da gudanar da web workload a kan cluster.

Matsalar da Ingress ke warwarewa

Yadda yake haɗuwa

Manifest na Ingress

Muhimman batutuwa

Me ya sa yake da muhimmanci

Tambayoyi masu alaƙa