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.

Sign up for GitHub

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

Jump to bottom

Test minimal Envoy functionality before release #2223

Closed
youngnick opened this issue Feb 12, 2020 · 9 comments
Closed

Test minimal Envoy functionality before release #2223

youngnick opened this issue Feb 12, 2020 · 9 comments
Labels
area/testing Issues or PRs related to tests or testing tools.

Comments

@youngnick
Copy link
Member

This issue covers work to test the minimum Envoy functionality in #2048 with a release candidate before the final release is cut.

This step should be performed between creating the release branch and cutting the final release in the release runbook https://projectcontour.io/resources/release-process/.
@youngnick youngnick added this to the 1.2.0 milestone Feb 12, 2020
@jpeach
Copy link
Contributor

jpeach commented Feb 12, 2020

xref #2048

@jpeach
Copy link
Contributor

jpeach commented Feb 12, 2020

Probably need to spin off a separate issue for generating the deployment YAML to run envoy with extensions disabled. That might depend on doing something with kustomize, since we want to be able to deploy Contour in a standard way but just slam in some new flags to the envoy container.

xref #2088

@jpeach jpeach added the area/testing Issues or PRs related to tests or testing tools. label Feb 19, 2020
jpeach added a commit to jpeach/contour that referenced this issue Feb 19, 2020
@jpeach
ci: verify that Contour installs
59073ef 
Add the bare minimum CI machinery to fetch a Kubernetes toolchain
and verify that Contour can be installed in the example deployment
configuration.

This updates projectcontour#2223.

Signed-off-by: James Peach <jpeach@vmware.com>
@jpeach jpeach mentioned this issue Feb 19, 2020
Merged
jpeach added a commit to jpeach/contour that referenced this issue Feb 19, 2020
@jpeach
ci: verify that Contour installs
30614dc 
Add the bare minimum CI machinery to fetch a Kubernetes toolchain
and verify that Contour can be installed in the example deployment
configuration.

This updates projectcontour#2223.

Signed-off-by: James Peach <jpeach@vmware.com>
jpeach added a commit to jpeach/contour that referenced this issue Feb 20, 2020
@jpeach
ci: verify that Contour installs
4b6594d 
Add the bare minimum CI machinery to fetch a Kubernetes toolchain
and verify that Contour can be installed in the example deployment
configuration.

This updates projectcontour#2223.

Signed-off-by: James Peach <jpeach@vmware.com>
@stevesloka
Copy link
Member

Completed manual testing for Contour release v1.2.0

@stevesloka stevesloka reopened this Feb 20, 2020
@stevesloka stevesloka modified the milestones: 1.2.0, 1.3.0 Feb 20, 2020
jpeach added a commit that referenced this issue Feb 21, 2020
@jpeach
ci: verify that Contour installs
abf82cb 
Add the bare minimum CI machinery to fetch a Kubernetes toolchain
and verify that Contour can be installed in the example deployment
configuration.

This updates #2223.

Signed-off-by: James Peach <jpeach@vmware.com>
@stevesloka stevesloka removed their assignment Feb 24, 2020
@jpeach
Copy link
Contributor

jpeach commented Mar 12, 2020

Test scenarios from @stevesloka

https://docs.google.com/spreadsheets/d/1Y22qy_9Q6UO1rcM24NrFq8x6sHoEpWTuNEVQq7hb42Y

@jpeach jpeach removed this from the 1.3.0 milestone Mar 20, 2020
@stevesloka
Copy link
Member

@jpeach what's the status on the test infra? Can we merge that and start incorporating even if it's not 100% complete.

We also need to find a way to track changes as new features are added. For example, the ingress class work that was just added should be tracked somewhere to be added to the functional tests.

@jpeach
Copy link
Contributor

jpeach commented Apr 1, 2020

@jpeach what's the status on the test infra?

The test driver works and can run declarative tests. I've got a handful of tests written for Contour.

Can we merge that and start incorporating even if it's not 100% complete.

Yes, we should start that. I need to publish the repo and add goreleaser so that there is an artifact that we can run. I have a separate repo with the test cases, which I think would end up being merged into Contour repository.

We also need to find a way to track changes as new features are added. For example, the ingress class work that was just added should be tracked somewhere to be added to the functional tests.

We could add a label, or file an issue for each test as we think of it?

@youngnick
Copy link
Member Author

I think that creating issues with a label is the way to go

jpeach added a commit to jpeach/contour that referenced this issue Apr 9, 2020
@jpeach
test: add initial integration test scripts
e20f947 
Add an initial set of inte3gration test documents, along with
helper scripts to install a kind cluster and to run the tests.

This updates projectcontour#2223.

Signed-off-by: James Peach <jpeach@vmware.com>
jpeach added a commit to jpeach/contour that referenced this issue Apr 9, 2020
@jpeach
test: add initial integration test scripts
80c8630 
Add an initial set of integration test documents, along with
helper scripts to install a kind cluster and to run the tests.

This updates projectcontour#2223.

Signed-off-by: James Peach <jpeach@vmware.com>
@jpeach jpeach mentioned this issue Apr 9, 2020
Merged
jpeach added a commit to jpeach/contour that referenced this issue May 5, 2020
@jpeach
test: add initial integration test scripts
448f50a 
Add an initial set of integration test documents, along with
helper scripts to install a kind cluster and to run the tests.

This updates projectcontour#2223.

Signed-off-by: James Peach <jpeach@vmware.com>
jpeach added a commit to jpeach/contour that referenced this issue May 6, 2020
@jpeach
test: add initial integration test scripts
1db6129 
Add an initial set of integration test documents, along with
helper scripts to install a kind cluster and to run the tests.

This updates projectcontour#2223.

Signed-off-by: James Peach <jpeach@vmware.com>
jpeach added a commit that referenced this issue May 6, 2020
@jpeach
test: add initial integration test scripts (#2426)
f8a63ac 
Add an initial set of integration test documents, along with
helper scripts to install a kind cluster and to run the tests.

This updates #2223.

Signed-off-by: James Peach <jpeach@vmware.com>
@skriss
Copy link
Member

skriss commented Jan 15, 2021

What's the action item on this issue? Should we consider this closed now that we have some integration tests in place?

@youngnick
Copy link
Member Author

Yes, I think that we should close this out now that we have integration tests in place. More specific items should generate new issues.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
area/testing Issues or PRs related to tests or testing tools.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@jpeach @stevesloka @skriss @youngnick