Prefix is an Ingress path type that matches URL paths by their slash-delimited prefixes.
Prefix is an Ingress path type that matches URL paths by slash-delimited prefixes. Ingress controllers use these rules to route external HTTP or HTTPS requests to internal Services. section 6.3
Distinguish Prefix from related Ingress path behavior:
Use Prefix for path-based routing such as directing requests under /api to one Service. section 6.3
Use Exact when the complete path string must match instead of a URL prefix. section 6.3
Define the path rule in an Ingress resource and rely on the ingress controller to interpret it. section 6.3
How Acing the Certified Kubernetes Administrator Exam, Second Edition covers it
How deep it goes
Defines prefix matching and contrasts it with Exact, but does not descend into controller matching internals.
Examples
Uses /api routing as a path-based example and contrasts it with exact-path matching.
What it assumes
Assumes understanding of Services and introduces their role as Ingress backends for external traffic.
What you can do after
Apply it when creating Ingress rules that route URL path prefixes to Kubernetes Services.
How it connects
Connects Ingress path rules with ingress controllers, Services, HTTP request paths, hostnames, and Exact matching.
trieuses · A trie is a tree-based data structure that stores sequences by sharing nodes for common prefixes, enabling efficient key and prefix lookup.
pathType fieldkind of · The pathType field is an Ingress field specifying how a request path is matched for routing.
linear time complexitymeasured by · Linear time complexity is an asymptotic running-time growth rate proportional to input size, or to the combined sizes of multiple inputs, up to a constant factor.
This explainer was generated by Manning's knowledge graph from the text of Acing the Certified Kubernetes Administrator Exam, Second Edition. The section links point to the parts of the book it draws on.
