solo-io/gloo v1.18.0-beta16

on GitHub

Breaking Changes

• Fix for issue where a missing TLS secret was treated by validation as an error, potentially bringing down the entire HTTPS gateway if the gloo pod restarts while in this bad state. This is a breaking change in the default behavior of validation.
  To disable this behavior, use the helm setting gateway.validation.warnMissingTlsSecret=false or the same field on the Settings CR. This field has no effect if allowWarnings is false or acceptAllResources is true. (#6957)

Helm Changes

• Ensure that gateway-proxy deployments respect the gatewayProxy.NAME.kind.deployment.priorityClassName field. This API allows you to set the PriorityClassName for gateway-proxy Pods. This is already supported on all other Gloo deployments. (#8677)
• New field gateway.validation.warnMissingTlsSecret controls whether missing TLS secrets referenced in SslConfig and UpstreamSslConfig will be treated as a warning instead of an error during validation. Defaults to true. This field has no effect if allowWarnings is false or acceptAllResources is true. (#6957)

Fixes

• Set the 'message' field on various HTTPRoute conditions to enable easier troubleshooting (#9859)
• Support defining the PriorityClassName on a GatewayProxy deployment. This allows users to attach pods to PriorityClasses (https://kubernetes.io/docs/concepts/scheduling-eviction/pod-priority-preemption/) (#9010)