@nebius/js-sdk - v0.2.54
    Preparing search index...

    Interface ControlPlaneSpec

    Represents the nebius.mk8s.v1.ControlPlaneSpec protobuf message.

    interface ControlPlaneSpec {
        "[customJson]"?: () => unknown;
        "[unknownFieldsSymbol]"?: Uint8Array<ArrayBufferLike>;
        $type: "nebius.mk8s.v1.ControlPlaneSpec";
        auditLogs?: AuditLogsSpec;
        endpoints?: ControlPlaneEndpointsSpec;
        etcdClusterSize: Long;
        karpenter?: Karpenter;
        subnetId: string;
        version: string;
        [key: symbol]: Uint8Array<ArrayBufferLike> | (() => unknown) | undefined;
    }

    Indexable

    • [key: symbol]: Uint8Array<ArrayBufferLike> | (() => unknown) | undefined

      Represents the nebius.mk8s.v1.ControlPlaneSpec protobuf message.

      • Uint8Array<ArrayBufferLike>
      • () => unknown
          • (): unknown

          • Represents the nebius.mk8s.v1.ControlPlaneSpec protobuf message.

            Returns unknown

      • undefined
    Index
    [customJson]? [unknownFieldsSymbol]? $type auditLogs? endpoints? etcdClusterSize karpenter? subnetId version
    "[customJson]"?: () => unknown

    Returns a safe value for JSON logs.

    Type Declaration

      • (): unknown

      • Returns a safe value for JSON logs.

        Returns unknown

    "[unknownFieldsSymbol]"?: Uint8Array<ArrayBufferLike>

    Preserves protobuf fields that this SDK version does not recognize.

    $type: "nebius.mk8s.v1.ControlPlaneSpec"

    Contains the fully qualified protobuf type name.

    auditLogs?: AuditLogsSpec

    Specify configuration of the pushing k8s audit logs into service logs and show it in the UI. By default cluster will be created without it.

    endpoints?: ControlPlaneEndpointsSpec

    Specification of endpoints of cluster control plane.

    etcdClusterSize: Long

    Number of instances in etcd cluster. 3 by default. Control plane with etcd_cluster_size: 3 called "Highly Available" ("HA"), because it's Kubernetes API will be available despite a failure of one control plane instance.

    karpenter?: Karpenter

    Enables installation of the Karpenter inside a cluster. Karpenter will be installed as a helm chart inside cluster so it requires creation of at least one CPU public node group.

    Please note that there is no feature parity between Karpenter node pools and public node groups. By default cluster will be created without it.

    subnetId: string

    Nebius VPC Subnet ID where control plane instances will be located. Also will be default NodeGroup subnet.

    version: string

    Desired Kubernetes version of the cluster. May be lower than the actual cluster version if the desired version is no longer supported and the cluster has been automatically updated. For now only acceptable format is <major>.<minor> like "1.31". Option for patch version update will be added later.

    Settings
    Member Visibility

    On This Page
    Properties