Terraform deployment in self hosted Connect environment

[gautam-goudar]

I wanted to ask - if I run the kafka and connect (cp-kafka-connect) locally and in the Terraform code point to my local machine (is this even possible) details, will I be able to deploy the connector in my local machine (or a K8s cluster) using Terraform?

Is the provider "confluent" smart enough to know that this needs to be deployed on the local machine? I won't be having the
kafka_id and kafka_rest_endpoint details for my local cluster.

Much appreciated.

[linouk23]

👋 @gautam-goudar thanks for creating this issue!

The short answer is I don't think it's currently supported 😕

Would you say your request is kinda similar to #145?

[gautam-goudar]

It's similar to an extent - but not completely since I don't plan to install the complete Confluent Platform.

In my case, I don't plan to install the Confluent Platform, but just a few components of the platform, like the connector only as an example. Have the connector image run in K8s cluster and have the ability to deploy the self managed connectors using Terraform into the K8s cluster. The connectors can be talking to topics hosted in Confluent Cloud itself.

[linouk23]

Sounds good, let's keep it open then as a separate issue 👍

[bijenkins]

We are needing this same functionality. The ability to create Self-Hosted as described in this article:

https://docs.confluent.io/platform/current/connect/supported.html

But, through Terraform currently, we are having to build out our a idempotent rest service around this. It also complicates being able to create associated topics since they are managed, for us, via Terraform.