Python specific quirks for kubernetes operator

[xrmx]

Desired feature or idea:

I would like to document the quirks one should take into account regarding architecture, C libraries and Python version incompatibilities when using the kubernetes operator.

Additional context:

I'm unsure if I should put it in the operator page of python docs in the zero-code section or in the kubernetes section with all the other languages.

[cartermp]

@xrmx can you share a few of those quirks here and how they're specific to when you're using the operator compared to when you plop the agent down on a machine yourself?

[xrmx]

@xrmx can you share a few of those quirks here and how they're specific to when you're using the operator compared to when you plop the agent down on a machine yourself?

The problem is with binary wheels, the image you use to build the agent must match (architecture, python version and libc flavour) with what you use on the application container. Or instrumentations with dependencies binding compiled code will not being able to load it and they will fail.
In the operator this is framed only as a problem with the grpc exporter but it's also a problem with the instrumentors. Bonus points is that the python distro will fail the initialization at the first instrumentor that fails to load.

[svrnm]

I'm unsure if I should put it in the operator page of python docs in the zero-code section or in the kubernetes section with all the other languages.

Maybe have the content itself in the zero-code section, since it seems to be generic and then link back to it from the operator pages?

[xrmx]

I'm unsure if I should put it in the operator page of python docs in the zero-code section or in the kubernetes section with all the other languages.

Maybe have the content itself in the zero-code section, since it seems to be generic and then link back to it from the operator pages?

I'll give it a try, thanks