imjasonh/gcloud-help
1
0
Fork 0
mirror of https://github.com/imjasonh/gcloud-help synced 2026-07-08 10:35:03 +00:00
Code Activity

gcloud: Thu May 30 09:26:18 UTC 2024

Browse source
This commit is contained in:
Automated 2024-05-30 09:26:18 +00:00
parent e617a432f4
commit 595ac8640a
232 changed files with 10919 additions and 274 deletions
Download patch file Download diff file Expand all files Collapse all files

6
gcloud/beta/container/backup-restore/backup-plans/create
View file

@ -11,7 +11,7 @@ SYNOPSIS
[--backup-delete-lock-days=BACKUP_DELETE_LOCK_DAYS
--backup-retain-days=BACKUP_RETAIN_DAYS --locked]
[--encryption-key=ENCRYPTION_KEY
--include-secrets --include-volume-data]
--include-secrets --include-volume-data --permissive-mode]
[--paused --cron-schedule=CRON_SCHEDULE
[--target-rpo-minutes=TARGET_RPO_MINUTES
: --exclusion-windows-file=EXCLUSION_WINDOWS_FILE]]
@ -149,6 +149,10 @@ OPTIONAL FLAGS
PersistentVolumeClaims that fall within the scope. If unset, the
default is false.
--permissive-mode
If true, backups won't fail when Backup for GKE detects Kubernetes
configuration that is known to cause restore failures.
--paused
If set, automatic backup creation is suppressed. When unset, automatic
backup creation resumes with the next scheduled create event.

6
gcloud/beta/container/backup-restore/backup-plans/update
View file

@ -13,7 +13,7 @@ SYNOPSIS
--backup-retain-days=BACKUP_RETAIN_DAYS --locked]
[--clear-labels | --remove-labels=[KEY,...]]
[--encryption-key=ENCRYPTION_KEY
--include-secrets --include-volume-data]
--include-secrets --include-volume-data --permissive-mode]
[--paused --cron-schedule=CRON_SCHEDULE
--exclusion-windows-file=EXCLUSION_WINDOWS_FILE
--target-rpo-minutes=TARGET_RPO_MINUTES] [GCLOUD_WIDE_FLAG ...]
@ -165,6 +165,10 @@ FLAGS
PersistentVolumeClaims that fall within the scope. If unset, the
default is false.
--permissive-mode
If true, backups won't fail when Backup for GKE detects Kubernetes
configuration that is known to cause restore failures.
--paused
If set, automatic backup creation is suppressed. When unset, automatic
backup creation resumes with the next scheduled create event.

56
gcloud/beta/container/backup-restore/restore-plans/create
View file

