Skip to content

Adding min istio version for new features to avoid running on older revisions #40892

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

Merged
merged 1 commit into from
Sep 12, 2022

Conversation

hemendrateli
Copy link
Contributor

Please provide a description of this PR:

We are adding min istio version for tests related to below PRs as this functionalities were not there in previous revisions :-
a. gRPC fault
injection(#39295)
b. Ignore port number in domain
matching(#40475)
c. Tunneling outbound traffic :- new tunnel field got
introduced(#37968)
d. Fix consistent hash based on source IP for TCP
proxy(#38438)
e. Traffic policy load balancer API
changes(#39742)

To help us figure out who should review this PR, please put an X in all the areas that this PR affects.

  • Ambient
  • Configuration Infrastructure
  • Docs
  • Installation
  • Networking
  • Performance and Scalability
  • Policies and Telemetry
  • Security
  • [X ] Test and Release
  • User Experience
  • Developer Infrastructure

Please check any characteristics that apply to this pull request.

  • [X ] Does not have any user-facing changes. This may include CLI changes, API changes, behavior changes, performance improvements, etc.

…evisions

We are adding min istio version for tests related to below PRs as this functionalities were not there in previous revisions :-
	a. gRPC fault
           injection(istio#39295)
	b. Ignore port number in domain
           matching(istio#40475)
	c. Tunneling outbound traffic :- new tunnel field got
           introduced(istio#37968)
	d. Fix consistent hash based on source IP for TCP
           proxy(istio#38438)
	e. Traffic policy load balancer API
           changes(istio#39742)
@hemendrateli hemendrateli requested review from a team as code owners September 9, 2022 06:54
@google-cla
Copy link

google-cla bot commented Sep 9, 2022

Thanks for your pull request! It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

View this failed invocation of the CLA check for more information.

For the most up to date status, view the checks section at the bottom of the pull request.

@istio-testing istio-testing added size/M Denotes a PR that changes 30-99 lines, ignoring generated files. needs-ok-to-test labels Sep 9, 2022
@istio-testing
Copy link
Collaborator

Hi @hemendrateli. Thanks for your PR.

I'm waiting for a istio member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

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.

@hzxuzhonghu
Copy link
Member

Not sure i understand why you are testing older istio version with test cases in master

@hemendrateli
Copy link
Contributor Author

/cc @stewartbutler

@hemendrateli
Copy link
Contributor Author

@hzxuzhonghu This is to test migration use case where multiple versions are installed and workloads communicate across revisions.

@howardjohn
Copy link
Member

/ok-to-test

@istio-testing istio-testing added ok-to-test Set this label allow normal testing to take place for a PR not submitted by an Istio org member. and removed needs-ok-to-test labels Sep 9, 2022
@@ -147,6 +151,7 @@ func TestReachability(t *testing.T) {
expectCrossCluster: notFromNaked,
expectCrossNetwork: notNaked,
expectSuccess: notToNaked,
minIstioVersion: "1.15.0",
Copy link
Contributor

Choose a reason for hiding this comment

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

does that mean it won't work for versions lesser than 1.15 ?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

  1. If we try to test this master branch reachability tests against versions lesser than 1.15 then it won't work (so we are trying to skip) because of new API changes done(PR#39742) which are not there in version 1.13.
  2. 1.13 branch already has its reachability tests which will work on 1.13 version.

@howardjohn howardjohn added the release-notes-none Indicates a PR that does not require release notes. label Sep 12, 2022
@howardjohn
Copy link
Member

/retest

@istio-testing istio-testing merged commit 7acaed8 into istio:master Sep 12, 2022
@stewartbutler
Copy link
Contributor

/cherrypick release-1.15

@istio-testing
Copy link
Collaborator

@stewartbutler: new pull request created: #40957

In response to this:

/cherrypick release-1.15

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
ok-to-test Set this label allow normal testing to take place for a PR not submitted by an Istio org member. release-notes-none Indicates a PR that does not require release notes. 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.

6 participants