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

Feature: Add Azure Resource Health #2762

Open
Tracked by #3531
nojnhuh opened this issue Mar 2, 2023 · 4 comments
Open
Tracked by #3531

Feature: Add Azure Resource Health #2762

nojnhuh opened this issue Mar 2, 2023 · 4 comments
Labels
capz Required for CAPZ ASO adoption new-feature

Comments

@nojnhuh
Copy link
Member

nojnhuh commented Mar 2, 2023

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:

kind: ResourceHealth
spec:
  id: <resource ID>
status:
  availabilityState: Available
  ...
@matthchr
Copy link
Member

matthchr commented Mar 7, 2023

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: serviceoperator.azure.com/showservicehealth or something

@matthchr
Copy link
Member

matthchr commented Mar 7, 2023

This is also a bit interesting in that it might want a faster reconcile pass than other resources

@theunrepentantgeek theunrepentantgeek modified the milestones: v2.3.0, v2.2.0 May 31, 2023
@matthchr matthchr modified the milestones: v2.2.0, v2.3.0 Jul 6, 2023
@matthchr matthchr added the capz Required for CAPZ ASO adoption label Jul 12, 2023
@matthchr matthchr modified the milestones: v2.4.0, v2.3.0 Jul 24, 2023
@matthchr matthchr modified the milestones: v2.3.0, v2.4.0 Aug 28, 2023
@theunrepentantgeek theunrepentantgeek modified the milestones: v2.5.0, v2.4.0 Sep 7, 2023
@matthchr matthchr modified the milestones: v2.4.0, v2.5.0 Nov 6, 2023
@theunrepentantgeek theunrepentantgeek modified the milestones: v2.6.0, v2.5.0 Nov 14, 2023
@matthchr matthchr modified the milestones: v2.5.0, v2.6.0 Nov 20, 2023
@theunrepentantgeek theunrepentantgeek removed this from the v2.6.0 milestone Dec 11, 2023
@theunrepentantgeek theunrepentantgeek modified the milestones: v2.7.0, v2.6.0 Dec 11, 2023
@matthchr matthchr removed this from the v2.6.0 milestone Feb 22, 2024
@matthchr
Copy link
Member

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.

@matthchr
Copy link
Member

matthchr commented Feb 3, 2025

No change in above.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
capz Required for CAPZ ASO adoption new-feature
Projects
Development

No branches or pull requests

3 participants