-
Notifications
You must be signed in to change notification settings - Fork 542
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
Use deployment instead of raw pod for storage perf tests #687
Use deployment instead of raw pod for storage perf tests #687
Conversation
Hi @mucahitkurt. Thanks for your PR. I'm waiting for a kubernetes member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. 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. |
/ok-to-test |
@wojtek-t are scale tests run on regional clusters? I'm thinking of when we want to reuse these for PVC tests too and each PVC is restricted to a single zone. To support multiple PVCs in a Pod case, we would need to either:
|
How does this work for config and secret where the name of the config/secret is different for every pod? |
@hantaowang I use N deployments for N pods, so the relation is 1-1, and volume matching shouldn't be different for the raw pod case, I create N volumes and match these volumes to the N pods inside the N deployments. |
@@ -3,7 +3,7 @@ | |||
|
|||
#Constants | |||
{{$TOTAL_PODS := DefaultParam .TOTAL_PODS 1}} | |||
{{$POD_TEMPLATE_PATH := DefaultParam .POD_TEMPLATE_PATH "../volume-types/emptydir/pod_with_emptydir.yaml"}} | |||
{{$DEPLOYMENT_TEMPLATE_PATH := DefaultParam .DEPLOYMENT_TEMPLATE_PATH "../volume-types/emptydir/deployment_with_emptydir.yaml"}} |
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'm sorry - I was blocking @hantaowang PRs for quite some time and your stuff, so this time I will do it the other way (unfortunately you're both touching the same stuff).
#688 is super useful, so I would like that one to merge first and then I will ask you to rebase this one on top.
Doesn't this then also stress the deployment controller? We may inadvertently become bottle necked by the deployment and replicaset controller despite the fact that so many deployments are rare. Deployments are definitely a dimension to stress on, but imo for storage that should be eliminated as a variable. |
Disagree - this number of deployments actually isn't very high (we're testing higher numbers). And we should be using what users are using not something artificial. |
Is it that realistic to use 1 deployment per pod? I'm thinking more for when the tests become larger scale (say 5000 nodes at 10 pods per node). I don't see anyone using 50000 deployments to manage this as that would definitely overload the controllers. |
I've seen a bunch of large user clusters with a huge number of those - yes it is realistic.
I wouldn't be that convinced that this will for sure overload controllers. |
waiting for the PVC tests PR's merge to continue |
That PR has just merged - can you please rebase? |
dc55398
to
3271c43
Compare
@wojtek-t, @hantaowang pod usages are converted to deployment usage |
metadata: | ||
name: {{.Name}} | ||
labels: | ||
app: {{.Name}} |
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.
What do we need "app" label for?
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 think we don't need it
configMap: | ||
name: vol-{{AddInt $volumeIndex (MultiplyInt $index $volumesPerPod)}} | ||
{{ end }} | ||
dnsPolicy: Default |
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.
We don't need to set it - it will be defaulted anyway.
name: vol-{{AddInt $volumeIndex (MultiplyInt $index $volumesPerPod)}} | ||
{{ end }} | ||
dnsPolicy: Default | ||
terminationGracePeriodSeconds: 1 |
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.
Please remove - I don't think we need it for anything.
- key: "node.kubernetes.io/unreachable" | ||
operator: "Exists" | ||
effect: "NoExecute" | ||
tolerationSeconds: 900 |
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.
All the comments in this file apply to all other files too.
Signed-off-by: Mucahit Kurt <[email protected]>
3271c43
to
f9843f0
Compare
/lgtm thanks! |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: mucahitkurt, wojtek-t 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 |
Fix #666
Raw pod object templates are changed with deployment templates and the same pods definitions are used inside deployments. Deployment-Pod relation is 1-1.
Also test config files are changed according to these new deployment templates.
/sig storage
/assign @wojtek-t
cc @msau42