You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When true, the workload is rendered as a Kubernetes StatefulSet instead of a Deployment. Recommended for deployments with a ReadWriteOnce volume: updates terminate the old pod before creating the new one, so no Recreate strategy or node pinning is needed. The volume, unless nfs-shared or externally managed (auto false), is provisioned per replica through volumeClaimTemplates. A pre-existing PVC named after the volume (left over from a previous Deployment) is migrated automatically: a migration job streams its data into each statefulset volume through the Kubernetes API, so the volumes are never mounted by the same pod (works on multi-zone clusters); delete the legacy PVC once migrated.
Extra containers (init containers and sidecars) for the deployment. Each key is a container name mapping to an ExtraContainerConfig.
[optional]
Example
fromcloudharness_model.models.deployment_auto_artifact_configimportDeploymentAutoArtifactConfig# TODO update the JSON string belowjson="{}"# create an instance of DeploymentAutoArtifactConfig from a JSON stringdeployment_auto_artifact_config_instance=DeploymentAutoArtifactConfig.from_json(json)
# print the JSON string representation of the objectprint(DeploymentAutoArtifactConfig.to_json())
# convert the object into a dictdeployment_auto_artifact_config_dict=deployment_auto_artifact_config_instance.to_dict()
# create an instance of DeploymentAutoArtifactConfig from a dictdeployment_auto_artifact_config_from_dict=DeploymentAutoArtifactConfig.from_dict(deployment_auto_artifact_config_dict)