Skip to content
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

Leverage error status in module state #1375

Open
a-thaler opened this issue Aug 22, 2024 · 0 comments
Open

Leverage error status in module state #1375

a-thaler opened this issue Aug 22, 2024 · 0 comments

Comments

@a-thaler
Copy link
Collaborator

Description
The state of a module was incorporated in the overall "Kyma" CR state in the past. An error state for "Kyma" indicated an operational problem. That got decoupled and and a bad module status will not trigger any operartional actions anymore. Instead it will be fully user facing and indicates a problem on user side.

Consequently, the state of the telemetry module should be calculated properly now, indicating:

  • an error: for permanent problems
  • a warning: for temporary or forecasted problems (aboutToExpire)

Criterias

  • The module state leverages error as value appropriate
  • Documentation got adjusted were needed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant