Skip to content

v1.18.4

Latest
Latest
Compare
Choose a tag to compare
@EItanya EItanya released this 12 Jan 03:05
v1.18.4
f69e899
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Learn about vigilant mode.

Fixes

  • Expose spawn_upstream_span on the tracing API. This setting tells envoy to spawn a new span for each upstream request. (solo-io/solo-projects#6748)
  • Add a new Ports field to the GatewayParameters Kube.Service Spec in order to allow admin users to configure additional information about the ports that the Gateway should listen on. This is useful if the user wants to specify a static NodePort (solo-io/solo-projects#7504)
  • Add new SSL options to GatewayTLSConfig to enable configuring additional SSL options which were previously available using the edge API. This includes cipher suites, minimum TLS version, maximum TLS version, client certificate validation, and one way TLS. (solo-io/solo-projects#7505)
  • gateway2: allow route delegation using wellknown label

There is a product requirement to enable users to use
a label to select HTTPRoutes to delegate to instead
of GVK ref to other HTTPRoutes (includes wildcards).

To strike a balance between flexibility and performance,
this change implements the proposal to use a well known
label delegation.gateway.solo.io/label=<value> to
allow users to delegate to other HTTPRoutes using a label.
HTTPRoutes are indexed using this well known label key that
enable O(1) lookups of routes matching this label value. (solo-io/solo-projects#7626)

  • Add ability to configure proxy service External Traffic Policy via Gateway Params (k8sgateway#9879)
  • Bumps Gateway API dependencies from v1.2.0 to v1.2.1. (#10546)
  • When merging parent-child policies, the merging should allow child
    policies to augment parent policies such that fields unset on the
    parent can be set by the child. There is a bug when using policy
    override capability with route delegation that disallows this when
    the annotation specifies non-wildcard fields, such that even if
    a field is unset by the parent only the fields specified in the
    override annotation are merged in - which is incorrect because
    the annotation only applies to fields that are being overriden
    (set by the parent). This change fixes the bug. (solo-io/solo-projects#7601)
Assets 12
Loading