Freigeben über


ContainerServiceFleetUpdateRunData Class

Definition

A class representing the ContainerServiceFleetUpdateRun data model. A multi-stage process to perform update operations across members of a Fleet.

public class ContainerServiceFleetUpdateRunData : Azure.ResourceManager.Models.ResourceData
type ContainerServiceFleetUpdateRunData = class
    inherit ResourceData
Public Class ContainerServiceFleetUpdateRunData
Inherits ResourceData
Inheritance
ContainerServiceFleetUpdateRunData

Constructors

ContainerServiceFleetUpdateRunData()

Initializes a new instance of ContainerServiceFleetUpdateRunData.

Properties

ETag

If eTag is provided in the response body, it may also be provided as a header per the normal etag convention. Entity tags are used for comparing two or more entities from the same requested resource. HTTP/1.1 uses entity tags in the etag (section 14.19), If-Match (section 14.24), If-None-Match (section 14.26), and If-Range (section 14.27) header fields.

Id

Fully qualified resource ID for the resource. Ex - /subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/{resourceProviderNamespace}/{resourceType}/{resourceName}.

(Inherited from ResourceData)
ManagedClusterUpdate

The update to be applied to all clusters in the UpdateRun. The managedClusterUpdate can be modified until the run is started.

Name

The name of the resource.

(Inherited from ResourceData)
ProvisioningState

The provisioning state of the UpdateRun resource.

ResourceType

The type of the resource. E.g. "Microsoft.Compute/virtualMachines" or "Microsoft.Storage/storageAccounts".

(Inherited from ResourceData)
Status

The status of the UpdateRun.

StrategyStages

The list of stages that compose this update run. Min size: 1.

SystemData

Azure Resource Manager metadata containing createdBy and modifiedBy information.

(Inherited from ResourceData)
UpdateStrategyId

The resource id of the FleetUpdateStrategy resource to reference.

When creating a new run, there are three ways to define a strategy for the run:

  1. Define a new strategy in place: Set the "strategy" field.
  2. Use an existing strategy: Set the "updateStrategyId" field. (since 2023-08-15-preview)
  3. Use the default strategy to update all the members one by one: Leave both "updateStrategyId" and "strategy" unset. (since 2023-08-15-preview)

Setting both "updateStrategyId" and "strategy" is invalid.

UpdateRuns created by "updateStrategyId" snapshot the referenced UpdateStrategy at the time of creation and store it in the "strategy" field. Subsequent changes to the referenced FleetUpdateStrategy resource do not propagate. UpdateRunStrategy changes can be made directly on the "strategy" field before launching the UpdateRun.

Applies to