Skip to content
This repository has been archived by the owner on Jan 24, 2024. It is now read-only.

Add inner topic protection #451

Conversation

hangc0276
Copy link
Collaborator

Motivation

For inner topic, such as, __consumer_offsets, __transaction_stats, and system topic, such as, __change_event, they are expose to all users and can produce / consumer message to / from those topic, which will cause the cluster crash.

Changes

  1. add produce protection for inner topic on KOP side.

TODO

  1. for consume protection, it's in testing.

@BewareMyPower
Copy link
Collaborator

Just a doubt about your TODO: do we need to protect consuming? If I didn't remember wrong, Kafka allows consumers to read __consumer_offsets and some admin tools are implemented by this way.

@hangc0276
Copy link
Collaborator Author

Just a doubt about your TODO: do we need to protect consuming? If I didn't remember wrong, Kafka allows consumers to read __consumer_offsets and some admin tools are implemented by this way.

OK, the consume may expose to users.

@hangc0276 hangc0276 requested a review from BewareMyPower April 23, 2021 02:24
@hangc0276 hangc0276 requested a review from BewareMyPower April 23, 2021 04:00
@hangc0276 hangc0276 self-assigned this Apr 25, 2021
@BewareMyPower
Copy link
Collaborator

I see it works well with system topic enabled. Is apache/pulsar#10341 necessary?

@BewareMyPower
Copy link
Collaborator

Sorry I just misunderstood.

@BewareMyPower BewareMyPower merged commit 398f61a into streamnative:master Apr 26, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants