Page MenuHomePhabricator

🚦 Notification about maintenance window on Status page
Closed, ResolvedPublic

Assigned To
Authored By
Anton.Kokh
Jul 30 2024, 12:37 PM
Referenced Files
F57777814: image.png
Dec 4 2024, 9:30 AM
F57753198: image.png
Nov 27 2024, 1:40 PM
Restricted File
Nov 26 2024, 9:36 AM
F57749260: image.png
Nov 26 2024, 9:36 AM
F57453697: grafik.png
Sep 4 2024, 9:19 AM
F57452472: grafik.png
Sep 4 2024, 9:19 AM

Description

Communicate on the Status page about the possible problems related to the update window scheduled for Kubernetes nodes every Monday

Copy: We regularly run automated maintenance updates on a Monday; these often happen in early morning UTC and often cause short term service disruption or a full outage.

Link to Figma

grafik.png (1,572×1,204 px, 129 KB)

Ideally we could reuse whatever is happening here except that I'd like to remove the title and the link

grafik.png (1,528×940 px, 91 KB)

Let me (@Charlie_WMDE ) know if you have any questions/want to pair.

Event Timeline

@Tarrow Could you please come up with text that would be meaningful to describe the maintenance window situation?

"We regularly run automated maintenance updates on a Monday; these often happen in early morning UTC and often cause short term service disruption or a full outage"

Charlie_WMDE updated the task description. (Show Details)
Charlie_WMDE subscribed.

We discussed the implementation with @dang .
It's not possible to remove the link and the title above the announcement without touching the parent repository.
Another problem is that the announcement will show up twice - pinned to the top of the page and directly in the history of announcements (it has to be assigned to a certain date and time).

image.png (507×495 px, 89 KB)

This seems confusing to me.
Maybe, what would make it less confusing is if this announcement would just be added every Monday morning and then disappear (physically adding and removing the pinned-announcement.md on schedule).
{F57749268}
Would it be possible/meaningful, @Tarrow ?

Also tagging @Charlie_WMDE

I had a look and I see two possible options to avoid any changes to upstream or layouts:

  • still do a pinned announcement but set the date far in the past
  • regularly create informational sections like you mentioned; to me this sounds rather annoying but I guess possible. Perhaps we could automate it with github actions?

I wonder if we could also manipulate the content of issue.html to suppress the occurrence in the timeline? Perhaps you can figure out some go templating to exclude informational ones?

and I discovered that you can also customise the announcements sections without poking inside the submodules by copying it into the layouts folder. see https://github.com/wmde/wikibase-cloud-status/pull/7/files

Feel free to take the ideas form either of these for your PR

I rewrote this based on @Tarrow's suggestion and also removed some unnecessary code. Please check it out @Anton.Kokh @Charlie_WMDE
https://github.com/wmde/wikibase-cloud-status/pull/5

hey @dang i can not find the netlify link to review the changes. could you please provide it for me? thanks.

@Charlie_WMDE unfortunately there is no netlify preview for this. Are you happy to "post merge" review it?

For a quick peak from the branch I checked out

image.png (943×715 px, 46 KB)

@Charlie_WMDE There's no netlify preview, do you want to jump in a call for this?

@Charlie_WMDE unfortunately there is no netlify preview for this. Are you happy to "post merge" review it?

For a quick peak from the branch I checked out

image.png (943×715 px, 46 KB)

@Tarrow yes, let's do that 👍 the pic doesn't show up for me btw 🤔

Hey @dang @Tarrow i'm wondering if this is expected behaviour?

image.png (1,406×1,058 px, 147 KB)

the notifications is in the same "box" as the current incident. ideally i'd like the notification to be below the incident "box" the way it is in tom's last screenshot when there was no incident.

if this isn't possible, i can accept that and we can keep it as is, but wanted to ask in case it can be changed.

Yes, if there is no warning/disruption, there will be no box border

my question was, whether we could also remove the border for when there's a warning