@ -12,8 +12,10 @@ SYNOPSIS
[--cluster-resource-conflict-policy=CLUSTER_RESOURCE_CONFLICT_POLICY]
[--description=DESCRIPTION] [--labels=[KEY=VALUE,...]]
[--namespaced-resource-restore-mode=NAMESPACED_RESOURCE_RESTORE_MODE]
[--restore-order-file=RESTORE_ORDER_FILE]
[--volume-data-restore-policy=VOLUME_DATA_RESTORE_POLICY;
default="no-volume-data-restoration"]
[--volume-data-restore-policy-bindings=[VOLUME_TYPE=POLICY,...]]
[--cluster-resource-scope-all-group-kinds
| --cluster-resource-scope-excluded-group-kinds=[CLUSTER_RESOURCE_SCOPE_EXCLUDED_GROUP_KINDS,
...] | --cluster-resource-scope-no-group-kinds
@ -173,6 +175,45 @@ OPTIONAL FLAGS
out of band process creates conflicting resources), a conflict will
be reported.
merge-replace-on-conflict
This mode merges the backup and the target cluster and replaces the
conflicting resources with the ones in the backup. If a single
resource to restore exists in the cluster before restoration, the
resource will be replaced with the one from the backup. To replace
an existing resource, the first attempt is to update the resource
to match the one from the backup; if the update fails, the second
attempt is to delete the resource and restore it from the backup.
Note that this mode could cause data loss as it replaces the
existing resources in the target cluster, and the original PV can
be retained or deleted depending on its reclaim policy.
merge-replace-volume-on-conflict
This mode merges the backup and the target cluster and skips the
conflicting resources except volume data. If a PVC to restore
already exists, this mode will restore/reconnect the volume without
overwriting the PVC. It is similar to MERGE_SKIP_ON_CONFLICT except
that it will apply the volume data policy for the conflicting PVCs
"RESTORE_VOLUME_DATA_FROM_BACKUP:" restore data only and respect
the reclaim policy of the original PV;
"REUSE_VOLUME_HANDLE_FROM_BACKUP:" reconnect and respect the
reclaim policy of the original PV; "NO_VOLUME_DATA_RESTORATION:"
new provision and respect the reclaim policy of the original PV.
Note that this mode could cause data loss as the original PV can be
retained or deleted depending on its reclaim policy.
merge-skip-on-conflict
This mode merges the backup and the target cluster and skips the
conflicting resources. If a single resource to restore exists in
the cluster before restoration, the resource will be skipped,
otherwise it will be restored.
--restore-order-file=RESTORE_ORDER_FILE
If provided, defines a custom order that can be used in a restore,
which includes dependencies between two group kinds that must be
honored during a restore, a satisfying group kind and a requiring group
kind. The satisfying group kind must be restored before the requiring
group kind.
--volume-data-restore-policy=VOLUME_DATA_RESTORE_POLICY; default="no-volume-data-restoration"
Define how data is populated for restored volumes. If this flag is not
specified, 'no-volume-data-restoration' will be used.
@ -194,6 +235,12 @@ OPTIONAL FLAGS
pre-provisioned using the volume handle of the original PV in the
Backup.
--volume-data-restore-policy-bindings=[VOLUME_TYPE=POLICY,...]
Dict that binds a supported volume type to a volume data restore
policy. e.g. gce-persistent-disk=restore-volume-data-from-backup for a
binding that results in Persistent Disk volumes being restored using
the "restore volume data from backup" policy.
The scope of cluster-scoped resources to restore.
At most one of these can be specified:
@ -221,9 +268,12 @@ OPTIONAL FLAGS
At most one of these can be specified:
--substitution-rules-file=SUBSTITUTION_RULES_FILE
If provided, defines a set of resource transformations that will be
applied to resources from the source backup before they are created
in the target cluster.
(DEPRECATED) If provided, defines a set of resource transformations
that will be applied to resources from the source backup before they
are created in the target cluster.
Flag substitution-rules-file is deprecated. Please use
--transformation-rules-file instead.
--transformation-rules-file=TRANSFORMATION_RULES_FILE
If provided, defines a set of resource transformations that will be

56
gcloud/beta/container/backup-restore/restore-plans/update
View file

