Is your feature request related to a problem? Please describe.
Companies operating a self-hosted Temporal server cluster (such as Datadog) often require more advanced configuration of the client used to connect to the server than what is currently supported by the TemporalConnection CRD. In addition to connection-level customization, there may be further setup or configuration needed to successfully run and integrate the controller within their environment.
Describe the solution you'd like
To address this, the proposal is to expose a public interface that allows creating the controller with custom options. This would make it easier to configure connection details beyond what the CRD supports. It could also optionally allow providing a pre-configured Temporal client, giving full control over how the controller connects to the server.
However, the change should not impact the current behavior of the controller in any way, such that for Temporal Cloud users it works directly out-of-the-box.
Additional context
Is your feature request related to a problem? Please describe.
Companies operating a self-hosted Temporal server cluster (such as Datadog) often require more advanced configuration of the client used to connect to the server than what is currently supported by the TemporalConnection CRD. In addition to connection-level customization, there may be further setup or configuration needed to successfully run and integrate the controller within their environment.
Describe the solution you'd like
To address this, the proposal is to expose a public interface that allows creating the controller with custom options. This would make it easier to configure connection details beyond what the CRD supports. It could also optionally allow providing a pre-configured Temporal client, giving full control over how the controller connects to the server.
However, the change should not impact the current behavior of the controller in any way, such that for Temporal Cloud users it works directly out-of-the-box.
Additional context