Azure / Azure/Azure-Spring-Apps

Preparing for Planned Maintenance

Abierto
#41 10 comentarios 0 reacciones 2 asignados Reclamado por @zmssp Ver en GitHub
Lenguaje dominante
Sin datos de lenguaje
Estrellas
9
Forks
11
Métricas de merge de PR
Sin PR fusionados en 30 d

Descripción

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

Guía de contribución

No hay ninguna guía de contribución indexada para este repositorio

Evaluación

Este issue todavía no se ha evaluado.

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.