Mike Dame
Mike Dame
Part of setting up for exposing the Probe API -- the main goal of this PR is to shift usage of the internal `process` package from the base Probe implementation...
Similar to https://github.com/open-telemetry/opentelemetry-go-instrumentation/issues/435, our e2es set up a kind cluster which would need a docker registry secret with credentials, and for the secret to be patched into the workflow pods
Ref #1105 To support custom (modular) Probes, we want a Probe API that is: * **Generic** - It should be rich enough to support our current use cases, but not...
## Type of question Best practices ## Question #### What did you do? Hi, we have several operands which we define in our manager's kustomization file like so: https://github.com/odigos-io/odigos/blob/5b5b1c02b1184936ab223265a6087071be258da3/operator/config/manager/kustomization.yaml#L6-L11 These...
This fixes 2 issues with the Instrumentor causing unnecessary CPU usage. The Instrumentor is currently consuming measurable CPU even at idle without active instrumentation requests happening. 1. Hotloop on `DistroParams`...
Cherry pick of https://github.com/odigos-io/odigos/pull/3956
Migrating to our new direct registry requires some changes to continue supporting OpenShift certification components from our docker repo. There is more detail in the linked image, but essentially this...
This adds an enpoint to the ui pod that collects a tar.gz of relevant Odigos components. It can capture: * Odigos component YAML (deployment+pod) and logs * Odigos CRDs *...
Icon added to ui-kit in https://github.com/odigos-io/ui-kit/pull/551