-
Notifications
You must be signed in to change notification settings - Fork 40
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
Update proxy wasm cpp sdk to work with envoy 1.16.x #178
Conversation
Stop running duplicate tests for Gloo in the Istio e2e suites
# see what's in the cluster if we failed | ||
git diff | ||
kubectl get all -A | ||
kubectl get configmaps -A |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nit: we should probably move this into a script for long term maintenance
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
or a make target
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
just a thought, i realize we have this elsewhere (and i'm not saying now is the ideal time to refactor)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I agree, good call. Also in general I think we can do a bunch of cleanup on this GH Actions file to streamline it a bit. I'm thinking we can use the matrix approach we use elsewhere. I tried a few performance optimizations to get the build time down in this PR (as you might see from the commits) but most of them ended up maxing out the CPU of the kind cluster in the e2e test machines and ultimately being rolled back.
Tested against the latest Gloo 1.5.0-beta (master) updated to use an envoy based on this PR - https://github.com/solo-io/envoy-gloo/pull/83/files and confirmed it's working.
For code reviewing, most of the changes in the diff are from moving the
examples
folder down a level into thecli
package.Things to look at when reviewing:
envoy-wasm
.Fixes #177
Fixes #145