Kubernetes Engine V1 API - Module Google::Cloud::Container::V1::AdditionalIPRangesConfig::Status (v1.12.0)

Version latest

• 1.12.0 (latest)
• 1.11.1
• 1.10.1
• 1.9.0
• 1.8.0
• 1.7.0
• 1.6.1
• 1.5.0
• 1.4.0
• 1.3.0
• 1.2.0
• 1.1.1
• 1.0.0
• 0.42.0
• 0.41.0
• 0.40.0
• 0.39.0
• 0.38.0
• 0.37.0
• 0.36.0
• 0.35.0
• 0.34.1
• 0.33.1
• 0.32.0
• 0.31.0
• 0.30.0
• 0.29.0
• 0.28.0
• 0.27.0
• 0.26.0
• 0.25.0
• 0.24.0
• 0.23.0
• 0.22.0
• 0.21.1
• 0.20.0
• 0.19.0
• 0.18.0
• 0.17.0
• 0.16.3
• 0.15.0
• 0.14.0
• 0.13.0
• 0.12.0
• 0.11.0
• 0.10.0
• 0.9.1
• 0.8.0
• 0.7.3

Reference documentation and code samples for the Kubernetes Engine V1 API module Google::Cloud::Container::V1::AdditionalIPRangesConfig::Status.

Additional subnet with DRAINING status will not be selected during new node pool creation. To undrain the draining status, update the cluster to set the sunbet to ACTIVE status. To remove the additional subnet, use the update cluster API to remove the subnet from the desired_additional_ip_ranges list. IP ranges can be removed regardless of its status, as long as no node pools are using them.

Constants

STATUS_UNSPECIFIED

value: 0
Not set, same as ACTIVE.

ACTIVE

value: 1
ACTIVE status indicates that the subnet is available for new node pool creation.

DRAINING

value: 2
DRAINING status indicates that the subnet is not used for new node pool creation.