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

    Interface NodeMetadataTemplate

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

    interface NodeMetadataTemplate {
        "[customJson]"?: () => unknown;
        "[unknownFieldsSymbol]"?: Uint8Array<ArrayBufferLike>;
        $type: "nebius.mk8s.v1.NodeMetadataTemplate";
        labels: { [key: string]: string };
        [key: symbol]: Uint8Array<ArrayBufferLike> | (() => unknown) | undefined;
    }

    Indexable

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

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

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

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

            Returns unknown

      • undefined
    Index
    [customJson]? [unknownFieldsSymbol]? $type labels
    "[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.NodeMetadataTemplate"

    Contains the fully qualified protobuf type name.

    labels: { [key: string]: string }

    Kubernetes Node labels.

    Keys and values must follow Kubernetes label syntax: https://kubernetes.io/docs/concepts/overview/working-with-objects/labels/

    For now change will not be propagated to existing nodes, so will be applied only to Kubernetes Nodes created after the field change. That behavior may change later. So, for now you will need to manually set them to existing nodes, if that is needed.

    System labels containing "kubernetes.io" and "k8s.io" will be ignored. Field change will NOT trigger NodeGroup roll out.

    Type Declaration

    • [key: string]: string

      Kubernetes Node labels.

      Keys and values must follow Kubernetes label syntax: https://kubernetes.io/docs/concepts/overview/working-with-objects/labels/

      For now change will not be propagated to existing nodes, so will be applied only to Kubernetes Nodes created after the field change. That behavior may change later. So, for now you will need to manually set them to existing nodes, if that is needed.

      System labels containing "kubernetes.io" and "k8s.io" will be ignored. Field change will NOT trigger NodeGroup roll out.

    Settings
    Member Visibility

    On This Page
    Properties