@ -8,9 +8,11 @@ SYNOPSIS
[--cluster-resource-conflict-policy=CLUSTER_RESOURCE_CONFLICT_POLICY]
[--description=DESCRIPTION] [--etag=ETAG]
[--namespaced-resource-restore-mode=NAMESPACED_RESOURCE_RESTORE_MODE]
[--restore-order-file=RESTORE_ORDER_FILE]
[--update-labels=[KEY=VALUE,...]]
[--volume-data-restore-policy=VOLUME_DATA_RESTORE_POLICY;
default="no-volume-data-restoration"]
[--volume-data-restore-policy-bindings=[VOLUME_TYPE=POLICY,...]]
[--all-namespaces | --excluded-namespaces=[EXCLUDED_NAMESPACES,...]
| --no-namespaces | --selected-applications=SELECTED_APPLICATIONS
| --selected-namespaces=[SELECTED_NAMESPACES,...]]
@ -125,6 +127,45 @@ FLAGS
out of band process creates conflicting resources), a conflict will
be reported.
merge-replace-on-conflict
This mode merges the backup and the target cluster and replaces the
conflicting resources with the ones in the backup. If a single
resource to restore exists in the cluster before restoration, the
resource will be replaced with the one from the backup. To replace
an existing resource, the first attempt is to update the resource
to match the one from the backup; if the update fails, the second
attempt is to delete the resource and restore it from the backup.
Note that this mode could cause data loss as it replaces the
existing resources in the target cluster, and the original PV can
be retained or deleted depending on its reclaim policy.
merge-replace-volume-on-conflict
This mode merges the backup and the target cluster and skips the
conflicting resources except volume data. If a PVC to restore
already exists, this mode will restore/reconnect the volume without
overwriting the PVC. It is similar to MERGE_SKIP_ON_CONFLICT except
that it will apply the volume data policy for the conflicting PVCs
"RESTORE_VOLUME_DATA_FROM_BACKUP:" restore data only and respect
the reclaim policy of the original PV;
"REUSE_VOLUME_HANDLE_FROM_BACKUP:" reconnect and respect the
reclaim policy of the original PV; "NO_VOLUME_DATA_RESTORATION:"
new provision and respect the reclaim policy of the original PV.
Note that this mode could cause data loss as the original PV can be
retained or deleted depending on its reclaim policy.
merge-skip-on-conflict
This mode merges the backup and the target cluster and skips the
conflicting resources. If a single resource to restore exists in
the cluster before restoration, the resource will be skipped,
otherwise it will be restored.
--restore-order-file=RESTORE_ORDER_FILE
If provided, defines a custom order that can be used in a restore,
which includes dependencies between two group kinds that must be
honored during a restore, a satisfying group kind and a requiring group
kind. The satisfying group kind must be restored before the requiring
group kind.
--update-labels=[KEY=VALUE,...]
List of label KEY=VALUE pairs to update. If a label exists, its value
is modified. Otherwise, a new label is created.
@ -155,6 +196,12 @@ FLAGS
pre-provisioned using the volume handle of the original PV in the
Backup.
--volume-data-restore-policy-bindings=[VOLUME_TYPE=POLICY,...]
Dict that binds a supported volume type to a volume data restore
policy. e.g. gce-persistent-disk=restore-volume-data-from-backup for a
binding that results in Persistent Disk volumes being restored using
the "restore volume data from backup" policy.
The scope of namespaced resources to restore.
At most one of these can be specified:
@ -226,9 +273,12 @@ FLAGS
At most one of these can be specified:
--substitution-rules-file=SUBSTITUTION_RULES_FILE
If provided, defines a set of resource transformations that will be
applied to resources from the source backup before they are created
in the target cluster.
(DEPRECATED) If provided, defines a set of resource transformations
that will be applied to resources from the source backup before they
are created in the target cluster.
Flag substitution-rules-file is deprecated. Please use
--transformation-rules-file instead.
--transformation-rules-file=TRANSFORMATION_RULES_FILE
If provided, defines a set of resource transformations that will be

17
gcloud/beta/container/backup-restore/restores/create
View file

@ -4,7 +4,9 @@ NAME
SYNOPSIS
gcloud beta container backup-restore restores create
(RESTORE : --location=LOCATION --restore-plan=RESTORE_PLAN)
--backup=BACKUP [--description=DESCRIPTION] [--labels=[KEY=VALUE,...]]
--backup=BACKUP [--description=DESCRIPTION] [--filter-file=FILTER_FILE]
[--labels=[KEY=VALUE,...]]
[--volume-data-restore-policy-overrides-file=VOLUME_DATA_RESTORE_POLICY_OVERRIDES_FILE]
[--async | --wait-for-completion] [GCLOUD_WIDE_FLAG ...]
DESCRIPTION
@ -78,6 +80,15 @@ OPTIONAL FLAGS
--description=DESCRIPTION
Optional text description for the restore.
--filter-file=FILTER_FILE
JSON/YAML file containing the configuration of the fine-grained restore
filter which can be used to further refine the resource selection of
the Restore beyond the coarse-grained scope defined in the RestorePlan.
For more information about examples and how to use this filter, please
refer to the Backup for GKE documentation:
https://cloud.google.com/kubernetes-engine/docs/add-on/backup-for-gke.
--labels=[KEY=VALUE,...]
List of label KEY=VALUE pairs to add.
@ -86,6 +97,10 @@ OPTIONAL FLAGS
contain only hyphens (-), underscores (_), lowercase characters, and
numbers.
--volume-data-restore-policy-overrides-file=VOLUME_DATA_RESTORE_POLICY_OVERRIDES_FILE
If provided, defines an array of volume data restore policy overrides
from the given config file in yaml.
At most one of these can be specified:
--async