SrSSKJr SSKJr SSKJr SSKJr SSKJ r SSK J r SSK J r SSK Jr SS K Jr SS KJr SS KJr SS KJr "S S\ R(5rSSSS.\lg)zResize cluster command.)absolute_import)division)unicode_literals) exceptions)util)actions)base)flags)log) console_attr) console_ioc.\rSrSrSr\S5rSrSrg)Resize!3Resizes an existing cluster for running containers.c  URSSS9 URSS9nURS[S[R"SSS 9S S 9 URS [S S 9 URSSS9 [ R "U5 g)zRegister flags for this command. Args: parser: An argparse.ArgumentParser-like object. It is mocked out in order to capture some information, but behaves like an ArgumentParser. namezThe name of this cluster.)helpT)requiredz--size num_nodeszIThe {flag_name} flag is now deprecated. Please use `--num-nodes` instead.)warnz&Target number of nodes in the cluster.)typedestactionrz --num-nodes)rrz --node-poolzThe node pool to resize.N) add_argumentadd_mutually_exclusive_groupintrDeprecationActionr AddAsyncFlag)parsergroups (lib/surface/container/clusters/resize.pyArgs Resize.Args$s %@A  / / / >E   ((/4567   57  ,FG vcURSnURSnU"U5nURURU5nSnURnUR(a UROSnUR U5nURnUb%UR!XaR5Rn["R$"SRUUUR&S9SSS 9 UR)XXUR&5n UR*(d+UR-U S RUR.55 [R0"U5 g![ R [R[R4aDn [R"SR[R"U 555 Sn A GN8Sn A ff=f) zThis is what gets called when the user runs this command. Args: args: an argparse namespace. All the arguments that were provided to this command invocation. api_adapter location_getNz default-poolz`Problem loading details of cluster to resize: {} You can still attempt to resize the cluster. z_Pool [{pool}] for [{cluster_name}] will be resized to {new_size} node(s) in each zone it spans.)pool cluster_namenew_sizeT)messagethrow_if_unattended cancel_on_noz Resizing {0})context ParseClusterr node_pool GetClusterr HttpExceptionapitools_exceptionsHttpForbiddenErrorrErrorr warningformatr SafeText FindNodePoolr PromptContinuerResizeNodePoolasync_WaitForOperation clusterIdUpdatedResource) selfargsadapterr(location cluster_refclusterr* pool_nameerrorop_refs r"Run Resize.Run>sll=)G<</LD!H&&tyy(;KG99L"&..nI 6"";/g\\l&&w?DDi=>Df#"."nn?E?.! # #KDNN KF ;; v-44[5J5JKM $/  $ $&9&L&L JJ 6 kkDEKV#,,U3F5666s1E3G 9GG N) __name__ __module__ __qualname____firstlineno____doc__ staticmethodr#rJ__static_attributes__rLr%r"rr!s;2+%r%rra3 Resize an existing cluster to a provided size. If you have multiple node pools, you must specify which node pool to resize by using the --node-pool flag. You are not required to use the flag if you have a single node pool. When increasing the size of a container cluster, the new instances are created with the same configuration as the existing instances. Existing pods are not moved onto the new instances, but new pods (such as those created by resizing a replication controller) will be scheduled onto the new instances. When decreasing a cluster, the nodes are drained. As a result, the pods running on these nodes are gracefully terminated. If your pods are being managed by a workload controller, the controller will attempt to reschedule them onto the remaining instances. If your pods are not managed by a workload controller, they will not be restarted. Note that when resizing down, instances running pods and instances without pods are not differentiated. Resize will pick instances to remove at random. When you resize a node pool that spans multiple zones, the new size represents the number of nodes in the node pool per zone. For example, if you have a node pool of size 2 spanning two zones, the total node count is 4. If you resize the node pool with `--num-nodes=4`, the total node count becomes 8. z To resize the default node pool of an existing cluster, run: $ {command} sample-cluster --num-nodes=2 )brief DESCRIPTIONEXAMPLESN)rQ __future__rrrapitools.base.pyrr4 googlecloudsdk.api_lib.containerrgooglecloudsdk.callioperr $googlecloudsdk.command_lib.containerr googlecloudsdk.corer googlecloudsdk.core.consoler r Commandr detailed_helprLr%r"r`sZ&'>1+(.6#42H%T\\H%Z > 6 ?$r%