gloo
gloo copied to clipboard
test/kube/e2e: Expand deployer tests
Description
Expand the e2e tests for our deployer
Context
Migrate Enterprise Tests
There were tests defined in our Enterprise project (https://github.com/solo-io/solo-projects/tree/main/test/kube2e/k8sgateway) that ought to be defined here, and executed from both projects.
Update Example Test Suite
This is a follow-up to https://github.com/solo-io/gloo/pull/9401, and within there, there was some feedback around naming and functionality.
Since this suite is read-only, and useful for devs, you can run it locally, using previously released images:
CLUSTER_NAME=kind TEST_PKG=test/kubernetes/e2e/example RELEASED_VERSION=1.17.0-beta20 GO_TEST_USER_FLAGS='-v' make go-test
ok github.com/solo-io/gloo/test/kubernetes/e2e/example 115.479s
Interesting decisions
Testing steps
- The tests pass in CI
- I also ran these tests locally:
CLUSTER_NAME=kind TEST_PKG=test/kubernetes/e2e/k8sgateway RELEASED_VERSION=1.17.0-beta20 GO_TEST_USER_FLAGS='-v' make go-test
Notes for reviewers
Checklist:
- [x] I have performed a self-review of my own code
- [x] I have commented my code, particularly in hard-to-understand areas
- [x] I have made corresponding changes to the documentation
- [x] I have added tests that prove my fix is effective or that my feature works
Visit the preview URL for this PR (updated for commit ebe46ec):
https://gloo-edge--pr9405-sam-e2e-tests-deploy-ufot5xxf.web.app
(expires Sat, 04 May 2024 18:57:18 GMT)
🔥 via Firebase Hosting GitHub Action 🌎
Sign: 77c2b86e287749579b7ff9cadb81e099042ef677
Issues linked to changelog: https://github.com/solo-io/solo-projects/issues/6089
bulldozer??