-
Notifications
You must be signed in to change notification settings - Fork 61
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
State of stream and actual state might be different #45
Comments
Also need to encode it to HTML maybe to avoid entities in the subjects when using wildcards? |
Sounds similar to several scenarios I encountered. E.g. JetStream was not enabled so Stream CRD is now permanently errored even after JetStream is enabled. Seems I have to delete and re-create the Stream CRD in order to fix. I wish the operator was able to recover from Errored states automatically. |
Yeah, we are also experiencing issues where state in the JS cluster isn't reflected back to the CR's. Say for example we define a stream and several consumers of that stream, if the stream is deleted, the consumers still show in k8s as being ok. Ideally some kind of continuous reconciliation should be in place to make sure that what is defined in the CR is what is in JS, or the status updated accordingly. |
A result of doing
kubectl get streams
can show:Although there is no issue with the streams themselves:
The text was updated successfully, but these errors were encountered: