mirror of https://github.com/istio/istio.io.git
add cleanup instructions and other minor task improvements (#217)
This commit is contained in:
parent
ce63a064e7
commit
54bfeea2a9
|
@ -239,9 +239,12 @@ This application is polyglot, i.e., the microservices are written in different l
|
|||
Now that you have the BookInfo sample up and running, you can use Istio to control traffic routing,
|
||||
inject faults, rate limit services, etc..
|
||||
|
||||
* To get started, check out the [request routing task]({{home}}/docs/tasks/request-routing.html)
|
||||
To get started, check out the [request routing task]({{home}}/docs/tasks/request-routing.html)
|
||||
|
||||
* When you're finished experimenting with the BookInfo sample, you can uninstall it as follows:
|
||||
|
||||
## Cleanup
|
||||
|
||||
When you're finished experimenting with the BookInfo sample, you can uninstall it as follows:
|
||||
|
||||
1. Delete the routing rules and terminate the application pods
|
||||
|
||||
|
|
|
@ -22,10 +22,14 @@ service or, alternatively, to simply enable direct calls to an external service.
|
|||
* Setup Istio by following the instructions in the
|
||||
[Installation guide](./installing-istio.html).
|
||||
|
||||
* Start a service pod that you can use as a test source for external calls.
|
||||
Any pod that you can `exec` and `curl` from will do, for example,
|
||||
the [sleep sample](https://github.com/istio/istio/tree/master/samples/apps/sleep)
|
||||
is a good choice.
|
||||
* Start the [sleep](https://github.com/istio/istio/tree/master/samples/apps/sleep) sample
|
||||
which will be used as a test source for external calls.
|
||||
|
||||
```bash
|
||||
kubectl apply -f <(istioctl kube-inject -f samples/apps/sleep/sleep.yaml)
|
||||
```
|
||||
|
||||
Note that any pod that you can `exec` and `curl` from would do.
|
||||
|
||||
## Using the Istio Egress service
|
||||
|
||||
|
@ -167,6 +171,22 @@ The second approach bypasses the Istio sidecar proxy, giving your services direc
|
|||
external URL. However, configuring the proxy this way does require
|
||||
cloud provider specific knowledge and configuration.
|
||||
|
||||
|
||||
## Cleanup
|
||||
|
||||
1. Remove the external services.
|
||||
|
||||
```bash
|
||||
kubectl delete service externalbin securegoogle
|
||||
```
|
||||
|
||||
1. Shutdown the [sleep](https://github.com/istio/istio/tree/master/samples/apps/sleep) service.
|
||||
|
||||
```
|
||||
kubectl delete -f samples/apps/sleep/sleep.yaml
|
||||
```
|
||||
|
||||
|
||||
## What's next
|
||||
|
||||
* Read more about the [egress service]({{home}}/docs/concepts/traffic-management/request-routing.html#ingress-and-egress-envoys).
|
||||
|
|
|
@ -102,3 +102,7 @@ continue without any errors.
|
|||
* Learn more about [fault injection]({{home}}/docs/concepts/traffic-management/fault-injection.html).
|
||||
|
||||
* Limit requests to the BookInfo `ratings` service with Istio [rate limiting](./rate-limiting.html).
|
||||
|
||||
* If you are not planning to explore any follow-on tasks, refer to the
|
||||
[BookInfo cleanup]({{home}}/docs/samples/bookinfo.html#cleanup) instructions
|
||||
to shutdown the application and cleanup the associated rules.
|
||||
|
|
|
@ -301,7 +301,7 @@ We also showed how to control the ingress traffic using an Istio route rule.
|
|||
|
||||
```bash
|
||||
istioctl delete route-rule httpbin-3s-rule
|
||||
kubectl delete ingress istio-ingress secured-ingress
|
||||
kubectl delete ingress simple-ingress secured-ingress
|
||||
kubectl delete secret ingress-secret
|
||||
```
|
||||
|
||||
|
@ -311,6 +311,7 @@ We also showed how to control the ingress traffic using an Istio route rule.
|
|||
kubectl delete -f samples/apps/httpbin/httpbin.yaml
|
||||
```
|
||||
|
||||
|
||||
## What's next
|
||||
|
||||
* Learn more about [routing rules]({{home}}/docs/concepts/traffic-management/rules-configuration.html).
|
||||
|
|
|
@ -258,3 +258,7 @@ Config API to add support for creating new descriptors.
|
|||
* Discover the full [Attribute Vocabulary]({{home}}/docs/reference/config/mixer/attribute-vocabulary.html).
|
||||
|
||||
* Read the reference guide to [Writing Config]({{home}}/docs/reference/writing-config.html).
|
||||
|
||||
* If you are not planning to explore any follow-on tasks, refer to the
|
||||
[BookInfo cleanup]({{home}}/docs/samples/bookinfo.html#cleanup) instructions
|
||||
to shutdown the application and cleanup the associated rules.
|
||||
|
|
|
@ -164,3 +164,7 @@ the following config validation error if any labels are missing.
|
|||
* Discover the full [Attribute Vocabulary]({{home}}/docs/reference/config/mixer/attribute-vocabulary.html).
|
||||
|
||||
* Read the reference guide to [Writing Config]({{home}}/docs/reference/writing-config.html).
|
||||
|
||||
* If you are not planning to explore any follow-on tasks, refer to the
|
||||
[BookInfo cleanup]({{home}}/docs/samples/bookinfo.html#cleanup) instructions
|
||||
to shutdown the application and cleanup the associated rules.
|
||||
|
|
|
@ -175,3 +175,7 @@ that we created exclusively for him:
|
|||
* Learn more about [request routing]({{home}}/docs/concepts/traffic-management/rules-configuration.html).
|
||||
|
||||
* Test the BookInfo application resiliency by [injecting faults](./fault-injection.html).
|
||||
|
||||
* If you are not planning to explore any follow-on tasks, refer to the
|
||||
[BookInfo cleanup]({{home}}/docs/samples/bookinfo.html#cleanup) instructions
|
||||
to shutdown the application and cleanup the associated rules.
|
||||
|
|
|
@ -123,3 +123,7 @@ the timeout is specified in millisecond (instead of second) units.
|
|||
* Learn more about [failure handling]({{home}}/docs/concepts/traffic-management/handling-failures.html).
|
||||
|
||||
* Learn more about [routing rules]({{home}}/docs/concepts/traffic-management/rules-configuration.html).
|
||||
|
||||
* If you are not planning to explore any follow-on tasks, refer to the
|
||||
[BookInfo cleanup]({{home}}/docs/samples/bookinfo.html#cleanup) instructions
|
||||
to shutdown the application and cleanup the associated rules.
|
||||
|
|
|
@ -158,3 +158,7 @@ When you make downstream calls, make sure to include those headers.
|
|||
* Discover the full [Attribute Vocabulary]({{home}}/docs/reference/config/mixer/attribute-vocabulary.html).
|
||||
|
||||
* Read the reference guide to [Writing Config]({{home}}/docs/reference/writing-config.html).
|
||||
|
||||
* If you are not planning to explore any follow-on tasks, refer to the
|
||||
[BookInfo cleanup]({{home}}/docs/samples/bookinfo.html#cleanup) instructions
|
||||
to shutdown the application and cleanup the associated rules.
|
||||
|
|
Loading…
Reference in New Issue