Enum Operation.Type (2.23.0)

public enum Operation.Type extends Enum<Operation.Type> implements ProtocolMessageEnum

Operation type categorizes the operation.

Protobuf enum google.container.v1beta1.Operation.Type

Implements

ProtocolMessageEnum

Static Fields

NameDescription
AUTO_REPAIR_NODES

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.

AUTO_REPAIR_NODES = 10;

AUTO_REPAIR_NODES_VALUE

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.

AUTO_REPAIR_NODES = 10;

AUTO_UPGRADE_NODES

Unused. Automatic node upgrade uses UPGRADE_NODES.

AUTO_UPGRADE_NODES = 11 [deprecated = true];

AUTO_UPGRADE_NODES_VALUE

Unused. Automatic node upgrade uses UPGRADE_NODES.

AUTO_UPGRADE_NODES = 11 [deprecated = true];

CREATE_CLUSTER

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 and eventually be deleted.

CREATE_CLUSTER = 1;

CREATE_CLUSTER_VALUE

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 and eventually be deleted.

CREATE_CLUSTER = 1;

CREATE_NODE_POOL

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.

CREATE_NODE_POOL = 7;

CREATE_NODE_POOL_VALUE

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.

CREATE_NODE_POOL = 7;

DELETE_CLUSTER

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 and the deletion will be automatically retried until completed.

DELETE_CLUSTER = 2;

DELETE_CLUSTER_VALUE

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 and the deletion will be automatically retried until completed.

DELETE_CLUSTER = 2;

DELETE_NODE_POOL

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

DELETE_NODE_POOL = 8;

DELETE_NODE_POOL_VALUE

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

DELETE_NODE_POOL = 8;

REPAIR_CLUSTER

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.

REPAIR_CLUSTER = 5;

REPAIR_CLUSTER_VALUE

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.

REPAIR_CLUSTER = 5;

RESIZE_CLUSTER

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.

RESIZE_CLUSTER = 18;

RESIZE_CLUSTER_VALUE

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.

RESIZE_CLUSTER = 18;

SET_LABELS

Unused. Updating labels uses UPDATE_CLUSTER.

SET_LABELS = 12 [deprecated = true];

SET_LABELS_VALUE

Unused. Updating labels uses UPDATE_CLUSTER.

SET_LABELS = 12 [deprecated = true];

SET_MAINTENANCE_POLICY

Unused. Updating maintenance policy uses UPDATE_CLUSTER.

SET_MAINTENANCE_POLICY = 16 [deprecated = true];

SET_MAINTENANCE_POLICY_VALUE

Unused. Updating maintenance policy uses UPDATE_CLUSTER.

SET_MAINTENANCE_POLICY = 16 [deprecated = true];

SET_MASTER_AUTH

Unused. Updating master auth uses UPDATE_CLUSTER.

SET_MASTER_AUTH = 13 [deprecated = true];

SET_MASTER_AUTH_VALUE

Unused. Updating master auth uses UPDATE_CLUSTER.

SET_MASTER_AUTH = 13 [deprecated = true];

SET_NETWORK_POLICY

Unused. Updating network policy uses UPDATE_CLUSTER.

SET_NETWORK_POLICY = 15 [deprecated = true];

SET_NETWORK_POLICY_VALUE

Unused. Updating network policy uses UPDATE_CLUSTER.

SET_NETWORK_POLICY = 15 [deprecated = true];

SET_NODE_POOL_MANAGEMENT

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

SET_NODE_POOL_MANAGEMENT = 9;

SET_NODE_POOL_MANAGEMENT_VALUE

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

SET_NODE_POOL_MANAGEMENT = 9;

SET_NODE_POOL_SIZE

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_NODE_POOL_SIZE = 14;

SET_NODE_POOL_SIZE_VALUE

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_NODE_POOL_SIZE = 14;

TYPE_UNSPECIFIED

Not set.

TYPE_UNSPECIFIED = 0;

TYPE_UNSPECIFIED_VALUE

Not set.

TYPE_UNSPECIFIED = 0;

UNRECOGNIZED
UPDATE_CLUSTER

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.

UPDATE_CLUSTER = 6;

UPDATE_CLUSTER_VALUE

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.

UPDATE_CLUSTER = 6;

UPGRADE_MASTER

The cluster 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.

UPGRADE_MASTER = 3;

UPGRADE_MASTER_VALUE

The cluster 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.

UPGRADE_MASTER = 3;

UPGRADE_NODES

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 confi