[Native K8s]: E2E test implementation in IAD #31
Merged
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
* Implemented terraform scripts for deployment and teardown of operator + sample app * Implemented workflow to run the terraform and validation + emit metrics * Implemented canary to call this workflow every 15 minutes * Added validations for K8s use case to validator
harrryr
reviewed
Mar 26, 2024
harrryr
approved these changes
Mar 26, 2024
harrryr
reviewed
Mar 27, 2024
harrryr
reviewed
Mar 27, 2024
majanjua-amzn
force-pushed
the
k8s
branch
2 times, most recently
from
5e67a36 to
03d95c8
Compare
zzhlogin
reviewed
Apr 12, 2024
zzhlogin
approved these changes
Apr 13, 2024
harrryr
reviewed
Apr 15, 2024
lisguo
reviewed
Apr 16, 2024
majanjua-amzn
force-pushed
the
k8s
branch
2 times, most recently
from
fd161bb to
18ac4a6
Compare
lisguo
approved these changes
Apr 17, 2024
harrryr
approved these changes
Apr 17, 2024
harrryr
approved these changes
Apr 17, 2024
zzhlogin
pushed a commit
to zzhlogin/aws-application-signals-test-framework
that referenced
this pull request
Jun 6, 2024
[K8s]: E2E test implementation in IAD
zzhlogin
pushed a commit
to zzhlogin/aws-application-signals-test-framework
that referenced
this pull request
Jun 6, 2024
[K8s]: E2E test implementation in IAD
zzhlogin
pushed a commit
to zzhlogin/aws-application-signals-test-framework
that referenced
this pull request
Jun 6, 2024
[K8s]: E2E test implementation in IAD
zzhlogin
pushed a commit
to zzhlogin/aws-application-signals-test-framework
that referenced
this pull request
Jun 6, 2024
[K8s]: E2E test implementation in IAD
georgeboc
pushed a commit
to georgeboc/aws-application-signals-test-framework
that referenced
this pull request
Jul 8, 2024
…vability#31) *Description of changes:* Added a random-traffic-generator for the Python Sample App. More details can be found in the README under `aws-otel-python-instrumentation/sample-applications/vehicle-dealership-sample-app/random-traffic-generator`. The traffic generator generates the following traffic: 1. Every minute, sends a single POST request to the VehicleInventoryApp and sends a single GET request. 2. Every hour, sends a burst of requests: 5 POST requests to the VehicleInventoryApp and 5 GET requests. 3. Every 5 minutes, sleeps for random amount of time between 30-60 seconds and then sends a GET request to the VehicleInventoryApp with a random throttle param between 5-20 seconds. The backend reads that throttle param and simulates throttling for that amount of time before responding to the request. 4. Every 5 minutes, sleeps for random amount of time between 30-60 seconds and then sends a GET request to the VehicleInventoryApp with an invalid car id to trigger 404 error. 5. Every 5 minutes, sleeps for random amount of time between 30-60 seconds and then sends a GET request to the ImageServiceApp with a non existent image name to trigger 500 error due to S3 Error: "An error occurred (NoSuchKey) when calling the GetObject operation: The specified key does not exist." By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
We want to test app signals on native kubernetes.
I have set up a native K8s cluster in IAD using kubeadm running on two EC2 instances (a master and worker node). The cluster is set to be clean (no operator or sample app) while the test is not running. Due to the cluster set up being quite complicated, this test is only set up in IAD as of now. Future effort may be assigned to extending this to all regions.
This test adds the requirement for the following IAM policies to be added the the EC2 IAM instance profile used in the test case:
AmazonS3FullAccess(instead ofAmazonS3ReadOnlyAccess): Used to push and pull the deployment files for the sample application using the existing e2e test related S3 bucketAmazonSSMFullAccess: Used to push and pull the remote service pod IP (this cannot be emitted from the SSH connection to the terraform, and this alternative solution provides a way for us to emit and collect this information)AWSAppRunnerServicePolicyForECRAccess: Used to pull the ECR images for the main and remote service of our sample applicationThis change is already done and verified in the IAD account.
Description of changes:
TESTenvironment variable from ec2 test caseTesting:
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.