diff options
| author |   Eddie Arrage <eddie.arrage@huawei.com> | 2018-04-24 23:48:09 +0000 |
|---|---|---|
| committer | Eddie Arrage <eddie.arrage@huawei.com> | 2018-04-24 23:49:49 +0000 |
| commit | 0ce5bc7e3df6f021f2c103de5777f655161388ab (patch) | |
| tree | dda69e3f3f229325db02aaf07e3999b54db3dc01 /docs/tracing.rst | |
| parent | 8d8abe26ba133345213b4afaca729659ad81c385 (diff) | |
Modified validation script for tracing to support CI
- Manual cherry pick to stable/fraser of patch:
https://gerrit.opnfv.org/gerrit/#/c/55387/
Change-Id: I965326b30b2f6266f147de77c4064833856aa186
Signed-off-by: Eddie Arrage <eddie.arrage@huawei.com>
Diffstat (limited to 'docs/tracing.rst')
| -rw-r--r-- | docs/tracing.rst | 19 |
1 files changed, 13 insertions, 6 deletions
diff --git a/docs/tracing.rst b/docs/tracing.rst index 79d686c..b83274c 100644 --- a/docs/tracing.rst +++ b/docs/tracing.rst @@ -13,20 +13,26 @@ following command:: kubectl apply -n istio-system -f https://raw.githubusercontent.com/jaegertracing/jaeger-kubernetes/master/all-in-one/jaeger-all-in-one-template.yml The standard Jaeger REST port is at 16686. To make this service available outside of the -Kubernetes cluster, use the following command:: +Kubernetes cluster via any node IP in the cluster, use the following command:: kubectl expose -n istio-system deployment jaeger-deployment --port=16686 --type=NodePort -Kubernetes will expose the Jaeger service on another port, which can be found with:: +Kubernetes will expose the Jaeger service on another port from 30000-32767 and the assignment can +be found with:: kubectl get svc -n istio-system An example listing from the command above is shown below where the Jaeger service is exposed -externally on port 30888:: +externally on port 30888 in this case:: istio-system jaeger-deployment NodePort 10.104.113.94 <none> 16686:30888/TCP -Jaeger will be accessible using the host IP of the Kubernetes cluster and port provided. +Jaeger will be accessible using the host IP of any node in Kubernetes cluster and port provided. +With this method, the Jaeger UI will also be available from a remote host. If external access is +required to Jaeger but restricted to cluster localhost(s), an alternate method is to use the +**port-forward** command in the foreground, as shown below:: + + kubectl -n istio-system port-forward $(kubectl -n istio-system get pod -l app=jaeger -o jsonpath='{.items[0].metadata.name}') 16686:16686 ******** Validate @@ -40,5 +46,6 @@ It validates the installation with the following criteria: #. Existence of Jaeger all-in-one deployment using Kubernetes #. Jaeger service is accessible using IP address and port configured in installation steps -#. Jaeger can retrieve default service listing for default Istio components -#. TBD - consider installation of production setup with cassandra or elastic search +#. Optionally, if Jaeger can retrieve service listing for default Istio components + (istio-ingress, istio-mixer). At least one HTTP request must be sent to istio-ingress + after initial Jaeger deployment for this validation to function. |