Add Pipeline controller and Kafka JDBC driver #73
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
pipeline-controller
.Details
The new
pipeline-controller
is significantly simpler than the existingsubscription-controller
, since it does not need to plan and deploy everything. So far, the pipeline controller is responsible for checking and reporting status of the pipeline. We need both implementations for now, but we plan to get rid of the subscription controller eventually.The new catalog API is based on JDBC, which works well for most data sources. I've included a simple JDBC driver for Kafka, with just the minimal functionality to get integration tests working.
Our integration tests are now just unit tests tagged with
integration
, rather than full K8s pods. This should reduce our build complexity a bit, but we still need to wait for Kafka to come up before most integration tests will pass.I have added a couple integration tests using quidem. I've included a text fixture for running quidem scripts.
Testing
We can create a Kafka changestream using our "demo" db:
The resulting pipeline can be seen reaching
Ready.
state:The physical Kafka topic is created by the Strimzi topic operator: