ci: scaffold e2e testing framework infrastructure #763
+388
−6
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
google-oss-prow
bot
added
area/controller
andyatmiami
force-pushed
the
test/full-e2e-scaffold
branch
2 times, most recently
from
50ea8f9 to
1428a84
Compare
Contributor
Author
|
/ok-to-test |
This commit establishes the foundational infrastructure for end-to-end
testing of the workspaces components. This is an intermediate step that
sets up the testing framework; no actual test execution is implemented
yet and will be added in subsequent work.
Changes include:
- Add new `testing/` directory with Makefile and setup scripts:
* `setup-kind.sh`: Automated Kind cluster creation and configuration
* `setup-cert-manager.sh`: Cert-manager installation (v1.12.13 LTS)
* `setup-istio.sh`: Istio service mesh installation
* Makefile targets for cluster setup, component deployment, and
e2e test execution (currently placeholder with TODO)
- Add GitHub Actions workflow (`.github/workflows/ws-e2e-test.yml`):
* Triggers on pushes to main branches and PRs affecting workspaces
* Sets up Go environment and Kind cluster
* Executes local-e2e target (placeholder for future test implementation)
- Update workspace Makefiles (backend, controller, frontend):
* Modify deploy targets to use `.output/` directories for kustomize
operations, preventing modification of source manifests
- Update .gitignore files:
* Add `.output/` directories to prevent committing generated
kustomize artifacts
The framework enables automated deployment of all three components
(controller, backend, frontend) to a Kind cluster with cert-manager
and Istio pre-configured, providing the foundation for comprehensive
e2e test scenarios in future commits.
Signed-off-by: Andy Stoneberg <[email protected]>
andyatmiami
force-pushed
the
test/full-e2e-scaffold
branch
from
4dccdd2 to
0f1461d
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
ℹ️ NO GH ISSUE
This commit establishes the foundational infrastructure for end-to-end testing of the workspaces components. This is an intermediate step that sets up the testing framework; no actual test execution is implemented yet and will be added in subsequent work.
Changes include:
Add new
testing/directory with Makefile and setup scripts:setup-kind.sh: Automated Kind cluster creation and configurationsetup-cert-manager.sh: Cert-manager installation (v1.12.13 LTS)setup-istio.sh: Istio service mesh installationAdd GitHub Actions workflow (
.github/workflows/ws-e2e-test.yml):Update workspace Makefiles (backend, controller, frontend):
.output/directories for kustomize operations, preventing modification of source manifestsUpdate .gitignore files:
.output/directories to prevent committing generated kustomize artifactsThe framework enables automated deployment of all three components (controller, backend, frontend) to a Kind cluster with cert-manager and Istio pre-configured, providing the foundation for comprehensive e2e test scenarios in future commits.