Class: Google::Cloud::Container::V1::NodePool
- Inherits:
-
Object
- Object
- Google::Cloud::Container::V1::NodePool
- Extended by:
- Protobuf::MessageExts::ClassMethods
- Includes:
- Protobuf::MessageExts
- Defined in:
- proto_docs/google/container/v1/cluster_service.rb
Overview
NodePool contains the name and configuration for a cluster's node pool. Node pools are a set of nodes (i.e. VM's), with a common configuration and specification, under the control of the cluster master. They may have a set of Kubernetes labels applied to them, which may be used to reference them during pod scheduling. They may also be resized up or down, to accommodate the workload.
Defined Under Namespace
Modules: Status Classes: UpgradeSettings
Instance Attribute Summary collapse
-
#autoscaling ⇒ ::Google::Cloud::Container::V1::NodePoolAutoscaling
Autoscaler configuration for this NodePool.
-
#conditions ⇒ ::Array<::Google::Cloud::Container::V1::StatusCondition>
Which conditions caused the current node pool state.
-
#config ⇒ ::Google::Cloud::Container::V1::NodeConfig
The node configuration of the pool.
-
#initial_node_count ⇒ ::Integer
The initial node count for the pool.
-
#instance_group_urls ⇒ ::Array<::String>
[Output only] The resource URLs of the managed instance groups associated with this node pool.
-
#locations ⇒ ::Array<::String>
The list of Google Compute Engine zones in which the NodePool's nodes should be located.
-
#management ⇒ ::Google::Cloud::Container::V1::NodeManagement
NodeManagement configuration for this NodePool.
-
#max_pods_constraint ⇒ ::Google::Cloud::Container::V1::MaxPodsConstraint
The constraint on the maximum number of pods that can be run simultaneously on a node in the node pool.
-
#name ⇒ ::String
The name of the node pool.
-
#pod_ipv4_cidr_size ⇒ ::Integer
[Output only] The pod CIDR block size per node in this node pool.
-
#self_link ⇒ ::String
[Output only] Server-defined URL for the resource.
-
#status ⇒ ::Google::Cloud::Container::V1::NodePool::Status
[Output only] The status of the nodes in this pool instance.
-
#status_message ⇒ ::String
[Output only] Deprecated.
-
#upgrade_settings ⇒ ::Google::Cloud::Container::V1::NodePool::UpgradeSettings
Upgrade settings control disruption and speed of the upgrade.
-
#version ⇒ ::String
The version of the Kubernetes of this node.
Instance Attribute Details
#autoscaling ⇒ ::Google::Cloud::Container::V1::NodePoolAutoscaling
Returns Autoscaler configuration for this NodePool. Autoscaler is enabled only if a valid configuration is present.
2143 2144 2145 2146 2147 2148 2149 2150 2151 2152 2153 2154 2155 2156 2157 2158 2159 2160 2161 2162 2163 2164 2165 2166 2167 2168 2169 2170 2171 2172 2173 2174 2175 2176 2177 2178 2179 2180 2181 2182 2183 2184 2185 2186 2187 2188 2189 2190 2191 2192 2193 2194 2195 2196 2197 2198 2199 2200 2201 2202 2203 2204 2205 2206 2207 2208 2209 2210 2211 2212 2213 2214 |
# File 'proto_docs/google/container/v1/cluster_service.rb', line 2143 class NodePool include ::Google::Protobuf::MessageExts extend ::Google::Protobuf::MessageExts::ClassMethods # These upgrade settings control the level of parallelism and the level of # disruption caused by an upgrade. # # maxUnavailable controls the number of nodes that can be simultaneously # unavailable. # # maxSurge controls the number of additional nodes that can be added to the # node pool temporarily for the time of the upgrade to increase the number of # available nodes. # # (maxUnavailable + maxSurge) determines the level of parallelism (how many # nodes are being upgraded at the same time). # # Note: upgrades inevitably introduce some disruption since workloads need to # be moved from old nodes to new, upgraded ones. Even if maxUnavailable=0, # this holds true. (Disruption stays within the limits of # PodDisruptionBudget, if it is configured.) # # Consider a hypothetical node pool with 5 nodes having maxSurge=2, # maxUnavailable=1. This means the upgrade process upgrades 3 nodes # simultaneously. It creates 2 additional (upgraded) nodes, then it brings # down 3 old (not yet upgraded) nodes at the same time. This ensures that # there are always at least 4 nodes available. # @!attribute [rw] max_surge # @return [::Integer] # The maximum number of nodes that can be created beyond the current size # of the node pool during the upgrade process. # @!attribute [rw] max_unavailable # @return [::Integer] # The maximum number of nodes that can be simultaneously unavailable during # the upgrade process. A node is considered available if its status is # Ready. class UpgradeSettings include ::Google::Protobuf::MessageExts extend ::Google::Protobuf::MessageExts::ClassMethods end # The current status of the node pool instance. module Status # Not set. STATUS_UNSPECIFIED = 0 # The PROVISIONING state indicates the node pool is being created. PROVISIONING = 1 # The RUNNING state indicates the node pool has been created # and is fully usable. RUNNING = 2 # The RUNNING_WITH_ERROR state indicates the node pool has been created # and is partially usable. Some error state has occurred and some # functionality may be impaired. Customer may need to reissue a request # or trigger a new update. RUNNING_WITH_ERROR = 3 # The RECONCILING state indicates that some work is actively being done on # the node pool, such as upgrading node software. Details can # be found in the `statusMessage` field. RECONCILING = 4 # The STOPPING state indicates the node pool is being deleted. STOPPING = 5 # The ERROR state indicates the node pool may be unusable. Details # can be found in the `statusMessage` field. ERROR = 6 end end |
#conditions ⇒ ::Array<::Google::Cloud::Container::V1::StatusCondition>
Returns Which conditions caused the current node pool state.
2143 2144 2145 2146 2147 2148 2149 2150 2151 2152 2153 2154 2155 2156 2157 2158 2159 2160 2161 2162 2163 2164 2165 2166 2167 2168 2169 2170 2171 2172 2173 2174 2175 2176 2177 2178 2179 2180 2181 2182 2183 2184 2185 2186 2187 2188 2189 2190 2191 2192 2193 2194 2195 2196 2197 2198 2199 2200 2201 2202 2203 2204 2205 2206 2207 2208 2209 2210 2211 2212 2213 2214 |
# File 'proto_docs/google/container/v1/cluster_service.rb', line 2143 class NodePool include ::Google::Protobuf::MessageExts extend ::Google::Protobuf::MessageExts::ClassMethods # These upgrade settings control the level of parallelism and the level of # disruption caused by an upgrade. # # maxUnavailable controls the number of nodes that can be simultaneously # unavailable. # # maxSurge controls the number of additional nodes that can be added to the # node pool temporarily for the time of the upgrade to increase the number of # available nodes. # # (maxUnavailable + maxSurge) determines the level of parallelism (how many # nodes are being upgraded at the same time). # # Note: upgrades inevitably introduce some disruption since workloads need to # be moved from old nodes to new, upgraded ones. Even if maxUnavailable=0, # this holds true. (Disruption stays within the limits of # PodDisruptionBudget, if it is configured.) # # Consider a hypothetical node pool with 5 nodes having maxSurge=2, # maxUnavailable=1. This means the upgrade process upgrades 3 nodes # simultaneously. It creates 2 additional (upgraded) nodes, then it brings # down 3 old (not yet upgraded) nodes at the same time. This ensures that # there are always at least 4 nodes available. # @!attribute [rw] max_surge # @return [::Integer] # The maximum number of nodes that can be created beyond the current size # of the node pool during the upgrade process. # @!attribute [rw] max_unavailable # @return [::Integer] # The maximum number of nodes that can be simultaneously unavailable during # the upgrade process. A node is considered available if its status is # Ready. class UpgradeSettings include ::Google::Protobuf::MessageExts extend ::Google::Protobuf::MessageExts::ClassMethods end # The current status of the node pool instance. module Status # Not set. STATUS_UNSPECIFIED = 0 # The PROVISIONING state indicates the node pool is being created. PROVISIONING = 1 # The RUNNING state indicates the node pool has been created # and is fully usable. RUNNING = 2 # The RUNNING_WITH_ERROR state indicates the node pool has been created # and is partially usable. Some error state has occurred and some # functionality may be impaired. Customer may need to reissue a request # or trigger a new update. RUNNING_WITH_ERROR = 3 # The RECONCILING state indicates that some work is actively being done on # the node pool, such as upgrading node software. Details can # be found in the `statusMessage` field. RECONCILING = 4 # The STOPPING state indicates the node pool is being deleted. STOPPING = 5 # The ERROR state indicates the node pool may be unusable. Details # can be found in the `statusMessage` field. ERROR = 6 end end |
#config ⇒ ::Google::Cloud::Container::V1::NodeConfig
Returns The node configuration of the pool.
2143 2144 2145 2146 2147 2148 2149 2150 2151 2152 2153 2154 2155 2156 2157 2158 2159 2160 2161 2162 2163 2164 2165 2166 2167 2168 2169 2170 2171 2172 2173 2174 2175 2176 2177 2178 2179 2180 2181 2182 2183 2184 2185 2186 2187 2188 2189 2190 2191 2192 2193 2194 2195 2196 2197 2198 2199 2200 2201 2202 2203 2204 2205 2206 2207 2208 2209 2210 2211 2212 2213 2214 |
# File 'proto_docs/google/container/v1/cluster_service.rb', line 2143 class NodePool include ::Google::Protobuf::MessageExts extend ::Google::Protobuf::MessageExts::ClassMethods # These upgrade settings control the level of parallelism and the level of # disruption caused by an upgrade. # # maxUnavailable controls the number of nodes that can be simultaneously # unavailable. # # maxSurge controls the number of additional nodes that can be added to the # node pool temporarily for the time of the upgrade to increase the number of # available nodes. # # (maxUnavailable + maxSurge) determines the level of parallelism (how many # nodes are being upgraded at the same time). # # Note: upgrades inevitably introduce some disruption since workloads need to # be moved from old nodes to new, upgraded ones. Even if maxUnavailable=0, # this holds true. (Disruption stays within the limits of # PodDisruptionBudget, if it is configured.) # # Consider a hypothetical node pool with 5 nodes having maxSurge=2, # maxUnavailable=1. This means the upgrade process upgrades 3 nodes # simultaneously. It creates 2 additional (upgraded) nodes, then it brings # down 3 old (not yet upgraded) nodes at the same time. This ensures that # there are always at least 4 nodes available. # @!attribute [rw] max_surge # @return [::Integer] # The maximum number of nodes that can be created beyond the current size # of the node pool during the upgrade process. # @!attribute [rw] max_unavailable # @return [::Integer] # The maximum number of nodes that can be simultaneously unavailable during # the upgrade process. A node is considered available if its status is # Ready. class UpgradeSettings include ::Google::Protobuf::MessageExts extend ::Google::Protobuf::MessageExts::ClassMethods end # The current status of the node pool instance. module Status # Not set. STATUS_UNSPECIFIED = 0 # The PROVISIONING state indicates the node pool is being created. PROVISIONING = 1 # The RUNNING state indicates the node pool has been created # and is fully usable. RUNNING = 2 # The RUNNING_WITH_ERROR state indicates the node pool has been created # and is partially usable. Some error state has occurred and some # functionality may be impaired. Customer may need to reissue a request # or trigger a new update. RUNNING_WITH_ERROR = 3 # The RECONCILING state indicates that some work is actively being done on # the node pool, such as upgrading node software. Details can # be found in the `statusMessage` field. RECONCILING = 4 # The STOPPING state indicates the node pool is being deleted. STOPPING = 5 # The ERROR state indicates the node pool may be unusable. Details # can be found in the `statusMessage` field. ERROR = 6 end end |
#initial_node_count ⇒ ::Integer
Returns The initial node count for the pool. You must ensure that your Compute Engine resource quota is sufficient for this number of instances. You must also have available firewall and routes quota.
2143 2144 2145 2146 2147 2148 2149 2150 2151 2152 2153 2154 2155 2156 2157 2158 2159 2160 2161 2162 2163 2164 2165 2166 2167 2168 2169 2170 2171 2172 2173 2174 2175 2176 2177 2178 2179 2180 2181 2182 2183 2184 2185 2186 2187 2188 2189 2190 2191 2192 2193 2194 2195 2196 2197 2198 2199 2200 2201 2202 2203 2204 2205 2206 2207 2208 2209 2210 2211 2212 2213 2214 |
# File 'proto_docs/google/container/v1/cluster_service.rb', line 2143 class NodePool include ::Google::Protobuf::MessageExts extend ::Google::Protobuf::MessageExts::ClassMethods # These upgrade settings control the level of parallelism and the level of # disruption caused by an upgrade. # # maxUnavailable controls the number of nodes that can be simultaneously # unavailable. # # maxSurge controls the number of additional nodes that can be added to the # node pool temporarily for the time of the upgrade to increase the number of # available nodes. # # (maxUnavailable + maxSurge) determines the level of parallelism (how many # nodes are being upgraded at the same time). # # Note: upgrades inevitably introduce some disruption since workloads need to # be moved from old nodes to new, upgraded ones. Even if maxUnavailable=0, # this holds true. (Disruption stays within the limits of # PodDisruptionBudget, if it is configured.) # # Consider a hypothetical node pool with 5 nodes having maxSurge=2, # maxUnavailable=1. This means the upgrade process upgrades 3 nodes # simultaneously. It creates 2 additional (upgraded) nodes, then it brings # down 3 old (not yet upgraded) nodes at the same time. This ensures that # there are always at least 4 nodes available. # @!attribute [rw] max_surge # @return [::Integer] # The maximum number of nodes that can be created beyond the current size # of the node pool during the upgrade process. # @!attribute [rw] max_unavailable # @return [::Integer] # The maximum number of nodes that can be simultaneously unavailable during # the upgrade process. A node is considered available if its status is # Ready. class UpgradeSettings include ::Google::Protobuf::MessageExts extend ::Google::Protobuf::MessageExts::ClassMethods end # The current status of the node pool instance. module Status # Not set. STATUS_UNSPECIFIED = 0 # The PROVISIONING state indicates the node pool is being created. PROVISIONING = 1 # The RUNNING state indicates the node pool has been created # and is fully usable. RUNNING = 2 # The RUNNING_WITH_ERROR state indicates the node pool has been created # and is partially usable. Some error state has occurred and some # functionality may be impaired. Customer may need to reissue a request # or trigger a new update. RUNNING_WITH_ERROR = 3 # The RECONCILING state indicates that some work is actively being done on # the node pool, such as upgrading node software. Details can # be found in the `statusMessage` field. RECONCILING = 4 # The STOPPING state indicates the node pool is being deleted. STOPPING = 5 # The ERROR state indicates the node pool may be unusable. Details # can be found in the `statusMessage` field. ERROR = 6 end end |
#instance_group_urls ⇒ ::Array<::String>
Returns [Output only] The resource URLs of the managed instance groups associated with this node pool.
2143 2144 2145 2146 2147 2148 2149 2150 2151 2152 2153 2154 2155 2156 2157 2158 2159 2160 2161 2162 2163 2164 2165 2166 2167 2168 2169 2170 2171 2172 2173 2174 2175 2176 2177 2178 2179 2180 2181 2182 2183 2184 2185 2186 2187 2188 2189 2190 2191 2192 2193 2194 2195 2196 2197 2198 2199 2200 2201 2202 2203 2204 2205 2206 2207 2208 2209 2210 2211 2212 2213 2214 |
# File 'proto_docs/google/container/v1/cluster_service.rb', line 2143 class NodePool include ::Google::Protobuf::MessageExts extend ::Google::Protobuf::MessageExts::ClassMethods # These upgrade settings control the level of parallelism and the level of # disruption caused by an upgrade. # # maxUnavailable controls the number of nodes that can be simultaneously # unavailable. # # maxSurge controls the number of additional nodes that can be added to the # node pool temporarily for the time of the upgrade to increase the number of # available nodes. # # (maxUnavailable + maxSurge) determines the level of parallelism (how many # nodes are being upgraded at the same time). # # Note: upgrades inevitably introduce some disruption since workloads need to # be moved from old nodes to new, upgraded ones. Even if maxUnavailable=0, # this holds true. (Disruption stays within the limits of # PodDisruptionBudget, if it is configured.) # # Consider a hypothetical node pool with 5 nodes having maxSurge=2, # maxUnavailable=1. This means the upgrade process upgrades 3 nodes # simultaneously. It creates 2 additional (upgraded) nodes, then it brings # down 3 old (not yet upgraded) nodes at the same time. This ensures that # there are always at least 4 nodes available. # @!attribute [rw] max_surge # @return [::Integer] # The maximum number of nodes that can be created beyond the current size # of the node pool during the upgrade process. # @!attribute [rw] max_unavailable # @return [::Integer] # The maximum number of nodes that can be simultaneously unavailable during # the upgrade process. A node is considered available if its status is # Ready. class UpgradeSettings include ::Google::Protobuf::MessageExts extend ::Google::Protobuf::MessageExts::ClassMethods end # The current status of the node pool instance. module Status # Not set. STATUS_UNSPECIFIED = 0 # The PROVISIONING state indicates the node pool is being created. PROVISIONING = 1 # The RUNNING state indicates the node pool has been created # and is fully usable. RUNNING = 2 # The RUNNING_WITH_ERROR state indicates the node pool has been created # and is partially usable. Some error state has occurred and some # functionality may be impaired. Customer may need to reissue a request # or trigger a new update. RUNNING_WITH_ERROR = 3 # The RECONCILING state indicates that some work is actively being done on # the node pool, such as upgrading node software. Details can # be found in the `statusMessage` field. RECONCILING = 4 # The STOPPING state indicates the node pool is being deleted. STOPPING = 5 # The ERROR state indicates the node pool may be unusable. Details # can be found in the `statusMessage` field. ERROR = 6 end end |
#locations ⇒ ::Array<::String>
Returns The list of Google Compute Engine zones in which the NodePool's nodes should be located.
If this value is unspecified during node pool creation, the Cluster.Locations value will be used, instead.
Warning: changing node pool locations will result in nodes being added and/or removed.
2143 2144 2145 2146 2147 2148 2149 2150 2151 2152 2153 2154 2155 2156 2157 2158 2159 2160 2161 2162 2163 2164 2165 2166 2167 2168 2169 2170 2171 2172 2173 2174 2175 2176 2177 2178 2179 2180 2181 2182 2183 2184 2185 2186 2187 2188 2189 2190 2191 2192 2193 2194 2195 2196 2197 2198 2199 2200 2201 2202 2203 2204 2205 2206 2207 2208 2209 2210 2211 2212 2213 2214 |
# File 'proto_docs/google/container/v1/cluster_service.rb', line 2143 class NodePool include ::Google::Protobuf::MessageExts extend ::Google::Protobuf::MessageExts::ClassMethods # These upgrade settings control the level of parallelism and the level of # disruption caused by an upgrade. # # maxUnavailable controls the number of nodes that can be simultaneously # unavailable. # # maxSurge controls the number of additional nodes that can be added to the # node pool temporarily for the time of the upgrade to increase the number of # available nodes. # # (maxUnavailable + maxSurge) determines the level of parallelism (how many # nodes are being upgraded at the same time). # # Note: upgrades inevitably introduce some disruption since workloads need to # be moved from old nodes to new, upgraded ones. Even if maxUnavailable=0, # this holds true. (Disruption stays within the limits of # PodDisruptionBudget, if it is configured.) # # Consider a hypothetical node pool with 5 nodes having maxSurge=2, # maxUnavailable=1. This means the upgrade process upgrades 3 nodes # simultaneously. It creates 2 additional (upgraded) nodes, then it brings # down 3 old (not yet upgraded) nodes at the same time. This ensures that # there are always at least 4 nodes available. # @!attribute [rw] max_surge # @return [::Integer] # The maximum number of nodes that can be created beyond the current size # of the node pool during the upgrade process. # @!attribute [rw] max_unavailable # @return [::Integer] # The maximum number of nodes that can be simultaneously unavailable during # the upgrade process. A node is considered available if its status is # Ready. class UpgradeSettings include ::Google::Protobuf::MessageExts extend ::Google::Protobuf::MessageExts::ClassMethods end # The current status of the node pool instance. module Status # Not set. STATUS_UNSPECIFIED = 0 # The PROVISIONING state indicates the node pool is being created. PROVISIONING = 1 # The RUNNING state indicates the node pool has been created # and is fully usable. RUNNING = 2 # The RUNNING_WITH_ERROR state indicates the node pool has been created # and is partially usable. Some error state has occurred and some # functionality may be impaired. Customer may need to reissue a request # or trigger a new update. RUNNING_WITH_ERROR = 3 # The RECONCILING state indicates that some work is actively being done on # the node pool, such as upgrading node software. Details can # be found in the `statusMessage` field. RECONCILING = 4 # The STOPPING state indicates the node pool is being deleted. STOPPING = 5 # The ERROR state indicates the node pool may be unusable. Details # can be found in the `statusMessage` field. ERROR = 6 end end |
#management ⇒ ::Google::Cloud::Container::V1::NodeManagement
Returns NodeManagement configuration for this NodePool.
2143 2144 2145 2146 2147 2148 2149 2150 2151 2152 2153 2154 2155 2156 2157 2158 2159 2160 2161 2162 2163 2164 2165 2166 2167 2168 2169 2170 2171 2172 2173 2174 2175 2176 2177 2178 2179 2180 2181 2182 2183 2184 2185 2186 2187 2188 2189 2190 2191 2192 2193 2194 2195 2196 2197 2198 2199 2200 2201 2202 2203 2204 2205 2206 2207 2208 2209 2210 2211 2212 2213 2214 |
# File 'proto_docs/google/container/v1/cluster_service.rb', line 2143 class NodePool include ::Google::Protobuf::MessageExts extend ::Google::Protobuf::MessageExts::ClassMethods # These upgrade settings control the level of parallelism and the level of # disruption caused by an upgrade. # # maxUnavailable controls the number of nodes that can be simultaneously # unavailable. # # maxSurge controls the number of additional nodes that can be added to the # node pool temporarily for the time of the upgrade to increase the number of # available nodes. # # (maxUnavailable + maxSurge) determines the level of parallelism (how many # nodes are being upgraded at the same time). # # Note: upgrades inevitably introduce some disruption since workloads need to # be moved from old nodes to new, upgraded ones. Even if maxUnavailable=0, # this holds true. (Disruption stays within the limits of # PodDisruptionBudget, if it is configured.) # # Consider a hypothetical node pool with 5 nodes having maxSurge=2, # maxUnavailable=1. This means the upgrade process upgrades 3 nodes # simultaneously. It creates 2 additional (upgraded) nodes, then it brings # down 3 old (not yet upgraded) nodes at the same time. This ensures that # there are always at least 4 nodes available. # @!attribute [rw] max_surge # @return [::Integer] # The maximum number of nodes that can be created beyond the current size # of the node pool during the upgrade process. # @!attribute [rw] max_unavailable # @return [::Integer] # The maximum number of nodes that can be simultaneously unavailable during # the upgrade process. A node is considered available if its status is # Ready. class UpgradeSettings include ::Google::Protobuf::MessageExts extend ::Google::Protobuf::MessageExts::ClassMethods end # The current status of the node pool instance. module Status # Not set. STATUS_UNSPECIFIED = 0 # The PROVISIONING state indicates the node pool is being created. PROVISIONING = 1 # The RUNNING state indicates the node pool has been created # and is fully usable. RUNNING = 2 # The RUNNING_WITH_ERROR state indicates the node pool has been created # and is partially usable. Some error state has occurred and some # functionality may be impaired. Customer may need to reissue a request # or trigger a new update. RUNNING_WITH_ERROR = 3 # The RECONCILING state indicates that some work is actively being done on # the node pool, such as upgrading node software. Details can # be found in the `statusMessage` field. RECONCILING = 4 # The STOPPING state indicates the node pool is being deleted. STOPPING = 5 # The ERROR state indicates the node pool may be unusable. Details # can be found in the `statusMessage` field. ERROR = 6 end end |
#max_pods_constraint ⇒ ::Google::Cloud::Container::V1::MaxPodsConstraint
Returns The constraint on the maximum number of pods that can be run simultaneously on a node in the node pool.
2143 2144 2145 2146 2147 2148 2149 2150 2151 2152 2153 2154 2155 2156 2157 2158 2159 2160 2161 2162 2163 2164 2165 2166 2167 2168 2169 2170 2171 2172 2173 2174 2175 2176 2177 2178 2179 2180 2181 2182 2183 2184 2185 2186 2187 2188 2189 2190 2191 2192 2193 2194 2195 2196 2197 2198 2199 2200 2201 2202 2203 2204 2205 2206 2207 2208 2209 2210 2211 2212 2213 2214 |
# File 'proto_docs/google/container/v1/cluster_service.rb', line 2143 class NodePool include ::Google::Protobuf::MessageExts extend ::Google::Protobuf::MessageExts::ClassMethods # These upgrade settings control the level of parallelism and the level of # disruption caused by an upgrade. # # maxUnavailable controls the number of nodes that can be simultaneously # unavailable. # # maxSurge controls the number of additional nodes that can be added to the # node pool temporarily for the time of the upgrade to increase the number of # available nodes. # # (maxUnavailable + maxSurge) determines the level of parallelism (how many # nodes are being upgraded at the same time). # # Note: upgrades inevitably introduce some disruption since workloads need to # be moved from old nodes to new, upgraded ones. Even if maxUnavailable=0, # this holds true. (Disruption stays within the limits of # PodDisruptionBudget, if it is configured.) # # Consider a hypothetical node pool with 5 nodes having maxSurge=2, # maxUnavailable=1. This means the upgrade process upgrades 3 nodes # simultaneously. It creates 2 additional (upgraded) nodes, then it brings # down 3 old (not yet upgraded) nodes at the same time. This ensures that # there are always at least 4 nodes available. # @!attribute [rw] max_surge # @return [::Integer] # The maximum number of nodes that can be created beyond the current size # of the node pool during the upgrade process. # @!attribute [rw] max_unavailable # @return [::Integer] # The maximum number of nodes that can be simultaneously unavailable during # the upgrade process. A node is considered available if its status is # Ready. class UpgradeSettings include ::Google::Protobuf::MessageExts extend ::Google::Protobuf::MessageExts::ClassMethods end # The current status of the node pool instance. module Status # Not set. STATUS_UNSPECIFIED = 0 # The PROVISIONING state indicates the node pool is being created. PROVISIONING = 1 # The RUNNING state indicates the node pool has been created # and is fully usable. RUNNING = 2 # The RUNNING_WITH_ERROR state indicates the node pool has been created # and is partially usable. Some error state has occurred and some # functionality may be impaired. Customer may need to reissue a request # or trigger a new update. RUNNING_WITH_ERROR = 3 # The RECONCILING state indicates that some work is actively being done on # the node pool, such as upgrading node software. Details can # be found in the `statusMessage` field. RECONCILING = 4 # The STOPPING state indicates the node pool is being deleted. STOPPING = 5 # The ERROR state indicates the node pool may be unusable. Details # can be found in the `statusMessage` field. ERROR = 6 end end |
#name ⇒ ::String
Returns The name of the node pool.
2143 2144 2145 2146 2147 2148 2149 2150 2151 2152 2153 2154 2155 2156 2157 2158 2159 2160 2161 2162 2163 2164 2165 2166 2167 2168 2169 2170 2171 2172 2173 2174 2175 2176 2177 2178 2179 2180 2181 2182 2183 2184 2185 2186 2187 2188 2189 2190 2191 2192 2193 2194 2195 2196 2197 2198 2199 2200 2201 2202 2203 2204 2205 2206 2207 2208 2209 2210 2211 2212 2213 2214 |
# File 'proto_docs/google/container/v1/cluster_service.rb', line 2143 class NodePool include ::Google::Protobuf::MessageExts extend ::Google::Protobuf::MessageExts::ClassMethods # These upgrade settings control the level of parallelism and the level of # disruption caused by an upgrade. # # maxUnavailable controls the number of nodes that can be simultaneously # unavailable. # # maxSurge controls the number of additional nodes that can be added to the # node pool temporarily for the time of the upgrade to increase the number of # available nodes. # # (maxUnavailable + maxSurge) determines the level of parallelism (how many # nodes are being upgraded at the same time). # # Note: upgrades inevitably introduce some disruption since workloads need to # be moved from old nodes to new, upgraded ones. Even if maxUnavailable=0, # this holds true. (Disruption stays within the limits of # PodDisruptionBudget, if it is configured.) # # Consider a hypothetical node pool with 5 nodes having maxSurge=2, # maxUnavailable=1. This means the upgrade process upgrades 3 nodes # simultaneously. It creates 2 additional (upgraded) nodes, then it brings # down 3 old (not yet upgraded) nodes at the same time. This ensures that # there are always at least 4 nodes available. # @!attribute [rw] max_surge # @return [::Integer] # The maximum number of nodes that can be created beyond the current size # of the node pool during the upgrade process. # @!attribute [rw] max_unavailable # @return [::Integer] # The maximum number of nodes that can be simultaneously unavailable during # the upgrade process. A node is considered available if its status is # Ready. class UpgradeSettings include ::Google::Protobuf::MessageExts extend ::Google::Protobuf::MessageExts::ClassMethods end # The current status of the node pool instance. module Status # Not set. STATUS_UNSPECIFIED = 0 # The PROVISIONING state indicates the node pool is being created. PROVISIONING = 1 # The RUNNING state indicates the node pool has been created # and is fully usable. RUNNING = 2 # The RUNNING_WITH_ERROR state indicates the node pool has been created # and is partially usable. Some error state has occurred and some # functionality may be impaired. Customer may need to reissue a request # or trigger a new update. RUNNING_WITH_ERROR = 3 # The RECONCILING state indicates that some work is actively being done on # the node pool, such as upgrading node software. Details can # be found in the `statusMessage` field. RECONCILING = 4 # The STOPPING state indicates the node pool is being deleted. STOPPING = 5 # The ERROR state indicates the node pool may be unusable. Details # can be found in the `statusMessage` field. ERROR = 6 end end |
#pod_ipv4_cidr_size ⇒ ::Integer
Returns [Output only] The pod CIDR block size per node in this node pool.
2143 2144 2145 2146 2147 2148 2149 2150 2151 2152 2153 2154 2155 2156 2157 2158 2159 2160 2161 2162 2163 2164 2165 2166 2167 2168 2169 2170 2171 2172 2173 2174 2175 2176 2177 2178 2179 2180 2181 2182 2183 2184 2185 2186 2187 2188 2189 2190 2191 2192 2193 2194 2195 2196 2197 2198 2199 2200 2201 2202 2203 2204 2205 2206 2207 2208 2209 2210 2211 2212 2213 2214 |
# File 'proto_docs/google/container/v1/cluster_service.rb', line 2143 class NodePool include ::Google::Protobuf::MessageExts extend ::Google::Protobuf::MessageExts::ClassMethods # These upgrade settings control the level of parallelism and the level of # disruption caused by an upgrade. # # maxUnavailable controls the number of nodes that can be simultaneously # unavailable. # # maxSurge controls the number of additional nodes that can be added to the # node pool temporarily for the time of the upgrade to increase the number of # available nodes. # # (maxUnavailable + maxSurge) determines the level of parallelism (how many # nodes are being upgraded at the same time). # # Note: upgrades inevitably introduce some disruption since workloads need to # be moved from old nodes to new, upgraded ones. Even if maxUnavailable=0, # this holds true. (Disruption stays within the limits of # PodDisruptionBudget, if it is configured.) # # Consider a hypothetical node pool with 5 nodes having maxSurge=2, # maxUnavailable=1. This means the upgrade process upgrades 3 nodes # simultaneously. It creates 2 additional (upgraded) nodes, then it brings # down 3 old (not yet upgraded) nodes at the same time. This ensures that # there are always at least 4 nodes available. # @!attribute [rw] max_surge # @return [::Integer] # The maximum number of nodes that can be created beyond the current size # of the node pool during the upgrade process. # @!attribute [rw] max_unavailable # @return [::Integer] # The maximum number of nodes that can be simultaneously unavailable during # the upgrade process. A node is considered available if its status is # Ready. class UpgradeSettings include ::Google::Protobuf::MessageExts extend ::Google::Protobuf::MessageExts::ClassMethods end # The current status of the node pool instance. module Status # Not set. STATUS_UNSPECIFIED = 0 # The PROVISIONING state indicates the node pool is being created. PROVISIONING = 1 # The RUNNING state indicates the node pool has been created # and is fully usable. RUNNING = 2 # The RUNNING_WITH_ERROR state indicates the node pool has been created # and is partially usable. Some error state has occurred and some # functionality may be impaired. Customer may need to reissue a request # or trigger a new update. RUNNING_WITH_ERROR = 3 # The RECONCILING state indicates that some work is actively being done on # the node pool, such as upgrading node software. Details can # be found in the `statusMessage` field. RECONCILING = 4 # The STOPPING state indicates the node pool is being deleted. STOPPING = 5 # The ERROR state indicates the node pool may be unusable. Details # can be found in the `statusMessage` field. ERROR = 6 end end |
#self_link ⇒ ::String
Returns [Output only] Server-defined URL for the resource.
2143 2144 2145 2146 2147 2148 2149 2150 2151 2152 2153 2154 2155 2156 2157 2158 2159 2160 2161 2162 2163 2164 2165 2166 2167 2168 2169 2170 2171 2172 2173 2174 2175 2176 2177 2178 2179 2180 2181 2182 2183 2184 2185 2186 2187 2188 2189 2190 2191 2192 2193 2194 2195 2196 2197 2198 2199 2200 2201 2202 2203 2204 2205 2206 2207 2208 2209 2210 2211 2212 2213 2214 |
# File 'proto_docs/google/container/v1/cluster_service.rb', line 2143 class NodePool include ::Google::Protobuf::MessageExts extend ::Google::Protobuf::MessageExts::ClassMethods # These upgrade settings control the level of parallelism and the level of # disruption caused by an upgrade. # # maxUnavailable controls the number of nodes that can be simultaneously # unavailable. # # maxSurge controls the number of additional nodes that can be added to the # node pool temporarily for the time of the upgrade to increase the number of # available nodes. # # (maxUnavailable + maxSurge) determines the level of parallelism (how many # nodes are being upgraded at the same time). # # Note: upgrades inevitably introduce some disruption since workloads need to # be moved from old nodes to new, upgraded ones. Even if maxUnavailable=0, # this holds true. (Disruption stays within the limits of # PodDisruptionBudget, if it is configured.) # # Consider a hypothetical node pool with 5 nodes having maxSurge=2, # maxUnavailable=1. This means the upgrade process upgrades 3 nodes # simultaneously. It creates 2 additional (upgraded) nodes, then it brings # down 3 old (not yet upgraded) nodes at the same time. This ensures that # there are always at least 4 nodes available. # @!attribute [rw] max_surge # @return [::Integer] # The maximum number of nodes that can be created beyond the current size # of the node pool during the upgrade process. # @!attribute [rw] max_unavailable # @return [::Integer] # The maximum number of nodes that can be simultaneously unavailable during # the upgrade process. A node is considered available if its status is # Ready. class UpgradeSettings include ::Google::Protobuf::MessageExts extend ::Google::Protobuf::MessageExts::ClassMethods end # The current status of the node pool instance. module Status # Not set. STATUS_UNSPECIFIED = 0 # The PROVISIONING state indicates the node pool is being created. PROVISIONING = 1 # The RUNNING state indicates the node pool has been created # and is fully usable. RUNNING = 2 # The RUNNING_WITH_ERROR state indicates the node pool has been created # and is partially usable. Some error state has occurred and some # functionality may be impaired. Customer may need to reissue a request # or trigger a new update. RUNNING_WITH_ERROR = 3 # The RECONCILING state indicates that some work is actively being done on # the node pool, such as upgrading node software. Details can # be found in the `statusMessage` field. RECONCILING = 4 # The STOPPING state indicates the node pool is being deleted. STOPPING = 5 # The ERROR state indicates the node pool may be unusable. Details # can be found in the `statusMessage` field. ERROR = 6 end end |
#status ⇒ ::Google::Cloud::Container::V1::NodePool::Status
Returns [Output only] The status of the nodes in this pool instance.
2143 2144 2145 2146 2147 2148 2149 2150 2151 2152 2153 2154 2155 2156 2157 2158 2159 2160 2161 2162 2163 2164 2165 2166 2167 2168 2169 2170 2171 2172 2173 2174 2175 2176 2177 2178 2179 2180 2181 2182 2183 2184 2185 2186 2187 2188 2189 2190 2191 2192 2193 2194 2195 2196 2197 2198 2199 2200 2201 2202 2203 2204 2205 2206 2207 2208 2209 2210 2211 2212 2213 2214 |
# File 'proto_docs/google/container/v1/cluster_service.rb', line 2143 class NodePool include ::Google::Protobuf::MessageExts extend ::Google::Protobuf::MessageExts::ClassMethods # These upgrade settings control the level of parallelism and the level of # disruption caused by an upgrade. # # maxUnavailable controls the number of nodes that can be simultaneously # unavailable. # # maxSurge controls the number of additional nodes that can be added to the # node pool temporarily for the time of the upgrade to increase the number of # available nodes. # # (maxUnavailable + maxSurge) determines the level of parallelism (how many # nodes are being upgraded at the same time). # # Note: upgrades inevitably introduce some disruption since workloads need to # be moved from old nodes to new, upgraded ones. Even if maxUnavailable=0, # this holds true. (Disruption stays within the limits of # PodDisruptionBudget, if it is configured.) # # Consider a hypothetical node pool with 5 nodes having maxSurge=2, # maxUnavailable=1. This means the upgrade process upgrades 3 nodes # simultaneously. It creates 2 additional (upgraded) nodes, then it brings # down 3 old (not yet upgraded) nodes at the same time. This ensures that # there are always at least 4 nodes available. # @!attribute [rw] max_surge # @return [::Integer] # The maximum number of nodes that can be created beyond the current size # of the node pool during the upgrade process. # @!attribute [rw] max_unavailable # @return [::Integer] # The maximum number of nodes that can be simultaneously unavailable during # the upgrade process. A node is considered available if its status is # Ready. class UpgradeSettings include ::Google::Protobuf::MessageExts extend ::Google::Protobuf::MessageExts::ClassMethods end # The current status of the node pool instance. module Status # Not set. STATUS_UNSPECIFIED = 0 # The PROVISIONING state indicates the node pool is being created. PROVISIONING = 1 # The RUNNING state indicates the node pool has been created # and is fully usable. RUNNING = 2 # The RUNNING_WITH_ERROR state indicates the node pool has been created # and is partially usable. Some error state has occurred and some # functionality may be impaired. Customer may need to reissue a request # or trigger a new update. RUNNING_WITH_ERROR = 3 # The RECONCILING state indicates that some work is actively being done on # the node pool, such as upgrading node software. Details can # be found in the `statusMessage` field. RECONCILING = 4 # The STOPPING state indicates the node pool is being deleted. STOPPING = 5 # The ERROR state indicates the node pool may be unusable. Details # can be found in the `statusMessage` field. ERROR = 6 end end |
#status_message ⇒ ::String
Returns [Output only] Deprecated. Use conditions instead. Additional information about the current status of this node pool instance, if available.
2143 2144 2145 2146 2147 2148 2149 2150 2151 2152 2153 2154 2155 2156 2157 2158 2159 2160 2161 2162 2163 2164 2165 2166 2167 2168 2169 2170 2171 2172 2173 2174 2175 2176 2177 2178 2179 2180 2181 2182 2183 2184 2185 2186 2187 2188 2189 2190 2191 2192 2193 2194 2195 2196 2197 2198 2199 2200 2201 2202 2203 2204 2205 2206 2207 2208 2209 2210 2211 2212 2213 2214 |
# File 'proto_docs/google/container/v1/cluster_service.rb', line 2143 class NodePool include ::Google::Protobuf::MessageExts extend ::Google::Protobuf::MessageExts::ClassMethods # These upgrade settings control the level of parallelism and the level of # disruption caused by an upgrade. # # maxUnavailable controls the number of nodes that can be simultaneously # unavailable. # # maxSurge controls the number of additional nodes that can be added to the # node pool temporarily for the time of the upgrade to increase the number of # available nodes. # # (maxUnavailable + maxSurge) determines the level of parallelism (how many # nodes are being upgraded at the same time). # # Note: upgrades inevitably introduce some disruption since workloads need to # be moved from old nodes to new, upgraded ones. Even if maxUnavailable=0, # this holds true. (Disruption stays within the limits of # PodDisruptionBudget, if it is configured.) # # Consider a hypothetical node pool with 5 nodes having maxSurge=2, # maxUnavailable=1. This means the upgrade process upgrades 3 nodes # simultaneously. It creates 2 additional (upgraded) nodes, then it brings # down 3 old (not yet upgraded) nodes at the same time. This ensures that # there are always at least 4 nodes available. # @!attribute [rw] max_surge # @return [::Integer] # The maximum number of nodes that can be created beyond the current size # of the node pool during the upgrade process. # @!attribute [rw] max_unavailable # @return [::Integer] # The maximum number of nodes that can be simultaneously unavailable during # the upgrade process. A node is considered available if its status is # Ready. class UpgradeSettings include ::Google::Protobuf::MessageExts extend ::Google::Protobuf::MessageExts::ClassMethods end # The current status of the node pool instance. module Status # Not set. STATUS_UNSPECIFIED = 0 # The PROVISIONING state indicates the node pool is being created. PROVISIONING = 1 # The RUNNING state indicates the node pool has been created # and is fully usable. RUNNING = 2 # The RUNNING_WITH_ERROR state indicates the node pool has been created # and is partially usable. Some error state has occurred and some # functionality may be impaired. Customer may need to reissue a request # or trigger a new update. RUNNING_WITH_ERROR = 3 # The RECONCILING state indicates that some work is actively being done on # the node pool, such as upgrading node software. Details can # be found in the `statusMessage` field. RECONCILING = 4 # The STOPPING state indicates the node pool is being deleted. STOPPING = 5 # The ERROR state indicates the node pool may be unusable. Details # can be found in the `statusMessage` field. ERROR = 6 end end |
#upgrade_settings ⇒ ::Google::Cloud::Container::V1::NodePool::UpgradeSettings
Returns Upgrade settings control disruption and speed of the upgrade.
2143 2144 2145 2146 2147 2148 2149 2150 2151 2152 2153 2154 2155 2156 2157 2158 2159 2160 2161 2162 2163 2164 2165 2166 2167 2168 2169 2170 2171 2172 2173 2174 2175 2176 2177 2178 2179 2180 2181 2182 2183 2184 2185 2186 2187 2188 2189 2190 2191 2192 2193 2194 2195 2196 2197 2198 2199 2200 2201 2202 2203 2204 2205 2206 2207 2208 2209 2210 2211 2212 2213 2214 |
# File 'proto_docs/google/container/v1/cluster_service.rb', line 2143 class NodePool include ::Google::Protobuf::MessageExts extend ::Google::Protobuf::MessageExts::ClassMethods # These upgrade settings control the level of parallelism and the level of # disruption caused by an upgrade. # # maxUnavailable controls the number of nodes that can be simultaneously # unavailable. # # maxSurge controls the number of additional nodes that can be added to the # node pool temporarily for the time of the upgrade to increase the number of # available nodes. # # (maxUnavailable + maxSurge) determines the level of parallelism (how many # nodes are being upgraded at the same time). # # Note: upgrades inevitably introduce some disruption since workloads need to # be moved from old nodes to new, upgraded ones. Even if maxUnavailable=0, # this holds true. (Disruption stays within the limits of # PodDisruptionBudget, if it is configured.) # # Consider a hypothetical node pool with 5 nodes having maxSurge=2, # maxUnavailable=1. This means the upgrade process upgrades 3 nodes # simultaneously. It creates 2 additional (upgraded) nodes, then it brings # down 3 old (not yet upgraded) nodes at the same time. This ensures that # there are always at least 4 nodes available. # @!attribute [rw] max_surge # @return [::Integer] # The maximum number of nodes that can be created beyond the current size # of the node pool during the upgrade process. # @!attribute [rw] max_unavailable # @return [::Integer] # The maximum number of nodes that can be simultaneously unavailable during # the upgrade process. A node is considered available if its status is # Ready. class UpgradeSettings include ::Google::Protobuf::MessageExts extend ::Google::Protobuf::MessageExts::ClassMethods end # The current status of the node pool instance. module Status # Not set. STATUS_UNSPECIFIED = 0 # The PROVISIONING state indicates the node pool is being created. PROVISIONING = 1 # The RUNNING state indicates the node pool has been created # and is fully usable. RUNNING = 2 # The RUNNING_WITH_ERROR state indicates the node pool has been created # and is partially usable. Some error state has occurred and some # functionality may be impaired. Customer may need to reissue a request # or trigger a new update. RUNNING_WITH_ERROR = 3 # The RECONCILING state indicates that some work is actively being done on # the node pool, such as upgrading node software. Details can # be found in the `statusMessage` field. RECONCILING = 4 # The STOPPING state indicates the node pool is being deleted. STOPPING = 5 # The ERROR state indicates the node pool may be unusable. Details # can be found in the `statusMessage` field. ERROR = 6 end end |
#version ⇒ ::String
Returns The version of the Kubernetes of this node.
2143 2144 2145 2146 2147 2148 2149 2150 2151 2152 2153 2154 2155 2156 2157 2158 2159 2160 2161 2162 2163 2164 2165 2166 2167 2168 2169 2170 2171 2172 2173 2174 2175 2176 2177 2178 2179 2180 2181 2182 2183 2184 2185 2186 2187 2188 2189 2190 2191 2192 2193 2194 2195 2196 2197 2198 2199 2200 2201 2202 2203 2204 2205 2206 2207 2208 2209 2210 2211 2212 2213 2214 |
# File 'proto_docs/google/container/v1/cluster_service.rb', line 2143 class NodePool include ::Google::Protobuf::MessageExts extend ::Google::Protobuf::MessageExts::ClassMethods # These upgrade settings control the level of parallelism and the level of # disruption caused by an upgrade. # # maxUnavailable controls the number of nodes that can be simultaneously # unavailable. # # maxSurge controls the number of additional nodes that can be added to the # node pool temporarily for the time of the upgrade to increase the number of # available nodes. # # (maxUnavailable + maxSurge) determines the level of parallelism (how many # nodes are being upgraded at the same time). # # Note: upgrades inevitably introduce some disruption since workloads need to # be moved from old nodes to new, upgraded ones. Even if maxUnavailable=0, # this holds true. (Disruption stays within the limits of # PodDisruptionBudget, if it is configured.) # # Consider a hypothetical node pool with 5 nodes having maxSurge=2, # maxUnavailable=1. This means the upgrade process upgrades 3 nodes # simultaneously. It creates 2 additional (upgraded) nodes, then it brings # down 3 old (not yet upgraded) nodes at the same time. This ensures that # there are always at least 4 nodes available. # @!attribute [rw] max_surge # @return [::Integer] # The maximum number of nodes that can be created beyond the current size # of the node pool during the upgrade process. # @!attribute [rw] max_unavailable # @return [::Integer] # The maximum number of nodes that can be simultaneously unavailable during # the upgrade process. A node is considered available if its status is # Ready. class UpgradeSettings include ::Google::Protobuf::MessageExts extend ::Google::Protobuf::MessageExts::ClassMethods end # The current status of the node pool instance. module Status # Not set. STATUS_UNSPECIFIED = 0 # The PROVISIONING state indicates the node pool is being created. PROVISIONING = 1 # The RUNNING state indicates the node pool has been created # and is fully usable. RUNNING = 2 # The RUNNING_WITH_ERROR state indicates the node pool has been created # and is partially usable. Some error state has occurred and some # functionality may be impaired. Customer may need to reissue a request # or trigger a new update. RUNNING_WITH_ERROR = 3 # The RECONCILING state indicates that some work is actively being done on # the node pool, such as upgrading node software. Details can # be found in the `statusMessage` field. RECONCILING = 4 # The STOPPING state indicates the node pool is being deleted. STOPPING = 5 # The ERROR state indicates the node pool may be unusable. Details # can be found in the `statusMessage` field. ERROR = 6 end end |