@akamai/openapi-ts
    Preparing search index...

    Type Alias GetNodeBalancerVpcConfigResponses

    type GetNodeBalancerVpcConfigResponses = {
        "200": {
            id?: number;
            ipv4_range?: string;
            ipv4_range_auto_assign?: boolean | null;
            nodebalancer_id?: number;
            subnet_id: number;
            vpc_id?: number | null;
        };
    }
    Index

    Properties

    Properties

    "200": {
        id?: number;
        ipv4_range?: string;
        ipv4_range_auto_assign?: boolean | null;
        nodebalancer_id?: number;
        subnet_id: number;
        vpc_id?: number | null;
    }

    You can have only one VPC in a NodeBalancer configuration. If any of your backend nodes are VPC Linodes, specify the VPC subnet and CIDR range. NodeBalancer routes traffic to backend VPC nodes through this subnet. Once the NodeBalancer is created, its VPC cannot be changed.

    Type Declaration

    • Optional Readonlyid?: number

      Read-only Identifies the VPC configuration for this NodeBalancer.

    • Optionalipv4_range?: string

      A CIDR range for the VPC's IPv4 addresses. The NodeBalancer sources IP addresses from this range when routing traffic to the backend VPC nodes.

    • Optionalipv4_range_auto_assign?: boolean | null

      Enables the use of a larger ipv4_range subnet for multiple NodeBalancers within the same VPC by allocating smaller /30 subnets for each NodeBalancer's backends.

      • When set to true, the system automatically allocates the smallest possible subnet (/30) from the provided ipv4_range for the NodeBalancer's backend interface. If the specified range doesn't have enough available IPs to allocate a /30 subnet, the creation fails.

      • When set to false, the NodeBalancer is created using the entire ipv4_range as specified, without attempting to allocate a /30 subnet.

    • Optional Readonlynodebalancer_id?: number

      Read-only Identifies the NodeBalancer.

    • subnet_id: number

      The VPC's subnet. Run the List VPCs operation provides data for your VPCs and their subnets.

    • Optional Readonlyvpc_id?: number | null

      Read-only The id of the VPC configured for this NodeBalancer.