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
Currently, Kubernetes does not offer a solution to proactively notify users of major changes to their cluster. This lack of proactive notifications can lead to missed issues, increased downtime, or delayed responses to critical changes. A more proactive monitoring and alerting system is needed to help users quickly identify and respond to issues..
Solution
The system can monitor changes in users clusters using audit lots, API server events, and version changes. Major changes are classified as upgrades that might affect future performance and breaking changes can be classified as changes that will cause backwards issues. Upon change detection, users will get an email notification with details about the change, consequences, and potentially steps on how to address it.
Additional information
No response
👨👧👦 Contributing
🙋♂️ Yes, I'd love to make a PR to implement this feature!
The text was updated successfully, but these errors were encountered:
Problem
Currently, Kubernetes does not offer a solution to proactively notify users of major changes to their cluster. This lack of proactive notifications can lead to missed issues, increased downtime, or delayed responses to critical changes. A more proactive monitoring and alerting system is needed to help users quickly identify and respond to issues..
Solution
The system can monitor changes in users clusters using audit lots, API server events, and version changes. Major changes are classified as upgrades that might affect future performance and breaking changes can be classified as changes that will cause backwards issues. Upon change detection, users will get an email notification with details about the change, consequences, and potentially steps on how to address it.
Additional information
No response
👨👧👦 Contributing
The text was updated successfully, but these errors were encountered: