Warning
This page was translated from the original Japanese version by PLaMo Translate. The Japanese version is authoritative; the English translation may contain inaccuracies.
Maintenance Policy
This section outlines the policies for scheduled and emergency maintenance activities.
Scheduled Maintenance Policy
PFCP implements regular scheduled maintenance to maintain system reliability.
| Item | Details |
|---|---|
| Maintenance Date | First Monday of each month |
| Announcement of Maintenance Date | At least one month in advance (Only announced if there are changes from the first Monday schedule) |
| Announcement of Maintenance Details | Two weeks prior to the maintenance date (Only announced when maintenance is actually scheduled) |
Kubernetes Version Upgrade Policy
We regularly perform minor version upgrades to improve Kubernetes cluster stability, performance, and security.
| Item | Details |
|---|---|
| Frequency | Every 4 months |
| Upgraded Version | The previous minor version from the latest release (For example, if the latest is v1.30, the upgraded version would be v1.29) |
| Announcement of Maintenance Date | Announced as part of the scheduled maintenance details |
Impact of Upgrades and Other Maintenance Activities on Clusters and Workloads
This section describes the user impacts of maintenance activities that involve temporary shutdowns of compute nodes, such as cluster upgrades.
Impact on Clusters and Compute Nodes
- Temporary instability in cluster operations may occur
- User-allocated dedicated nodes will have their upgraded compute nodes temporarily unavailable
- For contracts with fewer than 4 dedicated nodes, one node will be temporarily unavailable; for contracts with 4+ nodes, up to 25% (rounded down) will be unavailable
- For contracts with only one dedicated node, no nodes will be temporarily available for use
- Shared nodes will be temporarily unavailable by 25% (rounded down)
Impact on Workloads
- Workloads currently running on the compute nodes undergoing upgrade will be terminated
- Terminated workloads will be automatically recreated on different compute nodes or the same node, depending on rescheduling policies
- Workloads directly created by users (Bare Pods) without using higher-level resources like Deployments or Jobs will not be automatically recreated
- We strongly recommend avoiding direct creation of Pod resources
Warning
Important Note on Data Preservation
- Be aware that any data retained by workloads that is not stored in persistent storage will be lost
- This includes data stored in local memory, temporary filesystems, etc.
- Data stored in persistent storage will be preserved
Recommended Preparations for Compute Node Maintenance
- Always store critical data such as computation results and outputs in persistent storage
- If your workloads are stateful, thoroughly plan and prepare procedures for data persistence and recovery
Important
Workloads and processes may stop for reasons beyond maintenance or failures. Always store critical data in persistent storage.
Emergency Maintenance Policy
Unscheduled maintenance may be conducted under circumstances where service continuity is difficult to maintain or when critical security vulnerabilities are discovered. When maintenance affects clusters, compute nodes, or workloads, we will provide advance notice of the planned activities.
Staying Informed About Maintenance Activities
All new maintenance information will be posted on the PFCP News Site. For details, please refer to Notification of New Features and Maintenance.