First user guides (local setup with kind+Jaeger) #49
Conversation
errordeveloper
force-pushed
the
user-guides
branch
7 times, most recently
from
21ed0b4
to
cbaadd0
Compare
errordeveloper
force-pushed
the
user-guides
branch
5 times, most recently
from
b9db6cf
to
c1382f0
Compare
errordeveloper
changed the title
| ) | ||
| ``` | ||
|
|
||
| Deploy Jaeger operator: |
There was a problem hiding this comment.
is Jaeger a dependency for OpenTelemetry?
There was a problem hiding this comment.
Not generally. It's just part of the OpenTelemetry world, and it can be used sort of independently. You would probably use OTel SDK with Jaeger anyway, but the OTel collector is no essential for using Jaeger. Does this make sense?
There was a problem hiding this comment.
If you read all of the configs in both of the OpenTelemetryCollector CRs that are defined here, you should be able to get an idea how the pieces connect together. I would be happy to get on a call and draw some kind of an arch diagram together also!
GUIDE_KIND.md
Outdated
| namespace: kube-system | ||
| spec: | ||
| mode: daemonset | ||
| image: docker.io/errordeveloper/otelcol:cb59912b36f1b5aeed4bfb49c132e9f3dcda8992-dev@sha256:d89f31b721bf184620f225b983136002b0f55b30231fa15e7d98277f2f2713ab |
There was a problem hiding this comment.
will we be moving this over to an Isovalent or a Cilium container repo?
There was a problem hiding this comment.
Yeah, it will be either quay or GitHub. This one is just a public snapshot, the repo is still private...
There was a problem hiding this comment.
The repo is public now and the image is under ghcr.io/cilium/
errordeveloper
force-pushed
the
user-guides
branch
2 times, most recently
from
35b0f73
to
82f0783
Compare
errordeveloper
force-pushed
the
user-guides
branch
from
82f0783
to
3e296e4
Compare
Fixes #3