|
Important
|
The Jaeger Operator version is related to the version of the Jaeger components (Query, Collector, Agent) up to the minor portion. The patch version portion does not follow the ones from the Jaeger components. For instance, the Operator version 1.8.1 uses the Jaeger Docker images tagged with version 1.8 by default. |
|
Note
|
Make sure your kubectl command is properly configured to talk to a valid Kubernetes cluster. If you don’t have one yet, check minikube out.
|
To install the operator, run:
kubectl create -f https://raw.githubusercontent.com/jaegertracing/jaeger-operator/master/deploy/crds/io_v1alpha1_jaeger_crd.yaml
kubectl create -f https://raw.githubusercontent.com/jaegertracing/jaeger-operator/master/deploy/service_account.yaml
kubectl create -f https://raw.githubusercontent.com/jaegertracing/jaeger-operator/master/deploy/role.yaml
kubectl create -f https://raw.githubusercontent.com/jaegertracing/jaeger-operator/master/deploy/role_binding.yaml
kubectl create -f https://raw.githubusercontent.com/jaegertracing/jaeger-operator/master/deploy/operator.yamlAt this point, there should be a jaeger-operator deployment available:
$ kubectl get deployment jaeger-operator
NAME DESIRED CURRENT UP-TO-DATE AVAILABLE AGE
jaeger-operator 1 1 1 1 48sThe operator is now ready to create Jaeger instances!
The instructions from the previous section also work on OpenShift given that the operator-openshift.yaml is used instead of operator.yaml. Make sure to install the RBAC rules, the CRD and the operator as a privileged user, such as system:admin.
oc login -u system:admin
oc create -f https://raw.githubusercontent.com/jaegertracing/jaeger-operator/master/deploy/crds/io_v1alpha1_jaeger_crd.yaml
oc create -f https://raw.githubusercontent.com/jaegertracing/jaeger-operator/master/deploy/service_account.yaml
oc create -f https://raw.githubusercontent.com/jaegertracing/jaeger-operator/master/deploy/role.yaml
oc create -f https://raw.githubusercontent.com/jaegertracing/jaeger-operator/master/deploy/role_binding.yaml
oc create -f https://raw.githubusercontent.com/jaegertracing/jaeger-operator/master/deploy/operator-openshift.yamlOnce the operator is installed, grant the role jaeger-operator to users who should be able to install individual Jaeger instances. The following example creates a role binding allowing the user developer to create Jaeger instances:
oc create \
rolebinding developer-jaeger-operator \
--role=jaeger-operator \
--user=developerAfter the role is granted, switch back to a non-privileged user.
Example custom resources, for different configurations of Jaeger, can be found here.
The simplest possible way to install is by creating a YAML file like the following:
apiVersion: io.jaegertracing/v1alpha1
kind: Jaeger
metadata:
name: simplestThe YAML file can then be used with kubectl:
kubectl apply -f simplest.yamlIn a few seconds, a new in-memory all-in-one instance of Jaeger will be available, suitable for quick demos and development purposes. To check the instances that were created, list the jaeger objects:
$ kubectl get jaeger
NAME CREATED AT
simplest 28sTo get the pod name, query for the pods belonging to the simplest Jaeger instance:
$ kubectl get pods -l jaeger=simplest
NAME READY STATUS RESTARTS AGE
simplest-6499bb6cdd-kqx75 1/1 Running 0 2mSimilarly, the logs can be queried either from the pod directly using the pod name obtained from the previous example, or from all pods belonging to our instance:
$ kubectl logs -l jaeger=simplest
...
{"level":"info","ts":1535385688.0951214,"caller":"healthcheck/handler.go:133","msg":"Health Check state change","status":"ready"}For reference, here’s how a more complex all-in-one instance can be created:
apiVersion: io.jaegertracing/v1alpha1
kind: Jaeger
metadata:
name: my-jaeger
spec:
strategy: allInOne # (1)
allInOne:
image: jaegertracing/all-in-one:1.9 # (2)
options: # (3)
log-level: debug # (4)
storage:
type: memory # (5)
options: # (6)
memory: # (7)
max-traces: 100000
ingress:
enabled: false # (8)
agent:
strategy: DaemonSet # (9)
annotations:
scheduler.alpha.kubernetes.io/critical-pod: "" # (10)-
The default strategy is
allInOne. The only other possible values areproductionandstreaming. -
The image to use, in a regular Docker syntax
-
The (non-storage related) options to be passed verbatim to the underlying binary. Refer to the Jaeger documentation and/or to the
--helpoption from the related binary for all the available options. -
The option is a simple
key: valuemap. In this case, we want the option--log-level=debugto be passed to the binary. -
The storage type to be used. By default it will be
memory, but can be any other supported storage type (e.g. elasticsearch, cassandra, kafka, etc). -
All storage related options should be placed here, rather than under the 'allInOne' or other component options.
-
Some options are namespaced and we can alternatively break them into nested objects. We could have specified
memory.max-traces: 100000. -
By default, an ingress object is created for the query service. It can be disabled by setting its
enabledoption tofalse. If deploying on OpenShift, this will be represented by a Route object. -
By default, the operator assumes that agents are deployed as sidecars within the target pods. Specifying the strategy as "DaemonSet" changes that and makes the operator deploy the agent as DaemonSet. Note that your tracer client will probably have to override the "JAEGER_AGENT_HOST" env var to use the node’s IP.
-
Define annotations to be applied to all deployments (not services). These can be overridden by annotations defined on the individual components.
As shown in the example above, the Jaeger instance is associated with a strategy. The strategy determines the architecture to be used for the Jaeger backend.
The available strategies are described in the following sections.
This strategy is intended for development, testing and demo purposes.
The main backend components, agent, collector and query service, are all packaged into a single executable which is configured (by default) to use in-memory storage.
The production strategy is intended (as the name suggests) for production environments, where long term storage of trace data is important, as well as a more scalable and highly available architecture is required. Each of the backend components is therefore separately deployed.
The agent can be injected as a sidecar on the instrumented application or as a daemonset.
The query and collector services are configured with a supported storage type - currently cassandra or elasticsearch. Multiple instances of each of these components can be provisioned as required for performance and resilience purposes.
The main additional requirement is to provide the details of the storage type and options, e.g.
storage:
type: elasticsearch
options:
es:
server-urls: http://elasticsearch:9200The streaming strategy is designed to augment the production strategy by providing a streaming capability that effectively sits between the collector and the backend storage (e.g. cassandra or elasticsearch). This provides the benefit of reducing the pressure on the backend storage, under high load situations, and enables other trace post processing capabilities to tap into the real time span data directly from the streaming platform (kafka).
The only additional information required is to provide the details for accessing the Kafka platform, which is configured in a new ingester component:
apiVersion: io.jaegertracing/v1alpha1
kind: Jaeger
metadata:
name: simple-streaming
spec:
strategy: streaming
ingester:
options:
kafka: # (1)
topic: jaeger-spans
brokers: my-cluster-kafka-brokers.kafka:9092
ingester:
deadlockInterval: 0 # (2)
storage:
type: elasticsearch
options:
es:
server-urls: http://elasticsearch:9200-
Identifies the kafka configuration used by the collector, to produce the messages, and the ingester to consume the messages
-
The deadlock interval can be disabled to avoid the ingester being terminated when no messages arrive within the default 1 minute period
The operator creates a Kubernetes ingress route, which is the Kubernetes' standard for exposing a service to the outside world, but it comes with no Ingress providers by default. Check the documentation on what’s the most appropriate way to achieve that for your platform, but the following commands should provide a good start on minikube:
minikube addons enable ingressOnce that is done, the UI can be found by querying the Ingress object:
$ kubectl get ingress
NAME HOSTS ADDRESS PORTS AGE
simplest-query * 192.168.122.34 80 3m|
Important
|
an Ingress object is not created when the operator is started with the --platform=openshift flag, such as when using the resource operator-openshift.yaml.
|
In this example, the Jaeger UI is available at http://192.168.122.34
When using the operator-openshift.yaml resource, the Operator will automatically create a Route object for the query services. Check the hostname/port with the following command:
oc get routes|
Note
|
make sure to use https with the hostname/port you get from the command above, otherwise you’ll see a message like: "Application is not available".
|
By default, the Jaeger UI is protected with OpenShift’s OAuth service and any valid user is able to login. For development purposes, the user/password combination developer/developer can be used. To disable this feature and leave the Jaeger UI unsecured, set the Ingress property security to none:
apiVersion: io.jaegertracing/v1alpha1
kind: Jaeger
metadata:
name: disable-oauth-proxy
spec:
ingress:
security: noneThe operator can also inject Jaeger Agent sidecars in Deployment workloads, provided that the deployment has the annotation inject-jaeger-agent with a suitable value. The values can be either "true" (as string), or the Jaeger instance name, as returned by kubectl get jaegers. When "true" is used, there should be exactly one Jaeger instance for the same namespace as the deployment, otherwise, the operator can’t figure out automatically which Jaeger instance to use.
The following snippet shows a simple application that will get a sidecar injected, with the Jaeger Agent pointing to the single Jaeger instance available in the same namespace:
apiVersion: apps/v1
kind: Deployment
metadata:
name: myapp
annotations:
inject-jaeger-agent: "true" # (1)
spec:
selector:
matchLabels:
app: myapp
template:
metadata:
labels:
app: myapp
spec:
containers:
- name: myapp
image: acme/myapp:myversion-
Either
"true"(as string) or the Jaeger instance name
By default, the Operator expects the agents to be deployed as sidecars to the target applications. This is convenient for several purposes, like in a multi-tenant scenario or to have better load balancing, but there are scenarios where it’s desirable to install the agent as a DaemonSet. In that case, specify the Agent’s strategy to DaemonSet, as follows:
apiVersion: io.jaegertracing/v1alpha1
kind: Jaeger
metadata:
name: my-jaeger
spec:
agent:
strategy: DaemonSet|
Important
|
if you attempt to install two Jaeger instances on the same cluster with DaemonSet as the strategy, only one will end up deploying a DaemonSet, as the agent is required to bind to well-known ports on the node. Because of that, the second daemon set will fail to bind to those ports.
|
Your tracer client will then most likely need to be told where the agent is located. This is usually done by setting the env var JAEGER_AGENT_HOST and should be set to the value of the Kubernetes node’s IP, like:
apiVersion: apps/v1
kind: Deployment
metadata:
name: myapp
spec:
selector:
matchLabels:
app: myapp
template:
metadata:
labels:
app: myapp
spec:
containers:
- name: myapp
image: acme/myapp:myversion
env:
- name: JAEGER_AGENT_HOST
valueFrom:
fieldRef:
fieldPath: status.hostIPThe Operator supports passing secrets to the Collector, Query and All-In-One deployments. This can be used for example, to pass credentials (username/password) to access the underlying storage backend (for ex: Elasticsearch). The secrets are available as environment variables in the (Collector/Query/All-In-One) nodes.
storage:
type: elasticsearch
options:
es:
server-urls: http://elasticsearch:9200
secretName: jaeger-secretsThe secret itself would be managed outside of the jaeger-operator CR.
The operator can be used to define sampling strategies that will be supplied to tracers that have been configured to use a remote sampler:
apiVersion: io.jaegertracing/v1alpha1
kind: Jaeger
metadata:
name: with-sampling
spec:
strategy: allInOne
sampling:
options:
default_strategy:
type: probabilistic
param: 50This example defines a default sampling strategy that is probabilistic, with a 50% chance of the trace instances being sampled.
Refer to the Jaeger documentation on Collector Sampling Configuration to see how service and endpoint sampling can be configured. The JSON representation described in that documentation can be used in the operator by converting to YAML.
When the storage type is set to Cassandra, the operator will automatically create a batch job that creates the required schema for Jaeger to run. This batch job will block the Jaeger installation, so that it starts only after the schema is successfuly created. The creation of this batch job can be disabled by setting the enabled property to false:
apiVersion: io.jaegertracing/v1alpha1
kind: Jaeger
metadata:
name: cassandra-without-create-schema
spec:
strategy: allInOne
storage:
type: cassandra
cassandraCreateSchema:
enabled: false # (1)-
Defaults to
true
Further aspects of the batch job can be configured as well. An example with all the possible options is shown below:
apiVersion: io.jaegertracing/v1alpha1
kind: Jaeger
metadata:
name: cassandra-with-create-schema
spec:
strategy: allInOne # (1)
storage:
type: cassandra
options: # (2)
cassandra:
servers: cassandra
keyspace: jaeger_v1_datacenter3
cassandraCreateSchema: # (3)
datacenter: "datacenter3"
mode: "test"-
The same works for
productionandstreaming -
These options are for the regular Jaeger components, like
collectorandquery -
The options for the
create-schemajob
|
Note
|
the default create-schema job uses MODE=prod, which implies a replication factor of 2, using NetworkTopologyStrategy as the class, effectively meaning that at least 3 nodes are required in the Cassandra cluster. If a SimpleStrategy is desired, set the mode to test, which then sets the replication factor of 1. Refer to the create-schema script for more details.
|
To remove an instance, just use the delete command with the file used for the instance creation:
kubectl delete -f simplest.yamlAlternatively, you can remove a Jaeger instance by running:
kubectl delete jaeger simplest|
Note
|
deleting the instance will not remove the data from a permanent storage used with this instance. Data from in-memory instances, however, will be lost. |
Similar to the installation, just run:
kubectl delete -f https://raw.githubusercontent.com/jaegertracing/jaeger-operator/master/deploy/operator.yaml
kubectl delete -f https://raw.githubusercontent.com/jaegertracing/jaeger-operator/master/deploy/role_binding.yaml
kubectl delete -f https://raw.githubusercontent.com/jaegertracing/jaeger-operator/master/deploy/role.yaml
kubectl delete -f https://raw.githubusercontent.com/jaegertracing/jaeger-operator/master/deploy/service_account.yaml
kubectl delete -f https://raw.githubusercontent.com/jaegertracing/jaeger-operator/master/deploy/crds/io_v1alpha1_jaeger_crd.yaml