Skip to main content

GAMMA Initiative — The Future of Service Mesh Integration

4.1 What is GAMMA?​

GAMMA (Gateway API for Mesh Management and Administration) is an initiative that extends Gateway API into the service mesh domain.

  • GA achieved: Gateway API v1.1.0 (October 2025)
  • Unified scope: North-South (ingress) + East-West (service mesh) traffic
  • Core concept: Previously, ingress controllers and service meshes had entirely separate configuration systems — GAMMA unifies them under a single API
  • Role-based configuration: Applies Gateway API's role separation principles equally to mesh traffic

With GAMMA, cluster operators no longer need to learn and manage two different APIs. Both ingress and mesh can be managed with the same Gateway API resources.

4.2 Core Goals & Mesh Configuration Patterns​

GAMMA Initiative 핵심 개념
4가지 핵심 목표 & 메시 구성 패턴

4가지 핵심 목표

🎯
통합 API
인그레스와 서비스 메시를 동일한 Gateway API 리소스로 관리
👥
역할 기반 구성
Gateway API의 역할 분리 원칙을 메시 트래픽에도 동일하게 적용
⚡
최소 API 변경
기존 Gateway API에 최소한의 변경만 추가하여 메시 기능 지원
🔄
구현체 간 일관성
Istio, Cilium, Linkerd 등 다양한 메시에서 동일한 API 사용

메시 구성 패턴

❌ 기존 방식
Ingress Controller (North-South만)
Service Mesh (East-West만)
별도 설정 체계
▼ GAMMA Initiative ▼
✅ GAMMA 방식
Gateway API (통합 API)
North-South (parentRef: Gateway)
East-West (parentRef: Service)
단일 API로 통합

설정 방식 비교

기존 방식
Ingress (별도 CRD)
Ingress/VirtualService 등
Mesh (별도 CRD)
ServiceEntry/DestinationRule 등
→ 2가지 API 학습 필요
GAMMA 방식
HTTPRoute (통합)
• parentRef: Gateway
• parentRef: Service
→ 1가지 API로 통합

GAMMA HTTPRoute 예제

Service에 직접 L7 정책 적용
apiVersion: gateway.networking.k8s.io/v1
kind: HTTPRoute
metadata:
  name: service-b-retry
  namespace: production
spec:
  parentRefs:
    - group: ""
      kind: Service
      name: service-b    # Gateway가 아닌 Service에 attach
  rules:
    - backendRefs:
        - name: service-b
          port: 8080
      timeouts:
        request: 10s
      retry:
        attempts: 3
        backoff: 100ms
      # Service B로 가는 트래픽에 재시도/타임아웃 적용

4.3 GAMMA Support Status​

🔄 GAMMA 구현체 비교
기능, 데이터 플레인, 리소스 오버헤드별 상세 비교 — 클릭하여 상세 보기
AWS VPC Lattice + ACK✅ GAAWS 관리형 (VPC 레벨)❌ 불필요▼
Istio Ambient Mode✅ GAztunnel (L4) + waypoint (L7)❌ 불필요 (Ambient)▼
Cilium✅ GAeBPF + Envoy (L7)❌ 불필요 (eBPF)▼
Linkerd✅ Betalinkerd2-proxy (Rust)✅ 필요 (경량)▼
kGateway (Solo.io)✅ GAEnvoy❌ 불필요▼
GAMMA in AWS Environments

In AWS environments, VPC Lattice + ACK can implement GAMMA patterns without sidecars. Provides fully managed service mesh capabilities including IAM-based mTLS, CloudWatch/X-Ray observability, and fault injection through AWS FIS.

4.4 Advantages of GAMMA​

1. Reduced Learning Curve​

Teams only need to learn one API (Gateway API) to manage both ingress and mesh.

2. Configuration Consistency​

Manage both North-South/East-West traffic with the same YAML structure and patterns.

# Ingress (North-South)
spec:
  parentRefs:
    - kind: Gateway
      name: external-gateway

# Mesh (East-West)
spec:
  parentRefs:
    - kind: Service
      name: backend-service

3. Role-Based Separation​

Clear responsibility separation — infra teams manage Gateways, dev teams manage HTTPRoutes — applies equally to mesh traffic.

4. Vendor Neutrality​

Multiple mesh implementations can be managed with the same API, preventing vendor lock-in.