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.
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
Setup feature flag and scaffolding for a JetStream backend #13259
Setup feature flag and scaffolding for a JetStream backend #13259
Conversation
Skipping CI for Draft Pull Request. |
7c7a916
to
8dbabb5
Compare
/retest |
cb2988f
to
f147d64
Compare
e005b18
to
3b83958
Compare
/test pre-main-kyma-gardener-gcp-eventing |
/test pre-main-kyma-gardener-azure-alpha-eval |
47e633e
to
a12b42e
Compare
/test pre-main-kyma-gardener-gcp-eventing |
86a5dd3
to
ce557f1
Compare
/test pre-main-kyma-gardener-gcp-eventing |
ce557f1
to
1d751d3
Compare
1d751d3
to
ec1d53d
Compare
/test pre-main-kyma-gardener-gcp-eventing |
r.namedLogger().Errorw("setup watch for subscriptions failed", "error", err) | ||
return err | ||
} | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
(nit) should we also set a watch for nats pods. As in NATS.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't think so. IMO adding other watchers should happen depending on the logic, which is empty for now.
sm.mgr.GetEventRecorderFor("eventing-controller-jetstream"), | ||
sm.envCfg, | ||
) | ||
// TODO(PS): this could be refactored (also in other backends), so that the backend is created here and passed to |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
(nit) is this TODO(PS)
relevant for the team? or was it for you only?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It's also for the team. Just an old habit! Is it ok to leave it like that? Most likely, I'll work on it as part of the missing unit test tickets.
@pxsalehi: The following tests failed, say
Full PR test history. Your PR dashboard. 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/test-infra repository. I understand the commands that are listed here. |
Description
Changes proposed in this pull request:
Related issue(s)
Closes #13251