- 2.45.0 (latest)
- 2.44.0
- 2.43.0
- 2.42.0
- 2.41.0
- 2.40.0
- 2.39.0
- 2.38.0
- 2.37.0
- 2.36.0
- 2.35.0
- 2.34.0
- 2.33.0
- 2.32.0
- 2.31.0
- 2.30.0
- 2.29.0
- 2.28.0
- 2.27.0
- 2.26.0
- 2.25.0
- 2.24.0
- 2.23.0
- 2.22.0
- 2.21.0
- 2.20.0
- 2.19.0
- 2.18.0
- 2.17.4
- 2.16.0
- 2.15.0
- 2.14.0
- 2.13.0
- 2.12.2
- 2.11.2
- 2.10.8
- 2.9.0
- 2.8.1
- 2.7.1
- 2.6.1
- 2.5.0
- 2.4.1
- 2.3.1
- 2.2.0
- 2.1.0
- 2.0.1
- 1.0.3
- 0.5.0
- 0.4.0
- 0.3.0
Type(value)Operation type categorizes the operation.
Values: TYPE_UNSPECIFIED (0): Not set. CREATE_CLUSTER (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.
DELETE_CLUSTER (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.
UPGRADE_MASTER (3):
The [cluster
version][google.container.v1beta1.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 <https://cloud.google.com/kubernetes-engine/docs/concepts/cluster-upgrades#upgrading_automatically>`__.
For more details, see `documentation on cluster
upgrades <https://cloud.google.com/kubernetes-engine/docs/concepts/cluster-upgrades#cluster_upgrades>`__.
UPGRADE_NODES (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 <https://cloud.google.com/kubernetes-engine/docs/how-to/node-auto-upgrades>`__.
This operation sets the
`progress][google.container.v1beta1.Operation.progress]`
field and may be
`canceled][google.container.v1beta1.ClusterManager.CancelOperation]`.
The upgrade strategy depends on `node pool
configuration <https://cloud.google.com/kubernetes-engine/docs/concepts/node-pool-upgrade-strategies>`__.
The nodes are generally still usable during this operation.
REPAIR_CLUSTER (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 <https://cloud.google.com/kubernetes-engine/docs/concepts/maintenance-windows-and-exclusions#repairs>`__.
UPDATE_CLUSTER (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 <https://cloud.google.com/kubernetes-engine/docs/concepts/maintenance-windows-and-exclusions>`__.
Some GKE-initiated operations use this type. This includes
certain types of auto-upgrades and incident mitigations.
CREATE_NODE_POOL (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 <https://cloud.google.com/kubernetes-engine/docs/how-to/node-auto-provisioning>`__
may have automatically initiated such operations.
DELETE_NODE_POOL (8):
The node pool is being deleted. The node pool
should be assumed to be unusable as soon as this
operation starts.
SET_NODE_POOL_MANAGEMENT (9):
The node pool's
`manamagent][google.container.v1beta1.NodePool.management]`
field is being updated. These operations only update
metadata and may be concurrent with most other operations.
AUTO_REPAIR_NODES (10):
A problem has been detected with nodes and `they are being
repaired <https://cloud.google.com/kubernetes-engine/docs/how-to/node-auto-repair>`__.
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.
AUTO_UPGRADE_NODES (11):
Unused. Automatic node upgrade uses
`UPGRADE_NODES][google.container.v1beta1.Operation.Type.UPGRADE_NODES]`.
SET_LABELS (12):
Unused. Updating labels uses
`UPDATE_CLUSTER][google.container.v1beta1.Operation.Type.UPDATE_CLUSTER]`.
SET_MASTER_AUTH (13):
Unused. Updating master auth uses
`UPDATE_CLUSTER][google.container.v1beta1.Operation.Type.UPDATE_CLUSTER]`.
SET_NODE_POOL_SIZE (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.
SET_NETWORK_POLICY (15):
Unused. Updating network policy uses
`UPDATE_CLUSTER][google.container.v1beta1.Operation.Type.UPDATE_CLUSTER]`.
SET_MAINTENANCE_POLICY (16):
Unused. Updating maintenance policy uses
`UPDATE_CLUSTER][google.container.v1beta1.Operation.Type.UPDATE_CLUSTER]`.
RESIZE_CLUSTER (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 <https://cloud.google.com/kubernetes-engine/docs/concepts/maintenance-windows-and-exclusions#repairs>`__.
FLEET_FEATURE_UPGRADE (19):
Fleet features of GKE Enterprise are being
upgraded. The cluster should be assumed to be
blocked for other upgrades until the operation
finishes.