Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Support for Kafka native protocol #778

Open
mmolimar opened this issue Oct 27, 2016 · 2 comments
Open

Support for Kafka native protocol #778

mmolimar opened this issue Oct 27, 2016 · 2 comments

Comments

@mmolimar
Copy link

It'd be great if linkerd could have support for Kafka native protocol. Do you have in mind to include this in the roadmap?
@olix0r
Copy link
Member

olix0r commented Oct 31, 2016

Welcome to the project, @mmolimar!

I'm not all that familiar with Kafka's API, but from a glance at the docs it seems like it may be possible (though further investigation is needed to figure out exactly how this integrates).

Can you share any of linkerd's features that you're especially interested in for kafka?

@mmolimar
Copy link
Author

Thanks @olix0r
One use case I found was using Kafka in DC/OS. Kafka brokers are deployed on private agents inside a Mesos cluster and they are not accessible from the "outside world" of DC/OS. So, the idea would be to use Linkerd as a proxy in order to produce/consume messages in Kafka and take advantage of all features that Linkerd provides.

Tim-Brooks pushed a commit to Tim-Brooks/linkerd that referenced this issue Dec 20, 2018
@olix0r
Introduce the TapByResource API (linkerd#778)
06dd8d9 
This changes the public api to have a new rpc type, `TapByResource`.
This api supersedes the Tap api. `TapByResource` is richer, more closely 
reflecting the proxy's capabilities.

The proxy's Tap api is extended to select over destination labels,
corresponding with those returned by the Destination api.

Now both `Tap` and `TapByResource`'s responses may include destination
labels.

This change avoids breaking backwards compatibility by:

* introducing the new `TapByResource` rpc type, opting not to change Tap
* extending the proxy's Match type with a new, optional, `destination_label` field.
* `TapEvent` is extended with a new, optional, `destination_meta`.
Tim-Brooks pushed a commit to Tim-Brooks/linkerd that referenced this issue Dec 20, 2018
@siggy
Introduce tapByResource cli command (linkerd#802)
293e00b 
The existing `tap` command is being deprecated.

Introduce a `tapByResource` cli command. It supports tapping a Kubernetes
resource or collection of resources, optionally filtered by outbound resources.
This command will eventually replace `tap`.

Part of linkerd#778

Signed-off-by: Andrew Seigner <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@olix0r @mmolimar