Skip to content

Tags: yangzhenkun/istio

Tags

0.3.0

Toggle 0.3.0's commit message
istio Release 0.3.0

0.2.12

Toggle 0.2.12's commit message
Istio_Release_0.2.12

0.2.11

Toggle 0.2.11's commit message
Istio_Release_0.2.11 (istio#1550)

0.2.10

Toggle 0.2.10's commit message
Istio_Release_0.2.10 (istio#1225)

Former-commit-id: 651f112

0.2.9

Toggle 0.2.9's commit message
Merge branch 'release-0.2' into Istio_Release_0.2.9

Former-commit-id: 00fa37a

0.2.7

Toggle 0.2.7's commit message
simpler, additional e2e functional test + auth test (istio#833)

Automatic merge from submit-queue

simpler, additional e2e functional test + auth test

This is for a couple things:

a) an e2e test (using the e2e framework) that has minimum  dependencies and fast start which can be use as a starting point for new tests that do not rely on bookinfo
b) exercise fortio images, ingress rule svc2sc
c) detect whether auth is working or not
d) bug fix in fortio when server errors out
e) faster test start and end (and updated README with the faster instructions)

_background/justification_
We all spent a lot of time debugging complex end2end test over the last few weeks,
Also people have been complaining that writing new tests is hard (which is partially true as I learned through writing one), and we also don't have test verifying auth is really on

This PR makes progress toward solving all 3 problems, introducing a simpler (than mixer/bookinfo) test. 

A simpler test lets us quickly smoke test basic features.

This is additional to tests that exists in pilot (as this is about end2end with all the actual components in place, same code as we release)

e2e is not exclusively "website tasks testing" and should have as many sane tests as we can have

A separate effort - though this simpler test does help already - is to optimize the runtime and probably split test into "every PR" tests and "nightly"... etc... 

```release-note
New simpler e2e functional tests, including an auth test.
```

Former-commit-id: fad04b1

0.2.6

Toggle 0.2.6's commit message
Use default GKE cluster version (istio#975)

Automatic merge from submit-queue

Use default GKE cluster version

**What this PR does / why we need it**:

**Which issue this PR fixes** *(optional, in `fixes #<issue number>(, fixes #<issue_number>, ...)` format, will close that issue when PR gets merged)*: fixes #

**Special notes for your reviewer**:

**Release note**:

```release-note
none
```

Dynamically update cluster version we use by using GKE default value.

Former-commit-id: f6b0deb

0.2.4

Toggle 0.2.4's commit message
finalizeRelease-0.2.4 (istio#910)

Former-commit-id: e820d83

0.2.2

Toggle 0.2.2's commit message
Istio_Release_0.2.2 (istio#794)

Former-commit-id: 9ac006e

0.2.1

Toggle 0.2.1's commit message
Istio_Release_0.2.1 (istio#624)

Former-commit-id: 6077ca3