Skip to content
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

Stream Routing and Service Mesh #4009

Merged
merged 16 commits into from Nov 22, 2018

Conversation

Projects
None yet
4 participants
@hishamhm
Copy link
Member

hishamhm commented Nov 22, 2018

No description provided.

thibaultcha and others added some commits Oct 26, 2018

feat(schema) allow conditional validators to receive more fields
Allowing conditional validators to receive fields like `elements`,
`keys`, and `values` enabled the use of conditional validators on
composite types. E.g.:

```
conditional = {
  if_field = "protocols",
  if_match = { elements = { type = "string", one_of = { "http", "https" },
  -- ...
}
```
feat(schema) allow aggregates on base types in entities
Relax the no aggregates on base types rules for entities, so that Routes
can implement the new `sources`/`destinations` matching attributes,
which are arrays of of records.
feat(schema) add `cidr` typedef
Factored out of ip-restriction plugin
feat(db) enable read-before-write on entity checks
This avoids a breaking change in the behavior of PATCH when using HTTP routes
(namely, always requiring the `protocols` attribute to be given explicitly
when updating any routing criteria), after additional conditional entity
checks are added to the Routes entity in preparation for stream support.
feat(schema) tcp/tls support in Routes and Services
Adds support for `tcp` and `tls` to the `protocols` set of the Routes
entity, and introduces new fields, `snis`, `sources` and `destinations`,
which can be used only when `tcp` or `tls` are set in protocols.

Adds support for `tcp` and `tls` to the `protocol` field of the Services
entity.
feat(router) support for IP and TLS routing properties
The router is now able to select Routes based on the new IP and TLS
attributes:

  - source ip and/or port
  - destination ip and/or port
  - SNI (ssl server name indication extension)

@hishamhm hishamhm force-pushed the feat/service-mesh branch from df3002c to 1e50478 Nov 22, 2018

@hishamhm hishamhm force-pushed the feat/service-mesh branch from 1e50478 to 9143dfd Nov 22, 2018

@bungle

bungle approved these changes Nov 22, 2018

@hishamhm hishamhm merged commit 3091afe into next Nov 22, 2018

3 checks passed

continuous-integration/travis-ci/pr The Travis CI build passed
Details
continuous-integration/travis-ci/push The Travis CI build passed
Details
license/cla All CLA requirements met.

@hishamhm hishamhm deleted the feat/service-mesh branch Nov 22, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.