Kubernetes Engine V1 API - Module Google::Cloud::Container::V1::Operation::Type (v0.21.1)

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

Operation type categorizes the operation.

value: 0
Not set.

value: 1
The cluster is being created. The cluster should be assumed to be unusable until the operation finishes.

In the event of the operation failing, the cluster will enter the [ERROR state][Cluster.Status.ERROR] and eventually be deleted.

value: 2
The cluster is being deleted. The cluster should be assumed to be unusable as soon as this operation starts.

In the event of the operation failing, the cluster will enter the [ERROR state][Cluster.Status.ERROR] and the deletion will be automatically retried until completed.

value: 3
The [cluster version][google.container.v1.ClusterUpdate.desired_master_version] is being updated. Note that this includes "upgrades" to the same version, which are simply a recreation. This also includes auto-upgrades. For more details, see documentation on cluster upgrades.

value: 4
A node pool is being updated. Despite calling this an "upgrade", this includes most forms of updates to node pools. This also includes auto-upgrades.

This operation sets the progress field and may be canceled.

The upgrade strategy depends on node pool configuration. The nodes are generally still usable during this operation.

value: 5
A problem has been detected with the control plane and is being repaired. This operation type is initiated by GKE. For more details, see documentation on repairs.

value: 6
The cluster is being updated. This is a broad category of operations and includes operations that only change metadata as well as those that must recreate the entire cluster. If the control plane must be recreated, this will cause temporary downtime for zonal clusters.

Some features require recreating the nodes as well. Those will be recreated as separate operations and the update may not be completely functional until the node pools recreations finish. Node recreations will generally follow maintenance policies.

Some GKE-initiated operations use this type. This includes certain types of auto-upgrades and incident mitigations.

value: 7
A node pool is being created. The node pool should be assumed to be unusable until this operation finishes. In the event of an error, the node pool may be partially created.

If enabled, node autoprovisioning may have automatically initiated such operations.

value: 8
The node pool is being deleted. The node pool should be assumed to be unusable as soon as this operation starts.

value: 9
The node pool's manamagent field is being updated. These operations only update metadata and may be concurrent with most other operations.

value: 10
A problem has been detected with nodes and they are being repaired. This operation type is initiated by GKE, typically automatically. This operation may be concurrent with other operations and there may be multiple repairs occurring on the same node pool.

value: 11
Unused. Automatic node upgrade uses UPGRADE_NODES.

value: 12
Unused. Updating labels uses UPDATE_CLUSTER.

value: 13
Unused. Updating master auth uses UPDATE_CLUSTER.

value: 14
The node pool is being resized. With the exception of resizing to or from size zero, the node pool is generally usable during this operation.

value: 15
Unused. Updating network policy uses UPDATE_CLUSTER.

value: 16
Unused. Updating maintenance policy uses UPDATE_CLUSTER.

value: 18
The control plane is being resized. This operation type is initiated by GKE. These operations are often performed preemptively to ensure that the control plane has sufficient resources and is not typically an indication of issues. For more details, see documentation on resizes.