solo-io/gloo v1.14.0-beta18

on GitHub

This release build failed.

Dependency Bumps

• solo-io/skv2 has been upgraded to v0.29.2.
• helm/helm has been upgraded to v3.11.2.
• k8s.io/api has been upgraded to v0.25.8.
• k8s.io/apiextensions-apiserver has been upgraded to v0.25.8.
• k8s.io/apimachinery has been upgraded to v0.25.8.
• k8s.io/cli-runtime has been upgraded to v0.25.8.
• k8s.io/client-go has been upgraded to v0.25.8.
• k8s.io/code-generator has been upgraded to v0.25.8.
• k8s.io/component-base has been upgraded to v0.25.8.
• k8s.io/kubectl has been upgraded to v0.25.8.
• k8s.io/metrics has been upgraded to v0.25.8.
• k8s.io/kube-openapi has been upgraded to v0.0.0-20220803162953-67bda5d908f1.

Breaking Changes

• Adds support for running Gloo Edge (OSS) on Kubernetes 1.25 and removes support for 1.22 and below. Notable changes include PodDisruptionBudget moving from policy/v1beta1 to policy/v1, and the gloo helm chart OCI registry path changing from gcr.io/solo-public/gloo-helm to gcr.io/solo-public/gloo-helm/gloo. (#6833)

New Features

• Setting global.glooRbac.namespaced=true now also constrains the certgen jobs access permissions to secrets from the entire cluster to just those in the gloo install namespace. Also the original role (gloo-gateway-secret-create-vwc-update) was split into two separate roles (gloo-gateway-secret-create and gloo-gateway-vwc-update) as gloo-gateway-vwc-update needs to access cluster scoped validatingWebhookConfigs. gloo-gateway-secret-create-vwc-update no longer exists. (#5960)

Fixes

• In the Settings object, you can configure gateway.isolateVirtualHostsBySslConfig to ensure that VirtualHosts, secured with SslConfig, are published to unique filter chains. We attempt to merge VirtualServices which share the same SslConfiguration. There was a bug in the merge logic that caused VirtualServices to be dropped from the Proxy, and only the last matching VirtualService would remain, if you were using isolateVirtualHostsBySslConfig=true. (#7739)