OpAMP Bridge resource in the operator

[jaronoff97]

Per the discussion in the Operator SIG, the plan is for the Operator to take on creating a container that is able to remotely configure OpenTelemetryCollector CRDs via OpAMP. The design documents for this proposal can be read here.

I'm planning on taking on this work in the coming weeks/months. I plan to create a new directory in the operator repo's cmd folder with a remoteconfiguration service. This container will be built in the same way as the target allocator. The service will be marked as alpha in its README.md. There's probably a few more organizational tasks related to this that will need to be done.

Todo (part 1)

• Create the new directory for the remoteconfiguration service
• Create a valid opamp agent in the remote configuration
• Report health and status via OpAMP
• Connect the opamp agent to a valid operator opamp server
• Allow the remoteconfiguration service to create OpenTelemetryCollector CRDs
• Create collector CRDs from received messages from opamp
• Add tests and documentation

Todo (part 2)

• Add CI/CD for OpAMP Bridge container #1369
• Create OpAMP Bridge CRD in the operator #1368

Todo (part 3)

• Add ability for OpAMP Bridge to act as an opamp read-only server for a collector's opamp extension #1370
• Plumb a collector CRD's opamp-extension to point to the bridge when the bridge is enabled #1932
• Modify bridge to report on status of any annotated collectors #2131
• Allow bridge to modify only owned collectors #2132
• Allow bridge to report health of collectors in Kubernetes #2282

[jaronoff97]

I'm planning on starting on the part 1 next week

[jaronoff97]

issues will be made as needed, i just added three more that can mostly be done in parallel if anyone else wants to hop in :)

[jaronoff97]

All these are completed and the bridge is released! It's already being used in production ;)