Documentation Index

Fetch the complete documentation index at: https://guide.ncloud-docs.com/llms.txt

Use this file to discover all available pages before exploring further.

Add-on installation and management

Prev Next

Available in VPC

Add-on installation and management

This guide describes how to install add-ons, change their settings and versions, and delete them.

Install during cluster creation

When creating a cluster, specify the add-ons to install from the [Add-on] tab menu. The specified add-ons are installed during cluster creation. For the complete cluster creation procedure, see Getting started with Ncloud Kubernetes Service.

Specify the following items.

  • Select add-on: Specify multiple add-ons at once to install them together.
  • Select version: Specify the version to install for each add-on.
  • Enter settings: Enter the settings defined for each add-on. If no values are entered, the default values are used.

Install add-ons on running cluster

Add add-ons that are not installed on a running cluster. Add-ons that are already installed are excluded from the installation targets.

To install an add-on on a running cluster:

  1. Click the [Add-on] tab menu in the cluster details.
  2. Click [Import add-on].
  3. Click the add-on to install.
  4. Click the version to install.
  5. Enter the settings. If no setting values are entered, the default values are used.
  6. Click to select a conflict management method. For details, see Conflict management.
  7. Click [OK]. Installation starts.

Conflict management

An add-on creates the final configuration by applying the settings entered by the user to the default settings and applies it to the cluster. Default settings are used for items that are not entered. Changing the configuration by entering settings does not constitute a conflict.

Conflicts occur only in fields that the user has modified directly in the cluster (e.g., kubectl edit). If no fields have been modified directly, the result is the same regardless of the method selected.

Method Description
Overwrite (default) Even if the user has modified fields directly, they are overwritten with the values from the final configuration. The task does not fail due to conflicts.
Preserve Fields modified directly by the user are left unchanged, while the remaining fields are updated with the values from the final configuration. The task may fail if a directly modified value conflicts with this value.

Change settings and upgrade version

Change the version and settings of an installed add-on. The edit interface opens with the current settings populated.

To edit an installed add-on:

  1. Click the [Add-on] tab menu in the cluster details.
  2. Click [Edit] for the add-on to edit.
  3. Change the version if necessary. You can click to select a version that is compatible with the cluster.
  4. Modify the settings if necessary.
  5. Click to select a conflict management method. The criteria and behavior are the same as those described in Conflict management.
  6. Click [OK]. The changes are applied.
Note

If the changes are rejected or validation fails, the system automatically attempts to restore the previous working state (version and settings). However, automatic restoration is not performed if the changes are successfully applied but a runtime issue subsequently occurs (e.g., repeated container restarts).

Delete add-on

Remove an installed add-on from the cluster.

To delete an installed add-on:

  1. Click the [Add-on] tab menu in the cluster details.
  2. Click [Delete] for the add-on to delete.
  3. Review the information in the confirmation window, and then proceed with the deletion. Deletion starts.
Caution

Deleting an add-on removes the resources installed through the add-on. Before deletion, make sure that no workloads that depend on the add-on resources remain in the cluster. However, resources containing user data (e.g., volume snapshots in use) may be retained for protection. Manually remove any retained resources when necessary.

Check failed task

If a task fails, the add-on status is displayed as failed, and the cause is shown in the task result message. Check the message, adjust the settings, version, or conflict management method, and then try again.