mirror of https://github.com/linkerd/linkerd2.git
f04edae759
linkerd2-proxy-api v0.6.0 adds support for inbound proxies to discover route configurations based on the Gateway API HTTPRoute types. This change updates the policy controller to index `gateway.networking.k8s.io/v1beta` `HTTPRoute` types to discover these policies from the Kubernetes API. `HTTPRoute` resources may target `Server` resources (as a `parentRef`) to attach policies to an inbound proxy. When no routes are configured, a default route is synthesized to allow traffic; but when at least one route attaches to a server, only requests that match a route are permitted (other requests are failed with a 404). Only the *core* subset of the `HTTPRoute` filters are supported: `RequestRedirect` and `RequestHeaderModifier`. Backends may *not* be configured on these routes (since they may only apply to inbound/server- side proxies). No `status` updates are currently performed on these `HTTPRoute` resources. This change does not yet allow `AuthorizationPolicy` resources to target `HTTPRoute` resources. This will be added in a follow-up change. Signed-off-by: Alex Leong <alex@buoyant.io> Co-authored-by: Oliver Gould <ver@buoyant.io> |
||
|---|---|---|
| .. | ||
| core | ||
| grpc | ||
| k8s | ||
| src | ||
| .dockerignore | ||
| Cargo.toml | ||
| amd64.dockerfile | ||
| arm.dockerfile | ||
| arm64.dockerfile | ||