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

e2e: Use Helm chart from the commit #2435

Merged
merged 2 commits into from
Jan 5, 2022

Conversation

johngmyers
Copy link
Contributor

Issue

Description

Change the e2e tests to use the Helm chart from the commit, not from the main branch. The Helm chart from the commit should be what is under the test.

Checklist

  • Added tests that cover your change (if possible) (the change is the test)
  • Added/modified documentation as required (such as the README.md, or the docs directory) (N/A)
  • Manually tested (N/A)
  • Made sure the title of the PR is a good description that can go into the release notes

BONUS POINTS checklist: complete for good vibes and maybe prizes?! 🤯

  • Backfilled missing tests for code in same general area 🎉
  • Refactored something and made the world a better place 🌟

@k8s-ci-robot k8s-ci-robot added cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. size/M Denotes a PR that changes 30-99 lines, ignoring generated files. labels Dec 27, 2021
@codecov-commenter
Copy link

codecov-commenter commented Dec 27, 2021

Codecov Report

Merging #2435 (78f0ffd) into main (2e181b2) will not change coverage.
The diff coverage is n/a.

Impacted file tree graph

@@           Coverage Diff           @@
##             main    #2435   +/-   ##
=======================================
  Coverage   53.35%   53.35%           
=======================================
  Files         140      140           
  Lines        7962     7962           
=======================================
  Hits         4248     4248           
  Misses       3397     3397           
  Partials      317      317           

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 2e181b2...78f0ffd. Read the comment docs.

@johngmyers johngmyers force-pushed the e2e-chart branch 2 times, most recently from 47a9ad6 to b6a1098 Compare December 27, 2021 20:58
test/e2e/run-canary-test.sh Outdated Show resolved Hide resolved
test/framework/options.go Outdated Show resolved Hide resolved
@@ -51,6 +53,9 @@ func (options *Options) Validate() error {
if len(options.AWSVPCID) == 0 {
return errors.Errorf("%s must be set!", "aws-vpc-id")
}
if len(options.HelmDir) == 0 {
Copy link
Collaborator

Choose a reason for hiding this comment

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

Comment from PR 2433,

@kishorj 2 hours ago

why not make it optional? If set, test uses the specified directory, otherwise default to the aws eks-charts repo.

@johngmyers 1 hour ago

Making it optional adds complexity for no obvious reason and admits the possibility of missing an incompatibility between the repo's chart and the repo's image.

Could you give more information on the use case for this? Why would one not want to put the repo's Helm chart under test?

@kishorj now

One example is the canary script which we run against the release version. In this case we want the last published image and the chart, not the recent one from the repo.

Copy link
Contributor Author

@johngmyers johngmyers Jan 5, 2022

Choose a reason for hiding this comment

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

One possibility would be to download the published chart in the script, outside of ginkgo. But it might work to rely on the script's current helm repo add and pass the name of the chart.

@johngmyers
Copy link
Contributor Author

I can squash if requested.

@kishorj kishorj added the tide/merge-method-squash Denotes a PR that should be squashed by tide when it merges. label Jan 5, 2022
@kishorj
Copy link
Collaborator

kishorj commented Jan 5, 2022

I can squash if requested.

not necessary, I set to squash on merge :)

@k8s-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: johngmyers, kishorj

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

@k8s-ci-robot k8s-ci-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Jan 5, 2022
@kishorj
Copy link
Collaborator

kishorj commented Jan 5, 2022

/lgtm

@k8s-ci-robot k8s-ci-robot added the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Jan 5, 2022
@k8s-ci-robot k8s-ci-robot merged commit 316f6c0 into kubernetes-sigs:main Jan 5, 2022
@johngmyers johngmyers deleted the e2e-chart branch January 5, 2022 20:40
@johngmyers johngmyers mentioned this pull request Aug 23, 2023
12 tasks
Timothy-Dougherty pushed a commit to adammw/aws-load-balancer-controller that referenced this pull request Nov 9, 2023
* e2e: Use Helm chart from the commit

* Address review comments
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. lgtm "Looks good to me", indicates that a PR is ready to be merged. size/M Denotes a PR that changes 30-99 lines, ignoring generated files. tide/merge-method-squash Denotes a PR that should be squashed by tide when it merges.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants