Skip to content

Conversation

@astelmashenko
Copy link
Member

Introduced alternative broker implementations custom broker for Nats Jetstream

Add the core broker controller implementation for NATS JetStream:

- Add broker controller with JetStream stream management
- Add reconciler with ingress/filter deployment and service creation
- Add resource builders for ingress and filter components
- Add broker naming utilities for streams, subjects, and consumers
- Update main.go with fsloader context injection

The broker controller:
- Creates a JetStream stream per broker
- Deploys ingress deployment/service for receiving events
- Deploys filter deployment/service for event filtering
- Propagates status conditions based on endpoint availability
- Cleans up JetStream stream on broker deletion
@knative-prow knative-prow bot requested a review from aliok January 5, 2026 21:30
@knative-prow
Copy link

knative-prow bot commented Jan 6, 2026

There are empty aliases in OWNER_ALIASES, cleanup is advised.

@knative-prow
Copy link

knative-prow bot commented Jan 6, 2026

There are empty aliases in OWNER_ALIASES, cleanup is advised.

@astelmashenko
Copy link
Member Author

@Cali0707 , I implemented custom broker for Nats Jetstream, it is quite big PR. I assign it to you, if you think you need help to review it or somebody else should do it, please re-assign.

@astelmashenko
Copy link
Member Author

/assign @Cali0707

@astelmashenko astelmashenko marked this pull request as draft January 8, 2026 21:04
@knative-prow knative-prow bot added the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Jan 8, 2026
@astelmashenko
Copy link
Member Author

Converted to draft, this PR will be split into smaller reviewable PRs.

@knative-prow-robot knative-prow-robot added the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Jan 16, 2026
@knative-prow-robot
Copy link
Contributor

PR needs rebase.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. size/XXL Denotes a PR that changes 1000+ lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants