Azure / Azure/Azure-Spring-Apps

Preparing for Planned Maintenance

Ouverte
#41 10 commentaires 0 réactions 2 personnes assignées Réclamée par @zmssp Voir sur GitHub
Langage dominant
Aucune donnée de langage
Étoiles
9
Forks
11
Métriques de merge des PR
Aucune PR mergée en 30 j

Description

**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.

Guide de contribution

Aucun guide de contribution indexé pour ce dépôt

Évaluation

Cette issue n'a pas encore été évaluée.

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.