Key concepts
KakaoCloud Maintenance service helps manage OS, engine, kernel upgrades, and configuration changes for instances in a systematic way. Users can create tasks, schedule them by resource, and perform maintenance easily through an intuitive UI. Monitoring task and execution status, receiving prior notifications, and managing automated execution reduce unexpected failures and improve operational efficiency.
Maintenance key concepts
Maintenance service manages updates for multiple resources as user-defined task units, ensuring safe execution of OS, engine, and kernel upgrades and configuration changes per resource. Users can monitor execution flow based on the linked state structure between tasks and resources, and tasks can be scheduled to run automatically at reserved times. Results are monitored in real time, with execution status management for retries and exception handling when errors occur. Users can grasp task status at a glance via an intuitive UI, enabling stable management of large-scale maintenance tasks while ensuring both failure prevention and operational efficiency.
Task
A task is a unit that manages maintenance activities such as OS, engine, kernel upgrades, or configuration changes in KakaoCloud services. Multiple resources can be grouped for management, allowing comprehensive monitoring of execution flow and status. Schedules can be configured at task or resource level, enabling planned and safe maintenance. Items included in a task are as follows:
| Item | Description |
|---|---|
| Service | Service where task is executed |
| Requirement | Indicates whether task is mandatory or recommended - Mandatory: Must be executed within the deadline - Recommended: Optional; can be executed even after recommended date |
| Recommended schedule | Suggested schedule for executing task - Depends on requirement; for recommended tasks, updates can be performed even after the suggested date |
| Priority | Importance level used to set task execution order - High/medium/low priority determines execution order |
| Type | Update target of task - Examples: Kernel upgrade, Engine upgrade, OS update |
| Downtime | Indicates whether service interruption occurs during task execution - Classified as Downtime/No downtime; downtime may cause short impact |
| Target resources | Resources included in task - Each resource can have its own schedule and execution status |
| Task status | Overall progress status of task - Determined based on states of included resources - Examples: Pending, Reserved, In progress, Completed, Failed |
Resource
A resource is an individual instance or engine included in a task, representing an actual component to be updated. Schedules and execution statuses are managed per resource within a task, enabling detailed progress tracking and quick issue response. Items included for a resource are as follows:
| Item | Description |
|---|---|
| Resource name | Name of resource |
| Resource ID | Unique identifier for resource |
| Task schedule | Reserved schedule for executing the task - Recommended schedule is not displayed; resources without a reserved schedule show a hyphen ( -). Users can set schedules per resource |
| Execution status | Execution status of individual resource included in task - Each resource can have different states such as Pending, In progress, Completed, Failed |
Maintenance service status
Maintenance service uses two state types: task status and resource execution status.
Task status is determined by aggregating the execution results of resources included in the task. It changes based on resource statuses.
- Task status: Indicates overall progress of the entire task by aggregating statuses of multiple resources. Shows overall flow from start to completion, failure, or in-progress.
- Resource execution status: Indicates status of individual resource within task. Each resource can have different states such as Pending, In progress, Completed, or Error. Helps check detailed progress and detect issues.
Maintenance status
Task status
Represents the overall state of a task, determined by aggregating statuses of included resources.
| Status | Description | Classification |
|---|---|---|
Pending | No scheduled time set for one or more resources - Initial state after task creation | Gray |
Reserved | All resources, including excluded ones, have a scheduled time set | Green |
In progress | One or more resources are running, and others are in Completed/Failed/In progress state - When in progress, counts of Completed/Failed resources are displayed | Green |
Completed | All resources, including excluded ones, have completed execution | Green |
Failed | All resources, including excluded ones, have failed execution | Red |
Excluded | Excluded from update task target | Gray |
Resource execution status
Represents the individual progress state managed for each resource.
| Status | Description | Classification |
|---|---|---|
Pending | No scheduled time set - Initial state after task creation | Gray |
Reserved | Scheduled time set | Green |
In progress | Execution in progress | Green |
Completed | Execution completed | Green |
Failed | Execution failed due to various reasons | Red |
Excluded | Excluded from update task target | Gray |
Maintenance provided services
Currently, Maintenance service is provided only for MySQL, but other KakaoCloud managed services including PostgreSQL will be gradually added.
| Service | Description |
|---|---|
| MySQL | OS, engine, kernel updates |