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

Add e2e tests for Metrics Server and Master Metrics API #52811

Closed
nikhiljindal opened this issue Sep 20, 2017 · 14 comments
Closed

Add e2e tests for Metrics Server and Master Metrics API #52811

nikhiljindal opened this issue Sep 20, 2017 · 14 comments
Assignees
Labels
kind/cleanup Categorizes issue or PR as related to cleaning up code, process, or technical debt. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. sig/instrumentation Categorizes an issue or PR as relevant to SIG Instrumentation.

Comments

@nikhiljindal
Copy link
Contributor

Need e2e tests for kubernetes/enhancements#271 which is being released as part of release 1.8.

cc @piosz who is working on the tests.

@grodrigues3
Copy link
Contributor

/cc @DirectXMan12

@nikhiljindal nikhiljindal added the kind/failing-test Categorizes issue or PR as related to a consistently or frequently failing test. label Sep 20, 2017
@luxas
Copy link
Member

luxas commented Sep 21, 2017

@nikhiljindal Is this blocking the v1.8 release?

@nikhiljindal
Copy link
Contributor Author

Yes. I am hoping that we wont ship 1.8 without any e2e tests for this feature?

I will let @piosz and the release team take a call, if it comes to that. Hopefully we will have e2e tests soon without causing delays to the release.

@ericchiang
Copy link
Contributor

This is extremely late to be adding an e2e tests considering we just spent the last three weeks stabilizing the existing tests :(

If e2e tests are absolutely required lets get them in ASAP.

Removing the failing tests labels because this isn't a failing test.

cc @kubernetes/kubernetes-release-managers

@ericchiang ericchiang added kind/cleanup Categorizes issue or PR as related to cleaning up code, process, or technical debt. priority/critical-urgent Highest priority. Must be actively worked on as someone's top priority right now. and removed kind/e2e-test-failure kind/failing-test Categorizes issue or PR as related to a consistently or frequently failing test. labels Sep 21, 2017
@k8s-github-robot
Copy link

[MILESTONENOTIFIER] Milestone Labels Complete

@nikhiljindal @piosz

Issue label settings:

  • sig/instrumentation: Issue will be escalated to these SIGs if needed.
  • priority/critical-urgent: Never automatically move out of a release milestone; continually escalate to contributor and SIG through all available channels.
  • kind/cleanup: Adding tests, refactoring, fixing old bugs.
Additional instructions available here The commands available for adding these labels are documented here

@jdumars
Copy link
Member

jdumars commented Sep 22, 2017

@nikhiljindal @piosz this is a serious impact on the 1.8 release. We need to understand exactly what the risk is of shipping without this test in place, as well as some evidence that the test is stable.

@nikhiljindal
Copy link
Contributor Author

Sorry am not as familiar with this feature. I will let @piosz comment on that.

@piosz
Copy link
Member

piosz commented Sep 22, 2017

@jdumars apologies for the delay but I'm fighting with a cold. I'm working on them, hopefully will finish it today. The original plan was to test it through HPA e2e tests, but we decided to not use metrics-server by default in HPA (see #52553).

@liggitt
Copy link
Member

liggitt commented Sep 22, 2017

if it is not enabled by default for HPA in 1.8, then I don't think the e2e tests are release-blocking

@ericchiang
Copy link
Contributor

Commented on the feature repo but the release team has concerns about adding e2e tests this close to the release kubernetes/enhancements#271 (comment)

I agree with @liggitt. If this isn't on by default we should remove this from the milestone.

@piosz
Copy link
Member

piosz commented Sep 22, 2017

The feature is enabled by default but no other component uses it. The rollout plan is as follow:

  • in 1.8 metrics-server was introduced
  • in 1.9 we switch HPA to use it by default

I agree that having e2e tests is not a release blocker as HPA doesn't use it.

@luxas
Copy link
Member

luxas commented Sep 22, 2017

The feature is enabled by default

To clarify, in GKE only AFAIK, right?

@piosz
Copy link
Member

piosz commented Sep 22, 2017

GCE/GKE

@piosz piosz removed this from the v1.8 milestone Sep 22, 2017
@piosz piosz added priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. and removed priority/critical-urgent Highest priority. Must be actively worked on as someone's top priority right now. labels Sep 22, 2017
@piosz
Copy link
Member

piosz commented Oct 12, 2017

fixed in #53205
(we test metrics-server in HPA e2e tests which uses metrics from metrics-server)

@piosz piosz closed this as completed Oct 12, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/cleanup Categorizes issue or PR as related to cleaning up code, process, or technical debt. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. sig/instrumentation Categorizes an issue or PR as relevant to SIG Instrumentation.
Projects
None yet
Development

No branches or pull requests

9 participants