Add-on list

Available in VPC

The following add-ons are provided by Ncloud Kubernetes Service (NKS).

NKS Block Storage CSI

This CSI driver uses block storage as a Kubernetes PersistentVolume. Installing this add-on allows you to dynamically provision block storage-based volumes and mount them to pods.

After installation, see the Block Storage CSI examples for usage instructions.

Settings

The available settings are as follows.

The following is an example.

{
  "scheduling": {
    "nodeSelector": {
      "role": "storage"
    },
    "extraTolerations": [
      {
        "key": "dedicated",
        "operator": "Equal",
        "value": "storage",
        "effect": "NoSchedule"
      }
    ]
  }
}

NKS NAS (NFS) CSI

This CSI driver uses NAS (NFS) volume as Kubernetes PersistentVolume. Use it when you need a shared volume that multiple pods can access simultaneously.

After installation, see the NAS volume CSI examples for usage instructions.

Settings

The available settings are as follows.

The following is an example.

{
  "scheduling": {
    "nodeSelector": {
      "role": "storage"
    },
    "extraTolerations": [
      {
        "key": "dedicated",
        "operator": "Equal",
        "value": "storage",
        "effect": "NoSchedule"
      }
    ]
  }
}

ExternalDNS

This controller automatically registers and manages DNS names configured for Kubernetes Services and Ingresses with an external DNS service. Installing this add-on eliminates the need to manually manage domains exposed by workloads.

After installation, see the ExternalDNS use cases for usage instructions.

Settings

The settings provided by ExternalDNS are as follows.

The following is an example.

{
  "sources": ["service", "ingress", "crd"],
  "domainFilter": "example.com,foo.io",
  "annotationFilter": "external-dns.alpha.kubernetes.io/include=true",
  "labelFilter": "team=infra",
  "txtPrefix": "",
  "txtSuffix": "-edns",
  "policy": "sync",
  "logLevel": "info",
  "credentials": {
    "secretName": "external-dns-credentials"
  },
  "scheduling": {
    "nodeSelector": {
      "role": "external-dns"
    },
    "extraTolerations": [
      {
        "key": "dedicated",
        "operator": "Equal",
        "value": "dns",
        "effect": "NoSchedule"
      }
    ]
  }
}

NKS Gateway API Adapter

This adapter connects Gateway API resources (Gateway, HTTPRoute) to NAVER Cloud Application Load Balancer (ALB). Installing this add-on allows you to configure external traffic routing using standard Gateway API resources.

After installation, see Using Gateway API for usage instructions.

Settings

The available settings are as follows.

The following is an example.

{
  "scheduling": {
    "nodeSelector": {
      "role": "gateway"
    },
    "extraTolerations": [
      {
        "key": "dedicated",
        "operator": "Equal",
        "value": "gateway",
        "effect": "NoSchedule"
      }
    ]
  }
}

Istio

Istio is a service mesh that provides traffic management, mTLS-based security, and observability for service-to-service communication within a cluster. This add-on installs the Istio control plane (istiod). For information on sidecar injection and using mesh features, see the official Istio documentation.

This add-on supports Canary upgrades. Each installed version line has a Revision (e.g., the Revision of version 1.30.3 is 1-30), and each namespace uses the istio.io/rev label to specify the Revision whose sidecars are injected into it. For the upgrade procedure, see Canary upgrade in Add-on installation and management.

Settings

The settings provided by Istio are as follows. The meshConfig field passes Istio's mesh configuration (MeshConfig) as is. For the behavior of each field, see the Istio MeshConfig reference.

The following is an example.

{
  "meshConfig": {
    "accessLogFile": "/dev/stdout",
    "accessLogEncoding": "JSON",
    "outboundTrafficPolicy": { "mode": "REGISTRY_ONLY" },
    "meshMTLS": { "minProtocolVersion": "TLSV1_2" },
    "extensionProviders": [
      {
        "name": "otel",
        "opentelemetry": {
          "service": "otel-collector.observability.svc.cluster.local",
          "port": 4317
        }
      }
    ]
  },
  "nodeSelector": { "role": "mesh" },
  "tolerations": [
    { "key": "dedicated", "operator": "Equal", "value": "mesh", "effect": "NoSchedule" }
  ]
}

Canary upgrade and workload migration

When you start a Canary upgrade, the control plane of the new Revision is installed alongside the existing Revision. Workloads continue to use the Revision specified in the namespace's istio.io/rev label. If you change the label to the new Revision and restart the workloads, the restarted pods run with sidecars of the new Revision. Migrate namespaces sequentially, starting with those that have the smallest impact, and verify that they work properly.

# Switch the namespace to the new revision (e.g., 1-30)
kubectl label namespace <namespace> istio.io/rev=1-30 --overwrite

# Restart workloads (the new revision applies starting with restarted pods)
kubectl rollout restart deployment -n <namespace>

If issues are found, revert the label to the existing Revision and restart the workloads again to return to the existing Revision.

For details on how Revision-based upgrades work, see Canary upgrades in the official Istio documentation.

Version compatibility

The add-on versions available for installation vary depending on the cluster's Kubernetes version. When installing or editing an add-on, only versions compatible with the cluster can be selected. For the supported versions of each add-on, see the version compatibility table in Add-on version.