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
Improve tooling for all Kyma teams to rapidly get accurate information about the state of failing KEB operations provisioning, deprovisioning, and update within runtimes, focusing on the status of all dependent services.
An additional object in the JSON runtimes endpoint response which provides information about an error(s). It must contain the following information: component (for example Provisioner, Lifecycle Manager, Infrastracture Manager etc.), a message dedicated to an operator (contains proper details needed for investigation). Consider adding an error code which could be used for statistics. The operation description must not contain too much details - it goes to a customer.
KCP CLI provides information about the team (component -> team mapping)
KCP CLI shows a summary of a runtime
Runtimes endpoint provides a current step. It is a step which has been executed last time. Currently this information is not stored in the DB. There are two solutions: use internal, in memory pub sub or persist information about current in progress step in the operation (DB)
The text was updated successfully, but these errors were encountered:
Improve tooling for all Kyma teams to rapidly get accurate information about the state of failing KEB operations provisioning, deprovisioning, and update within runtimes, focusing on the status of all dependent services.
runtimes
endpoint response which provides information about an error(s). It must contain the following information: component (for example Provisioner, Lifecycle Manager, Infrastracture Manager etc.), a message dedicated to an operator (contains proper details needed for investigation). Consider adding an error code which could be used for statistics. The operation description must not contain too much details - it goes to a customer.The text was updated successfully, but these errors were encountered: