-
Notifications
You must be signed in to change notification settings - Fork 41
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
Added prow job for KinD based druid e2e #553
Conversation
Prow is not enabled for |
I will address your suggestion in this PR. We are currently trying with something that enables us to use local storage instead of remote storage. In that case, we may not need to create secrets for AWS credentials in prow cluster at all. If our effort is successful, I will update this PR with correct configs. Please, wait till then. Thanks |
The Gardener project currently lacks enough active contributors to adequately respond to all PRs.
You can:
/lifecycle stale |
The Gardener project currently lacks enough active contributors to adequately respond to all PRs.
You can:
/lifecycle rotten |
/remove-lifecycle rotten |
/remove-lifecycle stale |
@oliver-goetz Would you pls hv a look on the PR. I updated |
The Gardener project currently lacks enough active contributors to adequately respond to all PRs.
You can:
/lifecycle stale |
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.
Other than few formatting.
/lgtm
/hold |
Nothing to add to @acumino comments 👍 /remove-lifecycle stale |
/ping @abdasgupta |
cpu: 12 | ||
memory: 18Gi |
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.
One question, other than that lgtm.
Have you tested the resource consumption for this test?
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 haven't tested specifically. But that amount of resource is enough for the e2e tests. Basically, we run the tests inside a KIND cluster running inside a container.
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.
My only concern is not to allocate unnecessarily a lot of resources to prevent resource wastage.
/cc @oliver-goetz
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 to @acumino. We have nodes with 16 CPUs, so the etcd-druid test would consume an entire node.
Usually, we require 12 CPUs for our big e2e tests in gardener/gardener
where 15 shoots are created in parallel. The smaller tests require 6 CPUs.
Your description sound like the etcd-druid test rather fits into the small test category, so let's start with 6 CPUs.
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.
Okay. Let me come back to this after I check with the resources..
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.
@seshachalam-yv helped me to verify that the druid e2e tests run even with 6cpu and 8Gi mem. So I changed the PR to use that much resources only.
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.
/unhold
/approve
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: acumino 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 |
/cc @oliver-goetz for lgtm |
@acumino: GitHub didn't allow me to request PR reviews from the following users: for, lgtm. Note that only gardener members and repo collaborators can review this PR, and authors cannot review their own PRs. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
thanks, let's see how it works 😄 |
LGTM label has been added. Git tree hash: d792e44a66a2ffbed2791b297184cd13eb93ee3e
|
@abdasgupta: Updated the following 2 configmaps:
In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
/kind enhancement
What this PR does / why we need it:
This PR enables to run KinD based Druid e2e tests through prow jobs
Which issue(s) this PR fixes:
Fixes #
gardener/etcd-druid#465
Special notes for your reviewer: