-
Notifications
You must be signed in to change notification settings - Fork 580
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
e2e tests #606
e2e tests #606
Conversation
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: akutz If they are not already assigned, you can assign the PR to them by writing The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
b73a326
to
654721e
Compare
c46f48d
to
031bc0a
Compare
/hold cancel |
This patch deploys a new Boskos janitor as a service in the same cluster running Prow. The new service is named `boskos-janitor-aws`. Related to kubernetes-sigs/cluster-api-provider-aws#272 and kubernetes-sigs/cluster-api-provider-aws#606. /area boskos
This patch deploys a new Boskos janitor as a service in the same cluster running Prow. The new service is named `boskos-janitor-aws`. Related to kubernetes-sigs/cluster-api-provider-aws#272 and kubernetes-sigs/cluster-api-provider-aws#606. /area boskos
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.
Hi Jason, Regarding the PR description, there will be no single PR in this repo that fixes 272 as it will take a series of PRs across this and test infra. That’s why I said it partially fixed the issue. To me it’s a problem with the fixes notation that it only applies to a single issue. How do you recommend we use that when a resolution takes more than one PR across multiple repos? That would typically be an epic, but I don’t see that you’ve got ZenHub or GH projects set up to track epics. |
.PHONY: integration | ||
integration: generate verify ## Run integraion tests | ||
bazel test --define='gotags=integration' --test_output all //test/integration/... | ||
|
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.
# WARNING: DO NOT SET THE `JANITOR_ENABLED` TO 1 UNLESS YOU WISH TO TEARDOWN RESOURCES IN AWS |
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.
Hi @ashish-amarnath,
Are you suggesting the definition of a target named WARNING
? If so, do you mean the text should be echoed? I am sorry, but I do not understand the proposed change.
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.
Sorry, I missed this comment.
The suggestion was to add a comment to caution users not to change the JANITOR_ENABLED
flag.
This patch deploys a new Boskos janitor as a service in the same cluster running Prow. The new service is named `boskos-janitor-aws`. Related to kubernetes-sigs/cluster-api-provider-aws#272 and kubernetes-sigs/cluster-api-provider-aws#606. /area boskos
This patch deploys a new Boskos janitor as a service in the same cluster running Prow. The new service is named `boskos-janitor-aws`. Related to kubernetes-sigs/cluster-api-provider-aws#272 and kubernetes-sigs/cluster-api-provider-aws#606. /area boskos
This patch deploys a new Boskos janitor as a service in the same cluster running Prow. The new service is named `boskos-janitor-aws`. Related to kubernetes-sigs/cluster-api-provider-aws#272 and kubernetes-sigs/cluster-api-provider-aws#606. /area boskos
This patch deploys a new Boskos janitor as a service in the same cluster running Prow. The new service is named `boskos-janitor-aws`. Related to kubernetes-sigs/cluster-api-provider-aws#272 and kubernetes-sigs/cluster-api-provider-aws#606. /area boskos
Hi @randomvariable, I understand what he means. I just wanted to point out that the PR template pushes people to indicates fixes, even when it's partially applicable. I'll remove it though. |
Enjoying the terminology |
/hold |
hack/e2e-aws-janitor.sh
Outdated
|
||
# Prevent a disallowed AWS key from being used. | ||
if grep -iqF "$(echo "${AWS_ACCESS_KEY_ID-}" | \ | ||
{ md5sum || md5; } | awk '{print $1}')" hack/e2e-aws-disallowed.txt; then |
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.
Fix stderr
031bc0a
to
a2a4459
Compare
This patch updates documentation, the Makefile, and creates some new programs under the `hack` directory in order to make e2e testing as easy as possible, both locally and as a invocation point for Prow jobs.
a2a4459
to
0cc8410
Compare
/milestone v1alpha1 |
closing, since #658 has merged |
This patch deploys a new Boskos janitor as a service in the same cluster running Prow. The new service is named `boskos-janitor-aws`. Related to kubernetes-sigs/cluster-api-provider-aws#272 and kubernetes-sigs/cluster-api-provider-aws#606. /area boskos
This patch deploys a new Boskos janitor as a service in the same cluster running Prow. The new service is named `boskos-janitor-aws`. Related to kubernetes-sigs/cluster-api-provider-aws#272 and kubernetes-sigs/cluster-api-provider-aws#606. /area boskos
What this PR does / why we need it:
This patch updates documentation, the Makefile, and creates some new programs under the
hack
directory in order to make e2e testing as easy as possible, both locally and as a invocation point for Prow jobs.This is a work-in-progress, and the PR is being opened as a point of discussion and to provide an opportunity for the community to give feedback early in the process.
Blocked by:
boskos: AWS janitor region via env var kubernetes/test-infra#11425boskos: AWS janitor not cleaning up all of the resources kubernetes/test-infra#11471AWS janitor clean -all option kubernetes/test-infra#11482aws-janitor: Support for CloudFormation Stacks kubernetes/test-infra#11504/hold
Which issue(s) this PR fixes:
Partially-Sorta-Kinda-Phixes #272 (see Special notes)
Special notes for your reviewer:
This PR alone will not phix #272 as a period Prow job will need to be created. However, the content of this PR will be how Prow initiates the e2e testing.
Release note: