Maintenance Notice (July 23, 2026)

We are scheduling maintenance to address a security vulnerability, as described below. This maintenance involves rebooting compute nodes and will affect running workloads, so please review the details. We apologize for any inconvenience and appreciate your understanding and cooperation.

Scheduled Maintenance Date:

Thursday, July 23, 2026

Time:

9:00 – (all day)

Affected Service:

Kubernetes Service (including the Workspace feature)

Affected Sites:

SR1, IK1, YH1, IZ1

AW1 is not covered by this maintenance. Affected users at this site will be contacted individually.

Impact:

As with cluster upgrades, compute nodes will be rebooted sequentially (up to 25% at a time) rather than all at once.

Compute nodes will be rebooted to apply the kernel update. Applications (Pods) running on Kubernetes and Workspace execution environments will be temporarily stopped, deleted, and recreated.
Pods created directly without a higher-level resource such as a Deployment or Job will not be recreated automatically.
Data stored in persistent storage (PVCs, etc.) is not affected. However, data not in persistent storage — including data inside Pods and Workspace execution environments — will be lost.
Reserved nodes allocated to users will be temporarily unavailable while they are being rebooted.
- If you have fewer than 4 reserved nodes, they will be rebooted one at a time. If you have 4 or more, up to 25% (rounded down) will be temporarily unavailable at a time.
- If you have only 1 reserved node, it will be temporarily unavailable.
Up to 25% (rounded down) of shared nodes will be temporarily unavailable.

Reason:

To update compute nodes to a Linux kernel version that includes a fix for the discovered vulnerability.

Action requested of users:

If you use Kubernetes services or the Workspace feature, save any necessary data to persistent storage before maintenance begins.
If you need to preserve in-progress computation state, complete checkpointing before maintenance starts.
If you have created Pods directly without a higher-level resource such as a Deployment or Job, those Pods will not be recreated automatically. Please review your configuration in advance.

This maintenance is an emergency maintenance conducted in response to a critical security vulnerability. For our maintenance policy, see the User Guide.