* [Stable/jaeger-operator] Update readme This commit address changes from v1.10.0 to v1.11.0 by updating the readme Reference link https://github.com/jaegertracing/jaeger-operator/blob/master/README.adoc#installing-the-operator Signed-off-by: Luong Vo <vo.tran.thanh.luong@gmail.com> * Bump chart version Signed-off-by: Luong Vo <vo.tran.thanh.luong@gmail.com>
jaeger-operator
jaeger-operator is a Kubernetes operator.
Install
$ helm install stable/jaeger-operator
Introduction
This chart bootstraps a jaeger-operator deployment on a Kubernetes cluster using the Helm package manager.
Prerequisites
- Kubernetes 1.8+ with Beta APIs enabled
Installing the Chart
To install the chart with the release name my-release:
$ helm install --name my-release stable/jaeger-operator
The command deploys jaeger-operator on the Kubernetes cluster in the default configuration. The configuration section lists the parameters that can be configured during installation.
Tip
: List all releases using
helm list
Uninstalling the Chart
To uninstall/delete the my-release deployment:
$ helm delete my-release
The command removes all the Kubernetes components associated with the chart and deletes the release.
Configuration
The following table lists the configurable parameters of the jaeger-operator chart and their default values.
| Parameter | Description | Default |
|---|---|---|
image.repository |
Controller container image repository | jaegertracing/jaeger-operator |
image.tag |
Controller container image tag | 1.11.0 |
image.pullPolicy |
Controller container image pull policy | IfNotPresent |
rbac.create |
All required roles and rolebindings will be created | true |
serviceAccount.create |
Service account to use | true |
serviceAccount.name |
Service account name to use. If not set and create is true, a name is generated using the fullname template | `` |
resources |
K8s pod resorces | None |
nodeSelector |
Node labels for pod assignment | {} |
tolerations |
Toleration labels for pod assignment | [] |
affinity |
Affinity settings for pod assignment | {} |
Specify each parameter you'd like to override using a YAML file as described above in the installation section.
You can also specify any non-array parameter using the --set key=value[,key=value] argument to helm install. For example,
$ helm install stable/jaeger-operator --name my-release \
--set rbac.create=false
After the Helm Installation
Creating a new Jaeger instance
The simplest possible way to install is by creating a YAML file like the following:
apiVersion: jaegertracing.io/v1
kind: Jaeger
metadata:
name: simplest
The YAML file can then be used with kubectl:
$ kubectl apply -f simplest.yaml
Creating a new Jaeger with ElasticSearch
To do that you need to have an ElasticSearch installed in your Kubernetes cluster or install one using the Helm Chart available for that.
After that just deploy the following manifest:
# setup an elasticsearch with `make es`
apiVersion: jaegertracing.io/v1
kind: Jaeger
metadata:
name: simple-prod
spec:
strategy: production
storage:
type: elasticsearch
options:
es:
server-urls: http://elasticsearch:9200
username: elastic
password: changeme
The YAML file can then be used with kubectl:
$ kubectl apply -f simple-prod.yaml