You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If I have misunderstood, and the README is referring to something other than the channel as being in BETA, I anyway think the README should be explicit about the status of the channel as this is going to be of most interest to users of the knative extension.
I'm happy to raise PRs but it's unclear what the change should be.
Once we've cleared this up, I think it would also be helpful to raise a PR against knative docs to replace references to NATSS with Nats Jetstream, at the appropriate maturity level, as that's also confusing. However, I don't want to do that until I am sure the README.md here is accurate and the maturity level is well understood.
The text was updated successfully, but these errors were encountered:
Good day, I recently removed nats-streaming, which was beta, I tried to cleanup all places but certainly missed few.
Starting 1.16 there is only JetSteam based channel implementation, which is v1alpha1 in codebase, but actually we are using it in production for around 18 months. It is pretty stable.
The reason it is alpha is probably it is based on JetStream push consumers, which are deprecated now, and I need to migrate them to pull-consumers.
README.md states that components are in BETA.
However, the channel is still under the v1alpha1 package and the main knative documentation states only that there is NATSS (the old NATS streaming channel) in alpha status, here: https://github.com/knative/docs/blob/main/docs/eventing/channels/channels.yaml
Which is correct?
If I have misunderstood, and the README is referring to something other than the channel as being in BETA, I anyway think the README should be explicit about the status of the channel as this is going to be of most interest to users of the knative extension.
I'm happy to raise PRs but it's unclear what the change should be.
Once we've cleared this up, I think it would also be helpful to raise a PR against knative docs to replace references to NATSS with Nats Jetstream, at the appropriate maturity level, as that's also confusing. However, I don't want to do that until I am sure the README.md here is accurate and the maturity level is well understood.
The text was updated successfully, but these errors were encountered: