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

Install latest release of net-istio whenever we install latest release of serving. #8158

Merged
merged 4 commits into from
Jun 2, 2020

Conversation

tcnghia
Copy link
Contributor

@tcnghia tcnghia commented Jun 2, 2020

Fixes #8153

Proposed Changes

  • Install latest release version of knative/net-istio, if that is where knative/serving is from.

Release Note

NONE

/assign @chizhg

@googlebot googlebot added the cla: yes Indicates the PR's author has signed the CLA. label Jun 2, 2020
@knative-prow-robot knative-prow-robot added the size/M Denotes a PR that changes 30-99 lines, ignoring generated files. label Jun 2, 2020
@knative-prow-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: tcnghia

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

@knative-prow-robot knative-prow-robot added area/test-and-release It flags unit/e2e/conformance/perf test issues for product features approved Indicates a PR has been approved by an approver from all required OWNERS files. labels Jun 2, 2020
@tcnghia tcnghia changed the title Install latest release version of knative/net-istio, if that is where knative/serving is from. Install latest release of net-istio whenever we install latest release of serving. Jun 2, 2020
@markusthoemmes
Copy link
Contributor

Cross posting from the issue:

@tcnghia tbh I'd rather go with the checked in third_party version to have control over what gets tested when. If not, we should ditch the third_party file entirely and always rely on the latest release from net-istio.

@tcnghia
Copy link
Contributor Author

tcnghia commented Jun 2, 2020

@markusthoemmes that was my first thought, but I changed my mind because our users, if following the doc pages today, would start with both release versions of serving and net-istio. So here we try best to simulate their experience. If there is an issue upgrading from that setup, we need to know.

In the other case, using the net-istio nightly from the third_party directory is similar to "building net-istio at HEAD", which is also consistent with "building Serving at HEAD".

test/e2e-upgrade-tests.sh Outdated Show resolved Hide resolved
test/e2e-upgrade-tests.sh Outdated Show resolved Hide resolved
@@ -319,7 +328,18 @@ function install_knative_serving_standard() {
elif [[ -n "${CONTOUR_VERSION}" ]]; then
install_contour || return 1
else
install_istio "./third_party/net-istio.yaml" || return 1
if [[ "$1" == "HEAD" ]]; then
install_istio "./third_party/net-istio.yaml" || return 1
Copy link
Member

Choose a reason for hiding this comment

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

As we discussed yesterday, shall we install the latest nightly release here?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I think this is from the latest nightly release?

Otherwise, what is the URL to get the latest nightly release? thanks

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Since there is already a lot of bash in this PR, I'd do that in a follow up.

test/e2e-common.sh Outdated Show resolved Hide resolved
test/e2e-common.sh Outdated Show resolved Hide resolved
tcnghia and others added 3 commits June 2, 2020 10:30
Co-authored-by: Chi Zhang <chizhg@google.com>
Co-authored-by: Chi Zhang <chizhg@google.com>
@tcnghia
Copy link
Contributor Author

tcnghia commented Jun 2, 2020

So @chizhg and @markusthoemmes: I think we can try to get rid of the third_party file, but my guess is that it may increase problems in our presubmit. I am open to trying it out (in a nother PR) to see if my guess is true though. Worst case we can go back to where we are.

@chizhg
Copy link
Member

chizhg commented Jun 2, 2020

/lgtm

@knative-prow-robot knative-prow-robot added the lgtm Indicates that a PR is ready to be merged. label Jun 2, 2020
@knative-prow-robot knative-prow-robot merged commit 96b5f3e into knative:master Jun 2, 2020
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. area/test-and-release It flags unit/e2e/conformance/perf test issues for product features cla: yes Indicates the PR's author has signed the CLA. lgtm Indicates that a PR is ready to be merged. size/M Denotes a PR that changes 30-99 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Upgrade tests are always using the nightly release of net-istio
5 participants