App Mesh Jaeger Helm chart for Kubernetes
- Kubernetes >= 1.13
Add the EKS repository to Helm:
helm repo add eks https://aws.github.io/eks-chartsInstall App Mesh Jaeger:
helm upgrade -i appmesh-jaeger eks/appmesh-jaeger \
--namespace appmesh-systemFor Jaeger persistent storage you can create a PersistentVolumeClaim
and use --set persistentVolumeClaim.claimName=<PVC-CLAIM-NAME>.
Enable Jaeger tracing for the App Mesh data plane:
helm upgrade -i appmesh-controller eks/appmesh-controller \
--namespace appmesh-system \
--set tracing.enabled=true \
--set tracing.provider=jaeger \
--set tracing.address=appmesh-jaeger.appmesh-system \
--set tracing.port=9411Note that you should restart all pods running inside the mesh after enabling tracing.
The configuration section lists the parameters that can be configured during installation.
To uninstall/delete the appmesh-jaeger deployment:
helm delete appmesh-jaeger -n appmesh-systemThe command removes all the Kubernetes components associated with the chart and deletes the release.
The following tables lists the configurable parameters of the chart and their default values.
| Parameter | Description | Default |
|---|---|---|
image.repository |
image repository | jaegertracing/all-in-one |
image.tag |
image tag | <VERSION> |
image.pullPolicy |
image pull policy | IfNotPresent |
resources.requests/cpu |
pod CPU request | 100m |
resources.requests/memory |
pod memory request | 256Mi |
resources.limits/cpu |
pod CPU limit | 2000m |
resources.limits/memory |
pod memory limit | 2Gi |
probes.liveness.initialDelaySeconds |
seconds to delay liveness probing | 0 |
probes.liveness.periodSeconds |
interval between liveness probing | 10 |
probes.liveness.timeoutSeconds |
timeout for liveness probe | 1 |
probes.liveness.successThreshold |
minimum consecutive successes for probe to be considered successful | 1 |
probes.liveness.failureThreshold |
minimum consecutive fails for probe to be considered failed | 3 |
probes.readiness.initialDelaySeconds |
seconds to delay readiness probing | 0 |
probes.readiness.periodSeconds |
interval between readiness probing | 10 |
probes.readiness.timeoutSeconds |
timeout for readiness probe | 1 |
probes.readiness.successThreshold |
minimum consecutive successes for probe to be considered successful | 1 |
probes.readiness.failureThreshold |
minimum consecutive fails for probe to be considered failed | 3 |
affinity |
node/pod affinities | None |
nodeSelector |
node labels for pod assignment | {} |
tolerations |
list of node taints to tolerate | [] |
rbac.create |
if true, create and use RBAC resources |
true |
rbac.pspEnabled |
If true, create and use a restricted pod security policy |
false |
serviceAccount.create |
If true, create a new service account |
true |
serviceAccount.name |
Service account to be used | None |
memory.maxTraces |
The amount of traces stored in memory | 40000 |
persistentVolumeClaim.claimName |
Specify an existing volume claim to be used for Badger data | None |