-
Notifications
You must be signed in to change notification settings - Fork 16
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
Document Eventing States More Detailed #328
Conversation
docs/user/02-configuration.md
Outdated
|
||
Warnings indicate that user action is required, that is, the user must install the NATS module or create an EventMesh Secret. | ||
|
||
| Backend Config | Backend State | State | |
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.
the idea of this ticket was to clearly document which combination of settings will cause what sort of state
eg:
EV-configuration backend: NATS
NATS cluster: not available
resulting EV-STATE: ? (no events will be accepted / dispatched)
EV backend: NATS
NATSCluster: available (even if the NATS-module is currently being deleted)
Eventing: READY (events will still be accepted / dispatched)
....
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.
Second case you mentioned is still under development. I either document and wait until Marco is finished, or Marco will document it here. What do do think?
54b42e1
to
415d571
Compare
415d571
to
05411aa
Compare
docs/user/02-configuration.md
Outdated
|
||
Warnings indicate that user action is required, that is, the user must install the NATS module or create an EventMesh Secret. | ||
|
||
| Backend Config | Backend State | Backend Type | Eventing State | Addition comment | |
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.
Imho it would be easier to grep if we would sort the table by impact on event flow.
05411aa
to
779208d
Compare
docs/user/02-configuration.md
Outdated
| exists | Error (NATS ist unavailable or cannot be connected) | NATS | Warning | no events will be accepted / dispatched | | ||
| missing | | NATS/EventMesh | Warning | no events will be accepted / dispatched | | ||
| exists | Error (secret for EventMesh missing) | EventMesh | Warning | no events will be accepted / dispatched | | ||
| exists | Error (cases not caused by a user, e.g. cannot create EPP deployment or cannot start subscription manager although backend is available) | NATS/EventMesh | Error | no events will be accepted / dispatched | | ||
| exists | Processing (mainly happens during initialization and backend switching) | NATS/EventMesh | Processing | no events will be accepted / dispatched | | ||
| exists | Missing | NATS | Warning | no events will be accepted / dispatched | | ||
| exists | Warning (NATS deletion blocked) | NATS | Ready | events will be accepted / dispatched | |
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.
| exists | Error (NATS ist unavailable or cannot be connected) | NATS | Warning | no events will be accepted / dispatched | | |
| missing | | NATS/EventMesh | Warning | no events will be accepted / dispatched | | |
| exists | Error (secret for EventMesh missing) | EventMesh | Warning | no events will be accepted / dispatched | | |
| exists | Error (cases not caused by a user, e.g. cannot create EPP deployment or cannot start subscription manager although backend is available) | NATS/EventMesh | Error | no events will be accepted / dispatched | | |
| exists | Processing (mainly happens during initialization and backend switching) | NATS/EventMesh | Processing | no events will be accepted / dispatched | | |
| exists | Missing | NATS | Warning | no events will be accepted / dispatched | | |
| exists | Warning (NATS deletion blocked) | NATS | Ready | events will be accepted / dispatched | | |
| exists | Warning (NATS deletion blocked) | NATS | Ready | events will be accepted / dispatched | | |
| exists | Processing (mainly happens during initialization and backend switching) | NATS/EventMesh | Processing | no events will be accepted / dispatched | | |
| exists | Error (NATS ist unavailable or cannot be connected) | NATS | Warning | no events will be accepted / dispatched | | |
| missing | | NATS/EventMesh | Warning | no events will be accepted / dispatched | | |
| exists | Missing | NATS | Warning | no events will be accepted / dispatched | | |
| exists | Error (secret for EventMesh missing) | EventMesh | Warning | no events will be accepted / dispatched | | |
| exists | Error (cases not caused by a user, e.g. cannot create EPP deployment or cannot start subscription manager although backend is available) | NATS/EventMesh | Error | no events will be accepted / dispatched | |
More detailed documentation of the Eventin CR state