Azure / Azure/Azure-Spring-Apps

Preparing for Planned Maintenance

オープン
#41 コメント 10 件 リアクション 0 件 担当者 2 名 @zmssp が担当を希望しています GitHub で見る
主要言語
言語のデータがありません
スター
9
フォーク
11
PR マージ指標
30日以内にマージされた PR はありません

説明

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

コントリビューションガイド

このリポジトリのコントリビューションガイドは索引されていません

評価

この issue はまだ評価されていません。

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。