Hi there! Are you looking for the official Deno documentation? Try docs.deno.com for all your Deno learning needs.

VmwareNodeConfig

import type { VmwareNodeConfig } from "https://googleapis.deno.dev/v1/gkeonprem:v1.ts";

Parameters that describe the configuration of all nodes within a given node pool.

interface VmwareNodeConfig {
bootDiskSizeGb?: bigint;
cpus?: bigint;
enableLoadBalancer?: boolean;
image?: string;
imageType?: string;
labels?: {
[key: string]: string;
}
;
memoryMb?: bigint;
replicas?: bigint;
taints?: NodeTaint[];
vsphereConfig?: VmwareVsphereConfig;
}

§Properties

§
bootDiskSizeGb?: bigint
[src]

VMware disk size to be used during creation.

§
cpus?: bigint
[src]

The number of CPUs for each node in the node pool.

§
enableLoadBalancer?: boolean
[src]

Allow node pool traffic to be load balanced. Only works for clusters with MetalLB load balancers.

§
image?: string
[src]

The OS image name in vCenter, only valid when using Windows.

§
imageType?: string
[src]

Required. The OS image to be used for each node in a node pool. Currently cos, cos_cgv2, ubuntu, ubuntu_cgv2, ubuntu_containerd and windows are supported.

§
labels?: {
[key: string]: string;
}
[src]

The map of Kubernetes labels (key/value pairs) to be applied to each node. These will added in addition to any default label(s) that Kubernetes may apply to the node. In case of conflict in label keys, the applied set may differ depending on the Kubernetes version -- it's best to assume the behavior is undefined and conflicts should be avoided. For more information, including usage and the valid values, see: https://kubernetes.io/docs/concepts/overview/working-with-objects/labels/

§
memoryMb?: bigint
[src]

The megabytes of memory for each node in the node pool.

§
replicas?: bigint
[src]

The number of nodes in the node pool.

§
taints?: NodeTaint[]
[src]

The initial taints assigned to nodes of this node pool.

§
vsphereConfig?: VmwareVsphereConfig
[src]

Specifies the vSphere config for node pool.