This POC uses selectors rather than annotations to inject instrumentation.
This replicates secrets from some base (not determined yet) namespace to the pod namespace. [^1]
This merges the main branch and feat/poc features, along with some additional changes:
Sorting some declarations
Support for selector instrumentation per language, where each could use a different secret or language combo. [^2] [^3] [^4]
Using a custom secret name is broken
Type of change
[x] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[x] New feature / enhancement (non-breaking change which adds functionality)
[ ] Security fix
[ ] Bug fix (non-breaking change which fixes an issue)
Checklist:
[ ] Documentation has been updated
[ ] This change requires changes in testing:
[ ] unit tests
[ ] E2E tests
[^1]: There's no mechanism to update/patch/delete secrets in the case of a collision or rotating secrets
[^2]: This won't work if the pod has multiple containers with different languages
[^3]: Only the first container can be selected, except with Go, due to it having a specific annotation for which container to target
[^4]: If we could target multiple containers for instrumentation in a pod with different languages, We'd also need to fix volumes
Description
This POC uses selectors rather than annotations to inject instrumentation. This replicates secrets from some base (not determined yet) namespace to the pod namespace. [^1] This merges the
mainbranch andfeat/pocfeatures, along with some additional changes:Type of change
Checklist:
[^1]: There's no mechanism to update/patch/delete secrets in the case of a collision or rotating secrets [^2]: This won't work if the pod has multiple containers with different languages [^3]: Only the first container can be selected, except with Go, due to it having a specific annotation for which container to target [^4]: If we could target multiple containers for instrumentation in a pod with different languages, We'd also need to fix volumes