jaegertracing / helm-charts Goto Github PK
View Code? Open in Web Editor NEWHelm Charts for Jaeger backend
License: Apache License 2.0
Helm Charts for Jaeger backend
License: Apache License 2.0
Based on https://www.jaegertracing.io/docs/1.18/frontend-ui/#configuration, It says a JSON file can be passed in as configuration.
Similar to how for Collector's strategy file strategies.json we can create a configmap template for the jaeger query UI config JSON file .
this would make it easy for users to pass in configuration in the values file.
I can add it in , since i already created a configMap for my own purposes.
Hi Team,
Can you please provide the custom labels support in query-ing.yaml.
For example :-
{{- toYaml .Values.query.ingress.labels | nindent 4 }}
Thanks
I recently updated my Jaeger-Operator's chart from 2.10.2
to 2.12.3
, and got an error with Helm:
$ helm history -o json jaeger-operator | jq .
[
{
"revision": 623,
"updated": "Tue Oct 29 11:33:18 2019",
"status": "DEPLOYED",
"chart": "jaeger-operator-2.10.2",
"description": "Upgrade complete"
},
{
"revision": 624,
"updated": "Thu Jan 16 15:11:11 2020",
"status": "FAILED",
"chart": "jaeger-operator-2.12.3",
"description": "Upgrade \"jaeger-operator\" failed: Deployment.apps \"jaeger-operator\" is invalid: spec.selector: Invalid value: v1.LabelSelector{MatchLabels:map[string]string{\"app.kubernetes.io/name\":\"jaeger-operator\"}, MatchExpressions:[]v1.LabelSelectorRequirement(nil)}: field is immutable"
}
]
I couldn't find any info about this error in the README. So I started to look around, and found out these errors were probably due to a change in the label selectors of the Jaeger-Operator deployment: doing so is not allowed by Kubernetes, as these fields are immutable.
By deleting the deployment and reinstalling the chart, I finally solved my problem:
$ kub delete deploy jaeger-operator
$ helm rollback jaeger-operator 624
I assume other people probably also got this error (or will in the future), and that adding a note in the README
could be really useful π
Installing jaeger
helm chart into a customized namespace tracing
using this helm command, that creates elasticsearch as well.
helm upgrade --install jaeger jaegertracing/jaeger \
--set hotrod.enabled=trueΒ \
--set provisionDataStore.cassandra=falseΒ Β \
--set provisionDataStore.elasticsearch=trueΒ \
--set storage.type=elasticsearch \
--set collector.service.zipkinPort=9411Β \
-n tracing --debug
The jaeger-collector deployment assigns jaeger-elasticsearch-client
as the host
- name: ES_SERVER_URLS
value: http://jaeger-elasticsearch-client:9200
but it is not reachable because the ElasticSearch client is created in tracing
namespace.
It should be:
- name: ES_SERVER_URLS
value: http://jaeger-elasticsearch-client.tracing:9200
Deploying jaeger results in the following error:
Error: container has runAsNonRoot and image will run as root
Deploy script:
helm upgrade jaeger vendor/jaeger-helm-charts/charts/jaeger \
-n monitoring \
-f vendor/jaeger-helm-charts/charts/jaeger/values.yaml \
-f src/monitoring/jaeger/values.yaml \
-i $@
src/monitoring/jaeger/values.yaml
:
# Default values for jaeger are specified in
# vendor/jaeger-helm-charts/charts/jaeger/values.yaml
provisionDataStore:
cassandra: false
elasticsearch: false
kafka: false
storage:
type: elasticsearch
elasticsearch:
scheme: http
# NOTE(msschl): cluster internal only. Not reachable from outside...
host: elasticsearch-master.elasticsearch.svc.k8s-cluster.company.xyz
port: 9200
usePassword: false
query:
ingress:
enabled: true
hosts:
- tracing.kube-dev.company.xyz
annotations:
kubernetes.io/ingress.class: "nginx-ingress"
tls:
- secretName: "public/company-tls"
hosts:
- tracing.kube-dev.company.xyz
# QUESTION(msschl): Enable?
esIndexCleaner:
enabled: false
We do have a default psp policy in place and its bound to the deployed jaeger pods:
apiVersion: policy/v1beta1
kind: PodSecurityPolicy
metadata:
name: default-restricted
annotations:
seccomp.security.alpha.kubernetes.io/allowedProfileNames: 'runtime/default'
apparmor.security.beta.kubernetes.io/allowedProfileNames: 'runtime/default'
seccomp.security.alpha.kubernetes.io/defaultProfileName: 'runtime/default'
apparmor.security.beta.kubernetes.io/defaultProfileName: 'runtime/default'
spec:
allowedCapabilities: []
privileged: false
allowPrivilegeEscalation: false
requiredDropCapabilities:
- ALL
volumes:
- 'configMap'
- 'secret'
- 'persistentVolumeClaim'
hostNetwork: false
hostIPC: false
hostPID: false
runAsUser:
rule: 'MustRunAsNonRoot'
seLinux:
rule: 'RunAsAny'
supplementalGroups:
rule: 'MustRunAs'
ranges:
- min: 1
max: 65535
fsGroup:
rule: 'MustRunAs'
ranges:
- min: 1
max: 65535
readOnlyRootFilesystem: true
Full description from agent pod:
$ kubectl -n monitoring describe po jaeger-agent-ndzwz
Name: jaeger-agent-ndzwz
Namespace: monitoring
Priority: 0
Node: lxkubenode02/172.18.2.93
Start Time: Fri, 15 May 2020 17:36:33 +0200
Labels: app.kubernetes.io/component=agent
app.kubernetes.io/instance=jaeger
app.kubernetes.io/name=jaeger
controller-revision-hash=6ff9dcbc57
pod-template-generation=1
Annotations: cni.projectcalico.org/podIP: 10.244.206.69/32
cni.projectcalico.org/podIPs: 10.244.206.69/32
container.apparmor.security.beta.kubernetes.io/jaeger-agent: runtime/default
kubernetes.io/psp: default-restricted
seccomp.security.alpha.kubernetes.io/pod: runtime/default
Status: Pending
IP: 10.244.206.69
IPs:
IP: 10.244.206.69
Controlled By: DaemonSet/jaeger-agent
Containers:
jaeger-agent:
Container ID:
Image: jaegertracing/jaeger-agent:1.17.1
Image ID:
Ports: 5775/UDP, 6831/UDP, 6832/UDP, 5778/TCP, 14271/TCP
Host Ports: 0/UDP, 0/UDP, 0/UDP, 0/TCP, 0/TCP
State: Waiting
Reason: CreateContainerConfigError
Ready: False
Restart Count: 0
Liveness: http-get http://:admin/ delay=0s timeout=1s period=10s #success=1 #failure=3
Readiness: http-get http://:admin/ delay=0s timeout=1s period=10s #success=1 #failure=3
Environment:
REPORTER_GRPC_HOST_PORT: jaeger-collector:14250
Mounts:
/var/run/secrets/kubernetes.io/serviceaccount from jaeger-agent-token-s2hzt (ro)
Conditions:
Type Status
Initialized True
Ready False
ContainersReady False
PodScheduled True
Volumes:
jaeger-agent-token-s2hzt:
Type: Secret (a volume populated by a Secret)
SecretName: jaeger-agent-token-s2hzt
Optional: false
QoS Class: BestEffort
Node-Selectors: <none>
Tolerations: node.kubernetes.io/disk-pressure:NoSchedule
node.kubernetes.io/memory-pressure:NoSchedule
node.kubernetes.io/not-ready:NoExecute
node.kubernetes.io/pid-pressure:NoSchedule
node.kubernetes.io/unreachable:NoExecute
node.kubernetes.io/unschedulable:NoSchedule
Events:
Type Reason Age From Message
---- ------ ---- ---- -------
Normal Scheduled <unknown> default-scheduler Successfully assigned monitoring/jaeger-agent-ndzwz to lxkubenode02
Normal Pulling 6s (x4 over 25s) kubelet, lxkubenode02 Pulling image "jaegertracing/jaeger-agent:1.17.1"
Normal Pulled 5s (x4 over 24s) kubelet, lxkubenode02 Successfully pulled image "jaegertracing/jaeger-agent:1.17.1"
Warning Failed 5s (x4 over 24s) kubelet, lxkubenode02 Error: container has runAsNonRoot and image will run as root
Hello,
Will a PR to enable the memory backend be accepted?
I would like to deploy jaeger to a dev cluster but don't want to deploy cassandra or elasticsearch
Ciaran
The environment variable to support ES_TAGS_AS_FIELDS_ALL is missing in the chart.
Jaeger Operator 1.16 introduced self-tracing but there's no obvious way to enable that in the Helm chart deployment.
Since it depends on the namespace (and name) of the Jaeger instance to use, it would have to be configurable, so wouldn't be on-by-default.
Interactions with strimzi operator fail due to missing RBAC.
The following change in jaeger-operator deployment has not been integrated into the chart:
jaegertracing/jaeger-operator@b6211a4#diff-4374306bd7fd15cc09428b7ccf9bbec8
PR coming soon.
I installed jaeger-operator chart version 2.14.0 with default values and get some problems (I'll link issue with actual problems later).
Operator pod's logs linked bellow:
time="2020-03-25T19:06:36Z" level=info msg=Versions arch=amd64 identity=jaeger.jaeger-operator jaeger=1.17.0 jaeger-operator=v1.17.0 operator-sdk=v0.15.1 os=linux version=go1.13.3
time="2020-03-25T19:06:37Z" level=info msg="Consider running the operator in a cluster-wide scope for extra features"
time="2020-03-25T19:06:38Z" level=info msg="Auto-detected the platform" platform=kubernetes
time="2020-03-25T19:06:38Z" level=info msg="Automatically adjusted the 'es-provision' flag" es-provision=no
time="2020-03-25T19:06:38Z" level=info msg="Automatically adjusted the 'kafka-provision' flag" kafka-provision=no
time="2020-03-25T19:06:38Z" level=info msg="The service account running this operator does not have the role 'system:auth-delegator', consider granting it for additional capabilities"
time="2020-03-25T19:06:40Z" level=warning msg="could not create ServiceMonitor object" error="servicemonitors.monitoring.coreos.com \"jaeger-operator-metrics\" already exists"
time="2020-03-25T19:06:40Z" level=info msg="Storage type not provided. Falling back to 'memory'" instance=jaeger namespace=jaeger
E0325 19:06:41.586604 1 reflector.go:123] pkg/mod/k8s.io/[email protected]/tools/cache/reflector.go:96: Failed to list *v2beta2.HorizontalPodAutoscaler: horizontalpodautoscalers.autoscaling is forbidden: User "system:serviceaccount:jaeger:jaeger-operator" cannot list resource "horizontalpodautoscalers" in API group "autoscaling" in the namespace "jaeger"
E0325 19:06:42.588331 1 reflector.go:123] pkg/mod/k8s.io/[email protected]/tools/cache/reflector.go:96: Failed to list *v2beta2.HorizontalPodAutoscaler: horizontalpodautoscalers.autoscaling is forbidden: User "system:serviceaccount:jaeger:jaeger-operator" cannot list resource "horizontalpodautoscalers" in API group "autoscaling" in the namespace "jaeger"
E0325 19:06:43.590036 1 reflector.go:123] pkg/mod/k8s.io/[email protected]/tools/cache/reflector.go:96: Failed to list *v2beta2.HorizontalPodAutoscaler: horizontalpodautoscalers.autoscaling is forbidden: User "system:serviceaccount:jaeger:jaeger-operator" cannot list resource "horizontalpodautoscalers" in API group "autoscaling" in the namespace "jaeger"
E0325 19:06:44.591980 1 reflector.go:123] pkg/mod/k8s.io/[email protected]/tools/cache/reflector.go:96: Failed to list *v2beta2.HorizontalPodAutoscaler: horizontalpodautoscalers.autoscaling is forbidden: User "system:serviceaccount:jaeger:jaeger-operator" cannot list resource "horizontalpodautoscalers" in API group "autoscaling" in the namespace "jaeger"
E0325 19:06:45.593800 1 reflector.go:123] pkg/mod/k8s.io/[email protected]/tools/cache/reflector.go:96: Failed to list *v2beta2.HorizontalPodAutoscaler: horizontalpodautoscalers.autoscaling is forbidden: User "system:serviceaccount:jaeger:jaeger-operator" cannot list resource "horizontalpodautoscalers" in API group "autoscaling" in the namespace "jaeger"
E0325 19:06:46.595867 1 reflector.go:123] pkg/mod/k8s.io/[email protected]/tools/cache/reflector.go:96: Failed to list *v2beta2.HorizontalPodAutoscaler: horizontalpodautoscalers.autoscaling is forbidden: User "system:serviceaccount:jaeger:jaeger-operator" cannot list resource "horizontalpodautoscalers" in API group "autoscaling" in the namespace "jaeger"
E0325 19:06:47.597640 1 reflector.go:123] pkg/mod/k8s.io/[email protected]/tools/cache/reflector.go:96: Failed to list *v2beta2.HorizontalPodAutoscaler: horizontalpodautoscalers.autoscaling is forbidden: User "system:serviceaccount:jaeger:jaeger-operator" cannot list resource "horizontalpodautoscalers" in API group "autoscaling" in the namespace "jaeger"
E0325 19:06:48.599713 1 reflector.go:123] pkg/mod/k8s.io/[email protected]/tools/cache/reflector.go:96: Failed to list *v2beta2.HorizontalPodAutoscaler: horizontalpodautoscalers.autoscaling is forbidden: User "system:serviceaccount:jaeger:jaeger-operator" cannot list resource "horizontalpodautoscalers" in API group "autoscaling" in the namespace "jaeger"
E0325 19:06:49.601643 1 reflector.go:123] pkg/mod/k8s.io/[email protected]/tools/cache/reflector.go:96: Failed to list *v2beta2.HorizontalPodAutoscaler: horizontalpodautoscalers.autoscaling is forbidden: User "system:serviceaccount:jaeger:jaeger-operator" cannot list resource "horizontalpodautoscalers" in API group "autoscaling" in the namespace "jaeger"
E0325 19:06:50.603865 1 reflector.go:123] pkg/mod/k8s.io/[email protected]/tools/cache/reflector.go:96: Failed to list *v2beta2.HorizontalPodAutoscaler: horizontalpodautoscalers.autoscaling is forbidden: User "system:serviceaccount:jaeger:jaeger-operator" cannot list resource "horizontalpodautoscalers" in API group "autoscaling" in the namespace "jaeger"
E0325 19:06:51.605800 1 reflector.go:123] pkg/mod/k8s.io/[email protected]/tools/cache/reflector.go:96: Failed to list *v2beta2.HorizontalPodAutoscaler: horizontalpodautoscalers.autoscaling is forbidden: User "system:serviceaccount:jaeger:jaeger-operator" cannot list resource "horizontalpodautoscalers" in API group "autoscaling" in the namespace "jaeger"
E0325 19:06:52.607910 1 reflector.go:123] pkg/mod/k8s.io/[email protected]/tools/cache/reflector.go:96: Failed to list *v2beta2.HorizontalPodAutoscaler: horizontalpodautoscalers.autoscaling is forbidden: User "system:serviceaccount:jaeger:jaeger-operator" cannot list resource "horizontalpodautoscalers" in API group "autoscaling" in the namespace "jaeger"
E0325 19:06:53.610830 1 reflector.go:123] pkg/mod/k8s.io/[email protected]/tools/cache/reflector.go:96: Failed to list *v2beta2.HorizontalPodAutoscaler: horizontalpodautoscalers.autoscaling is forbidden: User "system:serviceaccount:jaeger:jaeger-operator" cannot list resource "horizontalpodautoscalers" in API group "autoscaling" in the namespace "jaeger"
E0325 19:06:54.612751 1 reflector.go:123] pkg/mod/k8s.io/[email protected]/tools/cache/reflector.go:96: Failed to list *v2beta2.HorizontalPodAutoscaler: horizontalpodautoscalers.autoscaling is forbidden: User "system:serviceaccount:jaeger:jaeger-operator" cannot list resource "horizontalpodautoscalers" in API group "autoscaling" in the namespace "jaeger"
E0325 19:06:55.614784 1 reflector.go:123] pkg/mod/k8s.io/[email protected]/tools/cache/reflector.go:96: Failed to list *v2beta2.HorizontalPodAutoscaler: horizontalpodautoscalers.autoscaling is forbidden: User "system:serviceaccount:jaeger:jaeger-operator" cannot list resource "horizontalpodautoscalers" in API group "autoscaling" in the namespace "jaeger"
E0325 19:06:56.617051 1 reflector.go:123] pkg/mod/k8s.io/[email protected]/tools/cache/reflector.go:96: Failed to list *v2beta2.HorizontalPodAutoscaler: horizontalpodautoscalers.autoscaling is forbidden: User "system:serviceaccount:jaeger:jaeger-operator" cannot list resource "horizontalpodautoscalers" in API group "autoscaling" in the namespace "jaeger"
E0325 19:06:57.619046 1 reflector.go:123] pkg/mod/k8s.io/[email protected]/tools/cache/reflector.go:96: Failed to list *v2beta2.HorizontalPodAutoscaler: horizontalpodautoscalers.autoscaling is forbidden: User "system:serviceaccount:jaeger:jaeger-operator" cannot list resource "horizontalpodautoscalers" in API group "autoscaling" in the namespace "jaeger"
E0325 19:06:58.620690 1 reflector.go:123] pkg/mod/k8s.io/[email protected]/tools/cache/reflector.go:96: Failed to list *v2beta2.HorizontalPodAutoscaler: horizontalpodautoscalers.autoscaling is forbidden: User "system:serviceaccount:jaeger:jaeger-operator" cannot list resource "horizontalpodautoscalers" in API group "autoscaling" in the namespace "jaeger"
E0325 19:06:59.622586 1 reflector.go:123] pkg/mod/k8s.io/[email protected]/tools/cache/reflector.go:96: Failed to list *v2beta2.HorizontalPodAutoscaler: horizontalpodautoscalers.autoscaling is forbidden: User "system:serviceaccount:jaeger:jaeger-operator" cannot list resource "horizontalpodautoscalers" in API group "autoscaling" in the namespace "jaeger"
E0325 19:07:00.624336 1 reflector.go:123] pkg/mod/k8s.io/[email protected]/tools/cache/reflector.go:96: Failed to list *v2beta2.HorizontalPodAutoscaler: horizontalpodautoscalers.autoscaling is forbidden: User "system:serviceaccount:jaeger:jaeger-operator" cannot list resource "horizontalpodautoscalers" in API group "autoscaling" in the namespace "jaeger"
E0325 19:07:01.626495 1 reflector.go:123] pkg/mod/k8s.io/[email protected]/tools/cache/reflector.go:96: Failed to list *v2beta2.HorizontalPodAutoscaler: horizontalpodautoscalers.autoscaling is forbidden: User "system:serviceaccount:jaeger:jaeger-operator" cannot list resource "horizontalpodautoscalers" in API group "autoscaling" in the namespace "jaeger"
E0325 19:07:02.628659 1 reflector.go:123] pkg/mod/k8s.io/[email protected]/tools/cache/reflector.go:96: Failed to list *v2beta2.HorizontalPodAutoscaler: horizontalpodautoscalers.autoscaling is forbidden: User "system:serviceaccount:jaeger:jaeger-operator" cannot list resource "horizontalpodautoscalers" in API group "autoscaling" in the namespace "jaeger"
E0325 19:07:03.630611 1 reflector.go:123] pkg/mod/k8s.io/[email protected]/tools/cache/reflector.go:96: Failed to list *v2beta2.HorizontalPodAutoscaler: horizontalpodautoscalers.autoscaling is forbidden: User "system:serviceaccount:jaeger:jaeger-operator" cannot list resource "horizontalpodautoscalers" in API group "autoscaling" in the namespace "jaeger"
E0325 19:07:04.632452 1 reflector.go:123] pkg/mod/k8s.io/[email protected]/tools/cache/reflector.go:96: Failed to list *v2beta2.HorizontalPodAutoscaler: horizontalpodautoscalers.autoscaling is forbidden: User "system:serviceaccount:jaeger:jaeger-operator" cannot list resource "horizontalpodautoscalers" in API group "autoscaling" in the namespace "jaeger"
E0325 19:07:05.634346 1 reflector.go:123] pkg/mod/k8s.io/[email protected]/tools/cache/reflector.go:96: Failed to list *v2beta2.HorizontalPodAutoscaler: horizontalpodautoscalers.autoscaling is forbidden: User "system:serviceaccount:jaeger:jaeger-operator" cannot list resource "horizontalpodautoscalers" in API group "autoscaling" in the namespace "jaeger"
E0325 19:07:06.636630 1 reflector.go:123] pkg/mod/k8s.io/[email protected]/tools/cache/reflector.go:96: Failed to list *v2beta2.HorizontalPodAutoscaler: horizontalpodautoscalers.autoscaling is forbidden: User "system:serviceaccount:jaeger:jaeger-operator" cannot list resource "horizontalpodautoscalers" in API group "autoscaling" in the namespace "jaeger"
E0325 19:07:07.638557 1 reflector.go:123] pkg/mod/k8s.io/[email protected]/tools/cache/reflector.go:96: Failed to list *v2beta2.HorizontalPodAutoscaler: horizontalpodautoscalers.autoscaling is forbidden: User "system:serviceaccount:jaeger:jaeger-operator" cannot list resource "horizontalpodautoscalers" in API group "autoscaling" in the namespace "jaeger"
E0325 19:07:08.640510 1 reflector.go:123] pkg/mod/k8s.io/[email protected]/tools/cache/reflector.go:96: Failed to list *v2beta2.HorizontalPodAutoscaler: horizontalpodautoscalers.autoscaling is forbidden: User "system:serviceaccount:jaeger:jaeger-operator" cannot list resource "horizontalpodautoscalers" in API group "autoscaling" in the namespace "jaeger"
E0325 19:07:09.642505 1 reflector.go:123] pkg/mod/k8s.io/[email protected]/tools/cache/reflector.go:96: Failed to list *v2beta2.HorizontalPodAutoscaler: horizontalpodautoscalers.autoscaling is forbidden: User "system:serviceaccount:jaeger:jaeger-operator" cannot list resource "horizontalpodautoscalers" in API group "autoscaling" in the namespace "jaeger"
E0325 19:07:10.644541 1 reflector.go:123] pkg/mod/k8s.io/[email protected]/tools/cache/reflector.go:96: Failed to list *v2beta2.HorizontalPodAutoscaler: horizontalpodautoscalers.autoscaling is forbidden: User "system:serviceaccount:jaeger:jaeger-operator" cannot list resource "horizontalpodautoscalers" in API group "autoscaling" in the namespace "jaeger"
E0325 19:07:11.646544 1 reflector.go:123] pkg/mod/k8s.io/[email protected]/tools/cache/reflector.go:96: Failed to list *v2beta2.HorizontalPodAutoscaler: horizontalpodautoscalers.autoscaling is forbidden: User "system:serviceaccount:jaeger:jaeger-operator" cannot list resource "horizontalpodautoscalers" in API group "autoscaling" in the namespace "jaeger"
E0325 19:07:12.648399 1 reflector.go:123] pkg/mod/k8s.io/[email protected]/tools/cache/reflector.go:96: Failed to list *v2beta2.HorizontalPodAutoscaler: horizontalpodautoscalers.autoscaling is forbidden: User "system:serviceaccount:jaeger:jaeger-operator" cannot list resource "horizontalpodautoscalers" in API group "autoscaling" in the namespace "jaeger"
E0325 19:07:13.650053 1 reflector.go:123] pkg/mod/k8s.io/[email protected]/tools/cache/reflector.go:96: Failed to list *v2beta2.HorizontalPodAutoscaler: horizontalpodautoscalers.autoscaling is forbidden: User "system:serviceaccount:jaeger:jaeger-operator" cannot list resource "horizontalpodautoscalers" in API group "autoscaling" in the namespace "jaeger"
E0325 19:07:14.651872 1 reflector.go:123] pkg/mod/k8s.io/[email protected]/tools/cache/reflector.go:96: Failed to list *v2beta2.HorizontalPodAutoscaler: horizontalpodautoscalers.autoscaling is forbidden: User "system:serviceaccount:jaeger:jaeger-operator" cannot list resource "horizontalpodautoscalers" in API group "autoscaling" in the namespace "jaeger"
E0325 19:07:15.654041 1 reflector.go:123] pkg/mod/k8s.io/[email protected]/tools/cache/reflector.go:96: Failed to list *v2beta2.HorizontalPodAutoscaler: horizontalpodautoscalers.autoscaling is forbidden: User "system:serviceaccount:jaeger:jaeger-operator" cannot list resource "horizontalpodautoscalers" in API group "autoscaling" in the namespace "jaeger"
E0325 19:07:16.656221 1 reflector.go:123] pkg/mod/k8s.io/[email protected]/tools/cache/reflector.go:96: Failed to list *v2beta2.HorizontalPodAutoscaler: horizontalpodautoscalers.autoscaling is forbidden: User "system:serviceaccount:jaeger:jaeger-operator" cannot list resource "horizontalpodautoscalers" in API group "autoscaling" in the namespace "jaeger"
E0325 19:07:17.658187 1 reflector.go:123] pkg/mod/k8s.io/[email protected]/tools/cache/reflector.go:96: Failed to list *v2beta2.HorizontalPodAutoscaler: horizontalpodautoscalers.autoscaling is forbidden: User "system:serviceaccount:jaeger:jaeger-operator" cannot list resource "horizontalpodautoscalers" in API group "autoscaling" in the namespace "jaeger"
E0325 19:07:18.660068 1 reflector.go:123] pkg/mod/k8s.io/[email protected]/tools/cache/reflector.go:96: Failed to list *v2beta2.HorizontalPodAutoscaler: horizontalpodautoscalers.autoscaling is forbidden: User "system:serviceaccount:jaeger:jaeger-operator" cannot list resource "horizontalpodautoscalers" in API group "autoscaling" in the namespace "jaeger"
E0325 19:07:19.661891 1 reflector.go:123] pkg/mod/k8s.io/[email protected]/tools/cache/reflector.go:96: Failed to list *v2beta2.HorizontalPodAutoscaler: horizontalpodautoscalers.autoscaling is forbidden: User "system:serviceaccount:jaeger:jaeger-operator" cannot list resource "horizontalpodautoscalers" in API group "autoscaling" in the namespace "jaeger"
E0325 19:07:20.663733 1 reflector.go:123] pkg/mod/k8s.io/[email protected]/tools/cache/reflector.go:96: Failed to list *v2beta2.HorizontalPodAutoscaler: horizontalpodautoscalers.autoscaling is forbidden: User "system:serviceaccount:jaeger:jaeger-operator" cannot list resource "horizontalpodautoscalers" in API group "autoscaling" in the namespace "jaeger"
E0325 19:07:21.665194 1 reflector.go:123] pkg/mod/k8s.io/[email protected]/tools/cache/reflector.go:96: Failed to list *v2beta2.HorizontalPodAutoscaler: horizontalpodautoscalers.autoscaling is forbidden: User "system:serviceaccount:jaeger:jaeger-operator" cannot list resource "horizontalpodautoscalers" in API group "autoscaling" in the namespace "jaeger"
E0325 19:07:22.667020 1 reflector.go:123] pkg/mod/k8s.io/[email protected]/tools/cache/reflector.go:96: Failed to list *v2beta2.HorizontalPodAutoscaler: horizontalpodautoscalers.autoscaling is forbidden: User "system:serviceaccount:jaeger:jaeger-operator" cannot list resource "horizontalpodautoscalers" in API group "autoscaling" in the namespace "jaeger"
E0325 19:07:23.668687 1 reflector.go:123] pkg/mod/k8s.io/[email protected]/tools/cache/reflector.go:96: Failed to list *v2beta2.HorizontalPodAutoscaler: horizontalpodautoscalers.autoscaling is forbidden: User "system:serviceaccount:jaeger:jaeger-operator" cannot list resource "horizontalpodautoscalers" in API group "autoscaling" in the namespace "jaeger"
E0325 19:07:24.670580 1 reflector.go:123] pkg/mod/k8s.io/[email protected]/tools/cache/reflector.go:96: Failed to list *v2beta2.HorizontalPodAutoscaler: horizontalpodautoscalers.autoscaling is forbidden: User "system:serviceaccount:jaeger:jaeger-operator" cannot list resource "horizontalpodautoscalers" in API group "autoscaling" in the namespace "jaeger"
E0325 19:07:25.672594 1 reflector.go:123] pkg/mod/k8s.io/[email protected]/tools/cache/reflector.go:96: Failed to list *v2beta2.HorizontalPodAutoscaler: horizontalpodautoscalers.autoscaling is forbidden: User "system:serviceaccount:jaeger:jaeger-operator" cannot list resource "horizontalpodautoscalers" in API group "autoscaling" in the namespace "jaeger"
E0325 19:07:26.674489 1 reflector.go:123] pkg/mod/k8s.io/[email protected]/tools/cache/reflector.go:96: Failed to list *v2beta2.HorizontalPodAutoscaler: horizontalpodautoscalers.autoscaling is forbidden: User "system:serviceaccount:jaeger:jaeger-operator" cannot list resource "horizontalpodautoscalers" in API group "autoscaling" in the namespace "jaeger"
E0325 19:07:27.676433 1 reflector.go:123] pkg/mod/k8s.io/[email protected]/tools/cache/reflector.go:96: Failed to list *v2beta2.HorizontalPodAutoscaler: horizontalpodautoscalers.autoscaling is forbidden: User "system:serviceaccount:jaeger:jaeger-operator" cannot list resource "horizontalpodautoscalers" in API group "autoscaling" in the namespace "jaeger"
E0325 19:07:28.678256 1 reflector.go:123] pkg/mod/k8s.io/[email protected]/tools/cache/reflector.go:96: Failed to list *v2beta2.HorizontalPodAutoscaler: horizontalpodautoscalers.autoscaling is forbidden: User "system:serviceaccount:jaeger:jaeger-operator" cannot list resource "horizontalpodautoscalers" in API group "autoscaling" in the namespace "jaeger"
E0325 19:07:29.680386 1 reflector.go:123] pkg/mod/k8s.io/[email protected]/tools/cache/reflector.go:96: Failed to list *v2beta2.HorizontalPodAutoscaler: horizontalpodautoscalers.autoscaling is forbidden: User "system:serviceaccount:jaeger:jaeger-operator" cannot list resource "horizontalpodautoscalers" in API group "autoscaling" in the namespace "jaeger"
E0325 19:07:30.682303 1 reflector.go:123] pkg/mod/k8s.io/[email protected]/tools/cache/reflector.go:96: Failed to list *v2beta2.HorizontalPodAutoscaler: horizontalpodautoscalers.autoscaling is forbidden: User "system:serviceaccount:jaeger:jaeger-operator" cannot list resource "horizontalpodautoscalers" in API group "autoscaling" in the namespace "jaeger"
E0325 19:07:31.684550 1 reflector.go:123] pkg/mod/k8s.io/[email protected]/tools/cache/reflector.go:96: Failed to list *v2beta2.HorizontalPodAutoscaler: horizontalpodautoscalers.autoscaling is forbidden: User "system:serviceaccount:jaeger:jaeger-operator" cannot list resource "horizontalpodautoscalers" in API group "autoscaling" in the namespace "jaeger"
E0325 19:07:32.686414 1 reflector.go:123] pkg/mod/k8s.io/[email protected]/tools/cache/reflector.go:96: Failed to list *v2beta2.HorizontalPodAutoscaler: horizontalpodautoscalers.autoscaling is forbidden: User "system:serviceaccount:jaeger:jaeger-operator" cannot list resource "horizontalpodautoscalers" in API group "autoscaling" in the namespace "jaeger"
E0325 19:07:33.688449 1 reflector.go:123] pkg/mod/k8s.io/[email protected]/tools/cache/reflector.go:96: Failed to list *v2beta2.HorizontalPodAutoscaler: horizontalpodautoscalers.autoscaling is forbidden: User "system:serviceaccount:jaeger:jaeger-operator" cannot list resource "horizontalpodautoscalers" in API group "autoscaling" in the namespace "jaeger"
E0325 19:07:34.690358 1 reflector.go:123] pkg/mod/k8s.io/[email protected]/tools/cache/reflector.go:96: Failed to list *v2beta2.HorizontalPodAutoscaler: horizontalpodautoscalers.autoscaling is forbidden: User "system:serviceaccount:jaeger:jaeger-operator" cannot list resource "horizontalpodautoscalers" in API group "autoscaling" in the namespace "jaeger"
E0325 19:07:35.692292 1 reflector.go:123] pkg/mod/k8s.io/[email protected]/tools/cache/reflector.go:96: Failed to list *v2beta2.HorizontalPodAutoscaler: horizontalpodautoscalers.autoscaling is forbidden: User "system:serviceaccount:jaeger:jaeger-operator" cannot list resource "horizontalpodautoscalers" in API group "autoscaling" in the namespace "jaeger"
E0325 19:07:36.694149 1 reflector.go:123] pkg/mod/k8s.io/[email protected]/tools/cache/reflector.go:96: Failed to list *v2beta2.HorizontalPodAutoscaler: horizontalpodautoscalers.autoscaling is forbidden: User "system:serviceaccount:jaeger:jaeger-operator" cannot list resource "horizontalpodautoscalers" in API group "autoscaling" in the namespace "jaeger"
E0325 19:07:37.700222 1 reflector.go:123] pkg/mod/k8s.io/[email protected]/tools/cache/reflector.go:96: Failed to list *v2beta2.HorizontalPodAutoscaler: horizontalpodautoscalers.autoscaling is forbidden: User "system:serviceaccount:jaeger:jaeger-operator" cannot list resource "horizontalpodautoscalers" in API group "autoscaling" in the namespace "jaeger"
E0325 19:07:38.702125 1 reflector.go:123] pkg/mod/k8s.io/[email protected]/tools/cache/reflector.go:96: Failed to list *v2beta2.HorizontalPodAutoscaler: horizontalpodautoscalers.autoscaling is forbidden: User "system:serviceaccount:jaeger:jaeger-operator" cannot list resource "horizontalpodautoscalers" in API group "autoscaling" in the namespace "jaeger"
E0325 19:07:39.703855 1 reflector.go:123] pkg/mod/k8s.io/[email protected]/tools/cache/reflector.go:96: Failed to list *v2beta2.HorizontalPodAutoscaler: horizontalpodautoscalers.autoscaling is forbidden: User "system:serviceaccount:jaeger:jaeger-operator" cannot list resource "horizontalpodautoscalers" in API group "autoscaling" in the namespace "jaeger"
E0325 19:07:40.706536 1 reflector.go:123] pkg/mod/k8s.io/[email protected]/tools/cache/reflector.go:96: Failed to list *v2beta2.HorizontalPodAutoscaler: horizontalpodautoscalers.autoscaling is forbidden: User "system:serviceaccount:jaeger:jaeger-operator" cannot list resource "horizontalpodautoscalers" in API group "autoscaling" in the namespace "jaeger"
E0325 19:07:41.708612 1 reflector.go:123] pkg/mod/k8s.io/[email protected]/tools/cache/reflector.go:96: Failed to list *v2beta2.HorizontalPodAutoscaler: horizontalpodautoscalers.autoscaling is forbidden: User "system:serviceaccount:jaeger:jaeger-operator" cannot list resource "horizontalpodautoscalers" in API group "autoscaling" in the namespace "jaeger"
E0325 19:07:42.710402 1 reflector.go:123] pkg/mod/k8s.io/[email protected]/tools/cache/reflector.go:96: Failed to list *v2beta2.HorizontalPodAutoscaler: horizontalpodautoscalers.autoscaling is forbidden: User "system:serviceaccount:jaeger:jaeger-operator" cannot list resource "horizontalpodautoscalers" in API group "autoscaling" in the namespace "jaeger"
E0325 19:07:43.712252 1 reflector.go:123] pkg/mod/k8s.io/[email protected]/tools/cache/reflector.go:96: Failed to list *v2beta2.HorizontalPodAutoscaler: horizontalpodautoscalers.autoscaling is forbidden: User "system:serviceaccount:jaeger:jaeger-operator" cannot list resource "horizontalpodautoscalers" in API group "autoscaling" in the namespace "jaeger"
E0325 19:07:44.714268 1 reflector.go:123] pkg/mod/k8s.io/[email protected]/tools/cache/reflector.go:96: Failed to list *v2beta2.HorizontalPodAutoscaler: horizontalpodautoscalers.autoscaling is forbidden: User "system:serviceaccount:jaeger:jaeger-operator" cannot list resource "horizontalpodautoscalers" in API group "autoscaling" in the namespace "jaeger"
E0325 19:07:45.716290 1 reflector.go:123] pkg/mod/k8s.io/[email protected]/tools/cache/reflector.go:96: Failed to list *v2beta2.HorizontalPodAutoscaler: horizontalpodautoscalers.autoscaling is forbidden: User "system:serviceaccount:jaeger:jaeger-operator" cannot list resource "horizontalpodautoscalers" in API group "autoscaling" in the namespace "jaeger"
E0325 19:07:46.718484 1 reflector.go:123] pkg/mod/k8s.io/[email protected]/tools/cache/reflector.go:96: Failed to list *v2beta2.HorizontalPodAutoscaler: horizontalpodautoscalers.autoscaling is forbidden: User "system:serviceaccount:jaeger:jaeger-operator" cannot list resource "horizontalpodautoscalers" in API group "autoscaling" in the namespace "jaeger"
So chart rbac is missing horizontalpodautoscalers permissions in RBAC template
edit: create issue template as per @yurishkuro's comment below
Use an audit tool such as Polaris and eliminate as many warnings as possible by default for jaeger chart.
The chart could benefit from some automatic tests:
Any other suggestions?
cc @scottrigby does the above seam feasible in CI? deploy a chart, delete it and then re deploy it with different values?
Background ?
(On Jaeger chart)
Both es-index-cleaner and spark-cronjob do not allow concurrencyPolicy and few other cronJob K8s resources properties to be set from the values.yaml file.
Example: https://github.com/jaegertracing/helm-charts/blob/master/charts/jaeger/templates/es-index-cleaner-cronjob.yaml#L14
This is explicitly set to Forbid which is fine, but in case of spark-cronjob the property is not set and is Allow by default.
In some scenarios, someone might want to run the spark job more frequently but they would not want multiple jobs to run concurrently (which can cause issues with load on the Elastic-search cluster).
What ?
We should make these properties configurable through a helm chart values file and see if there are other properties that make sense to be made configurable as well.
We should find a way to have the chart deploy an agent-sidecar-injector of sorts.
Please skip to #15 (comment)
Original issue has taken a different road.
We should also add ingester deployment
As per jaegertracing/jaeger#2092
Hello,
We have quite a few PRs unable to be merged because CI keeps failing.
Is there a way to skip CI?
In particular for this: #62
I think actions/checkout#23 has been an issue for many of these blocked PRs.
Bump chart api version to v2, move requirements.yaml into chart.yaml and any other necessary adjustments
The 0.19.3 release includes changes to the template for setting the elastic search url if using an existing elastic search and not provisioning. It works in 0.18.3 and 0.19.2.
Reproduce:
Set a values file with:
provisionDataStore:
cassandra: false
elasticsearch: false
storage:
type: elasticsearch
elasticsearch:
scheme: https
host: somehost
user: someuser
port: 9000
existingSecret: jaeger-secrets
usePassword: true
Run helm template jaeger -f values.yaml
and you'll see that the ES_SERVER_URLS
will not have a value set.
Should be changed to match changes in #31
As helm charts are hosted on github, the repository is not available when github is down.
Are there any plan/reflection to move the repository in a safer place ?
Thanks
The jaeger-operator-metrics
service seems to be created by the Helm Chart, but it's actually created by the jaeger-operator during its bootstrap. The service from the chart doesn't seem to be creating a properly configured service, as seen in a recent thread in the Jaeger mailing list.
This is a breaking change and ideally should not be left unattended.
Should we move forward with this change of default value or not?
Should we allow the keyspace override but leave jaeger_v1_dc1
as default?
Should we keep as is and just add a note in README regarding upgrading chart?
Related PR in helm chart:
#31
Related PRs in application:
jaegertracing/jaeger#2020
jaegertracing/jaeger-operator#837
Based on #20, this issue is a heads-up that the CRD file has been changed in the Operator's master and will be released as part of 1.17.
When i bump chart version from 2.14.2 to 2.15.0 jaeger-operator pod start spamming with
time="2020-06-01T11:28:44Z" level=error msg="failed to apply the changes" error="ingresses.networking.k8s.io is forbidden: User \"system:serviceaccount:jaeger:jaeger-jaeger-operator\" cannot list resource \"ingresses\" in API group \"networking.k8s.io\" in the namespace \"jaeger\"" execution="2020-06-01 11:28:44.059506841 +0000 UTC" instance=jaeger-jaeger-operator-jaeger namespace=jaeger
NAMESPACE NAME STATUS VERSION
jaeger jaeger-jaeger-operator-jaeger Failed
That is something with role permissions?
of the three cassandra nodes one is crashing continuously:
INFO [main] 2020-05-19 15:06:04,423 StorageService.java:1478 - JOINING: Starting to bootstrap...
Exception (java.lang.RuntimeException) encountered during startup: A node required to move the data consistently is down (/10.4.3.44). If you wish to move the data from a potentially inconsistent replica, restart the node with -Dcassandra.consistent.rangemovement=false
java.lang.RuntimeException: A node required to move the data consistently is down (/10.4.3.44). If you wish to move the data from a potentially inconsistent replica, restart the node with -Dcassandra.consistent.rangemovement=false
at org.apache.cassandra.dht.RangeStreamer.getAllRangesWithStrictSourcesFor(RangeStreamer.java:294)
at org.apache.cassandra.dht.RangeStreamer.addRanges(RangeStreamer.java:177)
at org.apache.cassandra.dht.BootStrapper.bootstrap(BootStrapper.java:87)
at org.apache.cassandra.service.StorageService.bootstrap(StorageService.java:1530)
at org.apache.cassandra.service.StorageService.joinTokenRing(StorageService.java:1024)
at org.apache.cassandra.service.StorageService.initServer(StorageService.java:718)
at org.apache.cassandra.service.StorageService.initServer(StorageService.java:652)
at org.apache.cassandra.service.CassandraDaemon.setup(CassandraDaemon.java:397)
at org.apache.cassandra.service.CassandraDaemon.activate(CassandraDaemon.java:630)
at org.apache.cassandra.service.CassandraDaemon.main(CassandraDaemon.java:757)
ERROR [main] 2020-05-19 15:06:04,475 CassandraDaemon.java:774 - Exception encountered during startup
java.lang.RuntimeException: A node required to move the data consistently is down (/10.4.3.44). If you wish to move the data from a potentially inconsistent replica, restart the node with -Dcassandra.consistent.rangemovement=false
at org.apache.cassandra.dht.RangeStreamer.getAllRangesWithStrictSourcesFor(RangeStreamer.java:294) ~[apache-cassandra-3.11.6.jar:3.11.6]
at org.apache.cassandra.dht.RangeStreamer.addRanges(RangeStreamer.java:177) ~[apache-cassandra-3.11.6.jar:3.11.6]
at org.apache.cassandra.dht.BootStrapper.bootstrap(BootStrapper.java:87) ~[apache-cassandra-3.11.6.jar:3.11.6]
at org.apache.cassandra.service.StorageService.bootstrap(StorageService.java:1530) ~[apache-cassandra-3.11.6.jar:3.11.6]
at org.apache.cassandra.service.StorageService.joinTokenRing(StorageService.java:1024) ~[apache-cassandra-3.11.6.jar:3.11.6]
at org.apache.cassandra.service.StorageService.initServer(StorageService.java:718) ~[apache-cassandra-3.11.6.jar:3.11.6]
at org.apache.cassandra.service.StorageService.initServer(StorageService.java:652) ~[apache-cassandra-3.11.6.jar:3.11.6]
at org.apache.cassandra.service.CassandraDaemon.setup(CassandraDaemon.java:397) [apache-cassandra-3.11.6.jar:3.11.6]
at org.apache.cassandra.service.CassandraDaemon.activate(CassandraDaemon.java:630) [apache-cassandra-3.11.6.jar:3.11.6]
at org.apache.cassandra.service.CassandraDaemon.main(CassandraDaemon.java:757) [apache-cassandra-3.11.6.jar:3.11.6]
INFO [StorageServiceShutdownHook] 2020-05-19 15:06:04,487 HintsService.java:209 - Paused hints dispatch
WARN [StorageServiceShutdownHook] 2020-05-19 15:06:04,490 Gossiper.java:1655 - No local state, state is in silent shutdown, or node hasn't joined, not announcing shutdown
INFO [StorageServiceShutdownHook] 2020-05-19 15:06:04,491 MessagingService.java:985 - Waiting for messaging service to quiesce
INFO [ACCEPT-/10.4.3.79] 2020-05-19 15:06:04,491 MessagingService.java:1346 - MessagingService has terminated the accept() thread
INFO [StorageServiceShutdownHook] 2020-05-19 15:06:04,987 HintsService.java:209 - Paused hints dispatch
We manage all our releases through helm. For us it would make sense to have a very simple Helm-Chart which allows to create Jeager CRDs which are managed by the jaeger operator. Similar to the Implementation for the jaeger-operator Helm-Chart (https://github.com/jaegertracing/helm-charts/blob/master/charts/jaeger-operator/templates/jaeger.yaml). We have a multi-tenancy-scenario and want to be able to deploy multiple Jaeger instances on different tenants on the same cluster, which are all managed by one Jaeger-Operator instance per cluster. Therefor i am asking if it would make sense to have a wrapper chart to deploy a Jaeger Instance without the operator. Or are there other approaches used to fullfill such a multi-tenancy-scenario?
Can we set up a jaegertracing bot and use its GH token instead of the @scottrigby token? :)
besides the fact, if that somehow get leaked the scott's token will be used for other things and maybe have access to his repos.
The jaeger-operator is missing permissions for autoscaling in 2.14.0 version of the chart.
Error log example:
E0309 17:08:23.724748 1 reflector.go:123] pkg/mod/k8s.io/[email protected]/tools/cache/reflector.go:96: Failed to list *v2beta2.HorizontalPodAutoscaler: horizontalpodautoscalers.autoscaling is forbidden: User "system:serviceaccount:monitoring:monitoring-jaeger-operator" cannot list resource "horizontalpodautoscalers" in API group "autoscaling" in the namespace "monitoring"
Reference to the apiGroup in the jaeger-operator project: here
We should improve env var flexibility.
env: {}
key value pairs to the more flexible env: []
as-is yaml
cc @pavelnikolov @cgroschupp @mehta-ankit @Jasstkn @arpitjindal97
you can reproduce using the following values.yaml
file:
storage:
type: elasticsearch
elasticsearch:
env:
ES_TLS_SKIP_HOST_VERIFY: true
and run
helm template jaegertracing/jaeger --version 0.27.2 -f values.yaml
What's the difference between the ChartImage and App version?Why the version is not same?
For, example:
# helm list jaeger
NAME REVISION UPDATED STATUS CHART APP VERSION NAMESPACE
jaeger-operator 2 Sat May 30 08:32:57 2020 DEPLOYED jaeger-operator-2.9.0 1.13.1 istio-system
The CHART is jaeger-operator-2.9.0, and APP VERSION is 1.13.1γ
Now, I want to get the VERSION 1.13.1 CAHRT. How can I get it?
the tag make me confused.
# git tag
...
jaeger-0.27.1
jaeger-0.27.2
jaeger-0.27.3
jaeger-0.28.0
jaeger-0.29.0
jaeger-operator-2.12.1
jaeger-operator-2.12.2
jaeger-operator-2.12.3
jaeger-operator-2.12.4
jaeger-operator-2.13.0
jaeger-operator-2.13.1
jaeger-operator-2.14.0
jaeger-operator-2.14.1
jaeger-operator-2.14.2
Hey!
I wonder why there is no ServiceMonitor for jaeger components? Is there any issues with it? If it's not, I'll happy to contribute this improvement. Let me know, what do you think about it =)
I see list of ports and default path in docs: https://www.jaegertracing.io/docs/1.17/monitoring/
Hi,
Not sure if this is the correct place to file this issue but here it goes.
Trying the operator chart with a minimal values file. I enabled jaeger instance creation with the operator installation without providing any specs.
Chart Version: 2.13.1
Operator Version: 1.16.0
Helm version: v2.16.3
crd:
install: true
jaeger:
# Specifies whether Jaeger instance should be created
create: true
spec: {}
rbac:
# Specifies whether RBAC resources should be created
create: true
pspEnabled: false
clusterRole: true
serviceAccount:
# Specifies whether a ServiceAccount should be created
create: true
# The name of the ServiceAccount to use.
# If not set and create is true, a name is generated using the fullname template
name:
Leads to the following errors.
time="2020-02-27T15:50:45Z" level=info msg=Versions arch=amd64 identity=jaegertracing.jaegertracing-jaeger-operator jaeger=1.16.0 jaeger-operator=v1.16.0 operator-sdk=v0.12.0 β
β os=linux version=go1.13.3 β
β time="2020-02-27T15:50:47Z" level=info msg="Auto-detected the platform" platform=kubernetes β
β time="2020-02-27T15:50:47Z" level=info msg="Automatically adjusted the 'es-provision' flag" es-provision=no β
β time="2020-02-27T15:50:47Z" level=info msg="Automatically adjusted the 'kafka-provision' flag" kafka-provision=no β
β time="2020-02-27T15:50:47Z" level=info msg="The service account running this operator does not have the role 'system:auth-delegator', consider granting it for additional capa β
β bilities" β
β time="2020-02-27T15:50:50Z" level=info msg="Storage type not provided. Falling back to 'memory'" instance=jaegertracing-jaeger-operator-jaeger namespace=jaegertracing β
β time="2020-02-27T15:50:51Z" level=error msg="failed to apply the changes" error="Deployment.apps \"jaegertracing-jaeger-operator-jaeger\" is invalid: [spec.template.spec.volu β
β mes[0].name: Invalid value: \"jaegertracing-jaeger-operator-jaeger-sampling-configuration-volume\": must be no more than 63 characters, spec.template.spec.containers[0].volum β
β eMounts[0].name: Not found: \"jaegertracing-jaeger-operator-jaeger-sampling-configuration-volume\"]" execution="2020-02-27 15:50:50.576488163 +0000 UTC" instance=jaegertracin β
β g-jaeger-operator-jaeger namespace=jaegertracing```
I was wondering if there has been any discussion regarding adding a K8s job to the Helm chart for Jeager to clean up elasticsearch indices (for example: delete indices that are n days old, since each ES index is timestamped by day).
The following image is already published.
https://hub.docker.com/r/jaegertracing/jaeger-es-index-cleaner
Let's look at that in a separate PR. Here's an example that's kind of nice and also easy https://charts.fluxcd.io/
Originally posted by @scottrigby in #2
Hi,
To use Jaeger via reverse proxy there is ENV called "QUERY_BASE_PATH".
How to inject it to the Jaeger pod via helm chart of Jaeger operator?
I tried using this command:
helm install -n jaeger jaegertracing/jaeger
And I got:
Error: validation failed: unable to recognize "": no matches for kind "ServiceMonitor" in version "monitoring.coreos.com/v1"
I think this is related to #97 as I can install version 0.27.0 of this chart fine.
I tried using the chart version 0.30.1, and it throws an error:
Error: YAML parse error on /charts/jaeger/templates/spark-cronjob.yaml: error converting YAML to JSON: yaml: line 44: could not find expected ':'
helm.go:75: [debug] error converting YAML to JSON: yaml: line 44: could not find expected ':'
I think its related to: #119
cc @naseemkullah
The optional elasticsearch dependency chart should be https://github.com/elastic/helm-charts/tree/master/elasticsearch
I tried to set cmdlineParams
in the collector like this:
collector:
cmdlineParams:
es.num-shards: 2
es.num-replicas: 0
Now the collector refuses to start with the error: Error: invalid argument "--es.num-shards=2" for "--es.num-replicas" flag: parse error
It looks like arguments are expected to be separated by a space rather than a =
.
Is the code below supposed to work with --es.num-shards
and --es.num-replicas
?
helm-charts/charts/jaeger/templates/collector-deploy.yaml
Lines 46 to 53 in f8e9b69
I am trying to install the whole jaeger stack on a specific node pool but cassandra pods are created outside of this pool.
Here is my values.yaml:
collector:
nodeSelector: &selector
pool: jaeger
query:
nodeSelector: *selector
cassandra:
nodeSelector: *selector
query
and collector
are correctly created on the pool
##jaeger agent helm related configurations
jaegeragent:
agent
service:
spec:
selector:
app.kubernetes.io/name: jaegeragent
app.kubernetes.io/component: agent
topologyKeys:
- "kubernetes.io/hostname"
What you expected to happen:
Pods only send data to the local daemonset
kubectl get endpointslice
No resources found
--feature-gates="ServiceTopology=true,EndpointSlice=true" is already enabeled.
helm-charts/charts/jaeger/values.yaml
Lines 18 to 44 in 2f60c58
It would be great to be able to provide any config options by a variety of means the user can choose from (any or a mix of the following: env vars, env vars from secrets, env vars from configmaps, comman line options).
This has been prompted by consistent PRs such as #73 and #65 to bubble up config options.
Can i use jaegertracing/jaeger
helm chart with badger and pvc+pv like jaegertracing/jaeger-operator
can create?
Hi π !
I've been trying to disable sniffing for Elasticsearch, but no luck.
Maybe I'm doing something wrong ?
I'm using
collector:
cmdlineParams:
es.sniffer: "false"
Still I'm getting the failed to create primary Elasticsearch client with health check timeout - no Elasticsearch node available
From what I can tell this is related with using https://github.com/olivere/elastic . And because I'm using an AWS Elasticsearch theres an issue when it sniffs the available nodes.
Any help would be much appreciated ! :)
Error: error creating GitHub release: POST https://api.github.com/repos/jaegertracing/helm-charts/releases: 404 Not Found []
We can begin by reverting the token used to see if that caused the issue.
Just a brief few lines describing how to achieve the ingester architecture and what happens behind the scenes in the chart when the component is enabled.
cc @arpitjindal97
A declarative, efficient, and flexible JavaScript library for building user interfaces.
π Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
An Open Source Machine Learning Framework for Everyone
The Web framework for perfectionists with deadlines.
A PHP framework for web artisans
Bring data to life with SVG, Canvas and HTML. πππ
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
Some thing interesting about web. New door for the world.
A server is a program made to process requests and deliver data to clients.
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
Some thing interesting about visualization, use data art
Some thing interesting about game, make everyone happy.
We are working to build community through open source technology. NB: members must have two-factor auth.
Open source projects and samples from Microsoft.
Google β€οΈ Open Source for everyone.
Alibaba Open Source for everyone
Data-Driven Documents codes.
China tencent open source team.