-
Task
-
Resolution: Done
-
Major
-
Maistra-0.1.0
-
None
-
None
Starting OpenShift/Istio with:
istiooc cluster up --enable=*,istio
oc create -n istio-operator -f {yaml file}
where the yaml file contains:
apiVersion: "istio.openshift.com/v1alpha1"
kind: "Installation"
metadata:
name: "istio-installation"
spec:
deployment_type: openshift
istio:
authentication: true
community: false
prefix: "brew-pulp-docker01.web.prod.ext.phx2.redhat.com:8888/openshift-istio-tech-preview/"
version: 0.1.0
jaeger:
prefix: "brew-pulp-docker01.web.prod.ext.phx2.redhat.com:8888/distributed-tracing-tech-preview/"
version: 1.6.0
elasticsearch_memory: 1Gi
kiali:
username: admin
password: admin
prefix: kiali/
version: v0.6
And then deploying the services in https://github.com/kenfinnigan/mesh-microprofile-2018, invoking a request from the UI doesn't result in the proper trace information being available in the Jaeger UI.
A similar problem occurred in the past with traces not reaching the jaeger-collector when mTLS is enabled, but that was resolved. It might be a re occurrence.
