Skip to content

source and gateways in match condition #276

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 3 commits into from
Dec 15, 2017
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
27 changes: 5 additions & 22 deletions routing/v1alpha2/gateway.pb.go

Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.

27 changes: 5 additions & 22 deletions routing/v1alpha2/gateway.proto
Original file line number Diff line number Diff line change
Expand Up @@ -86,6 +86,7 @@ package istio.routing.v1alpha2;
// - eu.bookinfo.com
// gateways:
// - my-gateway
// - mesh # applies to all the sidecars in the mesh
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

You mean for the internal service-to-service traffic ?

// http:
// - match:
// - headers:
Expand All @@ -109,8 +110,10 @@ package istio.routing.v1alpha2;
// name: reviews.qa
// weight: 20
//
// The following routing rule forwards traffic arriving at (external)
// port 2379 from 172.17.16.* subnet to internal Mongo server on port 5555.
// The following routing rule forwards traffic arriving at (external) port
// 2379 from 172.17.16.0/24 subnet to internal Mongo server on port 5555. This
// rule is not applicable internally in the mesh as the gateway list omits
// the reserved name "mesh".
//
// apiVersion: config.istio.io/v1alpha2
// kind: RouteRule
Expand All @@ -130,26 +133,6 @@ package istio.routing.v1alpha2;
// - destination:
// name: mongo.prod
//
// By default, if there is no wildcard, HTTP requests for unknown domains
// or requests that have no matching route rule will respond with a 404. If
// a specific default behavior is desired at the ingress, add a route rule
// with a wildcard host and the desired backend. For example, the following
// wildcard routing rule routes all traffic to homepage.prod by default.
//
// apiVersion: config.istio.io/v1alpha2
// kind: RouteRule
// metadata:
// name: default-ingress
// spec:
// hosts:
// - *
// gateways:
// - my-gateway
// http:
// - route:
// - destination:
// name: homepage.prod
//
message Gateway {
// REQUIRED: A list of server specifications.
repeated Server servers = 1;
Expand Down
Loading