Skip to content
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

DNS record scale test #63820

Merged
merged 1 commit into from
May 31, 2018
Merged

Conversation

chrisohaver
Copy link
Contributor

@chrisohaver chrisohaver commented May 14, 2018

What this PR does / why we need it:

Adds e2e scalability test for querying DNS with a scaled up number of records. Specifically, it creates 30 services per node 10000 services, then queries the cluster DNS and validates the response. This relates to a graduation criteria listed in kubernetes/community#1956.

Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
none

Special notes for your reviewer:

Release note:

NONE

@k8s-ci-robot k8s-ci-robot added release-note-none Denotes a PR that doesn't merit a release note. size/L Denotes a PR that changes 100-499 lines, ignoring generated files. cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. labels May 14, 2018
@k8s-ci-robot k8s-ci-robot requested review from dnardo and shyamjvs May 14, 2018 20:20
@rajansandeep
Copy link
Contributor

/ok-to-test

@k8s-ci-robot k8s-ci-robot removed the needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. label May 14, 2018
@rajansandeep
Copy link
Contributor

/sig network

@k8s-ci-robot k8s-ci-robot added the sig/network Categorizes an issue or PR as relevant to SIG Network. label May 14, 2018
@rajansandeep
Copy link
Contributor

/sig scalability

@k8s-ci-robot k8s-ci-robot added the sig/scalability Categorizes an issue or PR as relevant to SIG Scalability. label May 14, 2018
@@ -0,0 +1,91 @@
/*
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Could you instead place this test under test/e2e/network?

Sig-scalability is a horizontal effort - scale testing for vertical features should ideally belong to the relevant sig (which in this case seems to be sig-networking).

@chrisohaver
Copy link
Contributor Author

@johnbelamaric

@rajansandeep
Copy link
Contributor

/test pull-kubernetes-bazel-test
/test pull-kubernetes-kubemark-e2e-gce

@chrisohaver
Copy link
Contributor Author

@bowei, FYI

@chrisohaver
Copy link
Contributor Author

/test pull-kubernetes-integration

@fturib
Copy link

fturib commented May 21, 2018

/assign @bowei

@chrisohaver
Copy link
Contributor Author

This no longer creates 30 services per node - instead it creates the maximum number of services, regardless of cluster size.

@chrisohaver
Copy link
Contributor Author

flake?
/test pull-kubernetes-e2e-gce

@fturib
Copy link

fturib commented May 25, 2018

@shyamjvs , @dnardo , @bowei : gentle reminder here for review of this e2e test for DNS. Code slush will happen soon. Thanks for your collaboration.

@@ -0,0 +1,84 @@
/*
Copyright 2016 The Kubernetes Authors.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

2018

defer GinkgoRecover()
framework.ExpectNoError(testutils.CreateServiceWithRetries(f.ClientSet, f.Namespace.Name, services[i]))
}
workqueue.Parallelize(16, len(services), createService)
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Could you maybe expose this hard-coded value of 16 as some global constant?


// answers dns for service - creates the maximum number of services, and then check dns record for one
It("answers dns for service", func() {
services := generateDnsServicesInNamespace(f.Namespace.Name, 10000)
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Same as other comment. Expose this value as global constant.

@@ -169,6 +180,10 @@ func (t *dnsTestCommon) deleteConfigMap() {
}

func (t *dnsTestCommon) createUtilPod() {
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can't you just get rid of this function or replace it's uses with createUtilPodLabel?

@chrisohaver
Copy link
Contributor Author

/retest

Copy link
Member

@MrHohn MrHohn left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks! This looks good overall.
/approve

@k8s-ci-robot k8s-ci-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label May 30, 2018
@chrisohaver
Copy link
Contributor Author

Thanks @MrHohn! Can you tag for the current release milestone?

@MrHohn
Copy link
Member

MrHohn commented May 30, 2018

Can you tag for the current release milestone?

Sorry I don't have that privilege. But no worries I will grab someone for help.

@MrHohn
Copy link
Member

MrHohn commented May 30, 2018

/lgtm

@k8s-ci-robot k8s-ci-robot added the lgtm "Looks good to me", indicates that a PR is ready to be merged. label May 30, 2018
@k8s-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: chrisohaver, MrHohn

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 /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@MrHohn
Copy link
Member

MrHohn commented May 30, 2018

/kind feature
/priority important-soon

@k8s-ci-robot k8s-ci-robot added kind/feature Categorizes issue or PR as related to a new feature. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. labels May 30, 2018
@fejta-bot
Copy link

/retest
This bot automatically retries jobs that failed/flaked on approved PRs (send feedback to fejta).

Review the full test history for this PR.

Silence the bot with an /lgtm cancel comment for consistent failures.

3 similar comments
@fejta-bot
Copy link

/retest
This bot automatically retries jobs that failed/flaked on approved PRs (send feedback to fejta).

Review the full test history for this PR.

Silence the bot with an /lgtm cancel comment for consistent failures.

@fejta-bot
Copy link

/retest
This bot automatically retries jobs that failed/flaked on approved PRs (send feedback to fejta).

Review the full test history for this PR.

Silence the bot with an /lgtm cancel comment for consistent failures.

@fejta-bot
Copy link

/retest
This bot automatically retries jobs that failed/flaked on approved PRs (send feedback to fejta).

Review the full test history for this PR.

Silence the bot with an /lgtm cancel comment for consistent failures.

@chrisohaver
Copy link
Contributor Author

FYI, pull-kubernetes-kubemark-e2e-gce-big failure is not related to this change. It is currently failing consistently/universally since 2018-05-30 13:30 EDT.

@fturib
Copy link

fturib commented May 31, 2018

@caseydavenport, @dcbw : Can you add the needed label "status/approved-for-milestone" for this e2e test for DNS scale - it is located in sig-network area on advise of sig-scalability guys.
Thanks!

@fejta-bot
Copy link

/retest
This bot automatically retries jobs that failed/flaked on approved PRs (send feedback to fejta).

Review the full test history for this PR.

Silence the bot with an /lgtm cancel comment for consistent failures.

1 similar comment
@fejta-bot
Copy link

/retest
This bot automatically retries jobs that failed/flaked on approved PRs (send feedback to fejta).

Review the full test history for this PR.

Silence the bot with an /lgtm cancel comment for consistent failures.

@k8s-github-robot
Copy link

[MILESTONENOTIFIER] Milestone Pull Request: Up-to-date for process

@MrHohn @bowei @chrisohaver

Pull Request Labels
  • sig/network sig/scalability: Pull Request will be escalated to these SIGs if needed.
  • priority/important-soon: Escalate to the pull request owners and SIG owner; move out of milestone after several unsuccessful escalation attempts.
  • kind/feature: New functionality.
Help

@k8s-ci-robot
Copy link
Contributor

@chrisohaver: The following test failed, say /retest to rerun them all:

Test name Commit Details Rerun command
pull-kubernetes-kubemark-e2e-gce-big c66f932 link /test pull-kubernetes-kubemark-e2e-gce-big

Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR.

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. I understand the commands that are listed here.

@k8s-github-robot
Copy link

Automatic merge from submit-queue (batch tested with PRs 63445, 63820). If you want to cherry-pick this change to another branch, please follow the instructions here.

@k8s-github-robot k8s-github-robot merged commit 471b573 into kubernetes:master May 31, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. kind/feature Categorizes issue or PR as related to a new feature. lgtm "Looks good to me", indicates that a PR is ready to be merged. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. release-note-none Denotes a PR that doesn't merit a release note. sig/network Categorizes an issue or PR as relevant to SIG Network. sig/scalability Categorizes an issue or PR as relevant to SIG Scalability. size/L Denotes a PR that changes 100-499 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.