TRACING-4207: add support for Instrumentation CR

[iblancasa]

No description provided.

[coveralls]

Pull Request Test Coverage Report for Build 10810415250

Warning: This coverage report may be inaccurate.

This pull request's base commit is no longer the HEAD commit of its target branch. This means it includes changes from outside the original pull request, including, potentially, unrelated coverage changes.

• For more information on this, see Tracking coverage changes with pull request builds.
• To avoid this issue with future PRs, see these Recommended CI Configurations.
• For a quick fix, rebase this PR at GitHub. Your next report should be accurate.

Details

• 0 of 0 changed or added relevant lines in 0 files are covered.
• No unchanged relevant lines lost coverage.
• Overall coverage remained the same at 56.164%

---

Totals
Change from base Build 10770330531:	0.0%
Covered Lines:	164
Relevant Lines:	292

---

💛 - Coveralls

[JoaoBraveCoding]

Also, can you share some steps on how to test this on a cluster? I've never played with the Instrumentation resource. Adding the required resources to hack and providing the steps it is also fine.

[iblancasa]

Also, can you share some steps on how to test this on a cluster? I've never played with the Instrumentation resource. Adding the required resources to hack and providing the steps it is also fine.

I added one Instrumentation object to be used as stanza and one workload (to deploy in the spoke cluster) to automatically instrument it.

I have to retest everything but having some issues with my installation.

[JoaoBraveCoding]

I have to retest everything but having some issues with my installation.

No problem, do let me know when I can also give it a spin on my side 👍

BTW: you named your Instrumentation python but then in the CMA you are looking for one called instance that might be where things are going wrong.

[JoaoBraveCoding]

/lgtm

Tested and indeed pods on the spoke are getting instrumentation injected.