Azure / Azure/Azure-Spring-Apps

Preparing for Planned Maintenance

Offen
#41 10 Kommentare 0 Reaktionen 2 zugewiesene Personen Beansprucht von @zmssp Auf GitHub ansehen
Vorherrschende Sprache
Keine Sprachdaten
Sterne
9
Forks
11
PR-Merge-Kennzahlen
Keine gemergten PRs in 30 T.

Beschreibung

**Is your feature request related to a problem? Please describe.**

Within Azure Spring Cloud, we sometimes find after a planned maintenance that some of our apps seem to be impacted by planned maintenance. We have an alert setup on the resource health, so we're notified of any degraded apps after the event.

Additionally, we are looking to setup alerts of planned application lifecycle events and understand that the underlying Kubernetes version is updated every 2-4 months. However, the planned maintenance description does not provide any details on the change or what functionality that has changed within Azure Spring Cloud. This makes it tricky to proactively plan for any planned maintenance.

**Describe the solution you'd like**

Further information within the description as to what change is being planned so we can proactively plan for the maintenance in advance. It would also be good it we had control as to when it is applied into different environments. For example, apply the planned maintenance into a non-production environment first.

**Describe the Customer Impact**

Degraded apps after a planned maintenance.

Beitragsleitfaden

Für dieses Repository ist kein Beitragsleitfaden indexiert

Bewertung

Dieses Issue wurde noch nicht bewertet.

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.