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
OSSM-1955 Merge Envoy's 1.20 release branch #199
OSSM-1955 Merge Envoy's 1.20 release branch #199
Conversation
Signed-off-by: Ryan Northey <ryan@synca.io>
…49d2923f35d6` (#22283) docker: Bump `distroless/base-debian11:nonroot` -> `49d2923f35d6` Signed-off-by: Ryan Northey <ryan@synca.io>
repo: Release `1.20.7` Signed-off-by: Ryan Northey <ryan@synca.io>
Signed-off-by: Otto van der Schaaf <ovanders@redhat.com>
Some certificates have expired, causing test failures. Signed-off-by: Otto van der Schaaf <ovanders@redhat.com>
…stra-2.2-upstream-1.20
Annoyingly, the CI logs have:
I'm going to the certificate regeneration script but commit just the four new files related the certs specific to this test. I suspect some inconsistency crept in as generating these may depend on the other certificates, and therefore the new ones need to be regenerated as well. |
As we pulled in refreshed certificates from upstream, we now need to do a partial refresh for the ones introduced in our 0150925. (The refresh from upstream also touched the ca & intermediate ca, which means that the certificates we introduced ourselves are now inconsistent with respect to who signed them -- thus causing test failures). Signed-off-by: Otto van der Schaaf <ovanders@redhat.com>
1c76c9e
to
082adf4
Compare
Ugh, the failure mode for |
LGTM |
Merge branch
release/v1.20
fromenvoyproxy/envoy
.This should resolve CI structurally failing as observed in recent pull requests,
by pulling in a change that updates expired certificates: bfb9b97