Skip to content

Instantly share code, notes, and snippets.

@seifrajhi

seifrajhi/gateway_api_vs_ingress_table.md

Created March 16, 2024 08:52
Show Gist options
  • Save seifrajhi/f1f731a121da6c1e55c717787bb06344 to your computer and use it in GitHub Desktop.
Save seifrajhi/f1f731a121da6c1e55c717787bb06344 to your computer and use it in GitHub Desktop.
Download ZIP
Gateway API vs. Ingress
Raw
gateway_api_vs_ingress_table.md

Gateway API vs. Ingress

Feature Ingress Gateway API
Traffic Routing Basic HTTP routing and advanced routing features are not natively supported. Header-based matching, traffic weighting, typed routes, and different backend types.
Extensibility Achieved with custom annotations through a vendor-specific approach. Allows users to define their own custom resources.
Standardization Individual implementations with inconsistencies across different Ingress controllers. Universal specification that is supported across various implementations.
Role-Based Access Control Does not natively let different teams manage different configuration sections. Allows individual teams to manage their traffic while cluster operators set the policies.
Protocol Support To expose non-HTTP services to the internet, different Kubernetes resources are needed. Extensive protocol support.
Security Basic support for TLS termination. Generally facilitates enhanced security controls which the cluster operators define.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment