-
Notifications
You must be signed in to change notification settings - Fork 206
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
Feature: Add Azure Resource Health #2762
Comments
The other way that I mentioned which I don't know if I love, is that we have a spot for it on status but we only fill that out if you ask us to via an annotation. Think: |
This is also a bit interesting in that it might want a faster reconcile pass than other resources |
This is still something we're interested in, but will need to do some design work before we can implement it as not every resource has resource health, and we need to define how we would expose health to users and also how users opt in/out of it. |
No change in above. |
Azure provides a Resource Health API that reports certain issues with certain types of Azure resources. Having that same data accessible from ASO would be useful downstream in projects like CAPZ that already integrate with Resource Health using the Go SDK directly.
Overview: https://learn.microsoft.com/en-us/azure/service-health/resource-health-overview
API docs: https://learn.microsoft.com/en-us/rest/api/resourcehealth/
I imagine that data could either be used to augment the existing
status
of the existing resource or in a new API type that might look something like:The text was updated successfully, but these errors were encountered: