gcloud: Wed Jan 29 10:02:21 UTC 2025

gcloud/beta/container/backup-restore/help

@@ -24,6 +24,9 @@ GROUPS
      locations
         (BETA) Backup for GKE Locations.
 
+     operations
+        (BETA) Backup for GKE Operations.
+
      restore-plans
         (BETA) Backup for GKE Restore Plans.
 

gcloud/beta/container/backup-restore/operations/help

@@ -0,0 +1,27 @@
+NAME
+    gcloud beta container backup-restore operations - backup for GKE Operations
+
+SYNOPSIS
+    gcloud beta container backup-restore operations COMMAND
+        [GCLOUD_WIDE_FLAG ...]
+
+DESCRIPTION
+    (BETA) Backup for GKE Operations.
+
+GCLOUD WIDE FLAGS
+    These flags are available to all commands: --help.
+
+    Run $ gcloud help for details.
+
+COMMANDS
+    COMMAND is one of the following:
+
+     list
+        (BETA) List operations.
+
+NOTES
+    This command is currently in beta and might change without notice. This
+    variant is also available:
+
+        $ gcloud alpha container backup-restore operations
+

gcloud/beta/container/backup-restore/operations/list

@@ -0,0 +1,94 @@
+NAME
+    gcloud beta container backup-restore operations list - list operations
+
+SYNOPSIS
+    gcloud beta container backup-restore operations list [--location=LOCATION]
+        [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE]
+        [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...]
+
+DESCRIPTION
+    (BETA) List Backup for GKE operations.
+
+EXAMPLES
+    To list all operations in project my-project in location us-central1, run:
+
+        $ gcloud beta container backup-restore operations list \
+            --project=my-project --location=us-central1
+
+    To list all operations in project my-project across all locations, run:
+
+        $ gcloud beta container backup-restore operations list \
+            --project=my-project
+
+FLAGS
+     Location resource - Name of the location from which to list operations
+     (provided via options or through properties): --project=<project>
+     --location=<location>. This represents a Cloud resource. (NOTE) Some
+     attributes are not given arguments in this group but can be set in other
+     ways.
+
+     To set the project attribute:
+      ◆ provide the argument --location on the command line with a fully
+        specified name;
+      ◆ set the property gkebackup/location with a fully specified name;
+      ◆ provide the argument --project on the command line;
+      ◆ set the property core/project.
+
+       --location=LOCATION
+          ID of the location or fully qualified identifier for the location.
+
+          To set the location attribute:
+          ▸ provide the argument --location on the command line;
+          ▸ set the property gkebackup/location.
+
+LIST COMMAND FLAGS
+     --filter=EXPRESSION
+        Apply a Boolean filter EXPRESSION to each resource item to be listed.
+        If the expression evaluates True, then that item is listed. For more
+        details and examples of filter expressions, run $ gcloud topic filters.
+        This flag interacts with other flags that are applied in this order:
+        --flatten, --sort-by, --filter, --limit.
+
+     --limit=LIMIT
+        Maximum number of resources to list. The default is unlimited. This
+        flag interacts with other flags that are applied in this order:
+        --flatten, --sort-by, --filter, --limit.
+
+     --page-size=PAGE_SIZE
+        Some services group resource list output into pages. This flag
+        specifies the maximum number of resources per page. The default is
+        determined by the service if it supports paging, otherwise it is
+        unlimited (no paging). Paging may be applied before or after --filter
+        and --limit depending on the service.
+
+     --sort-by=[FIELD,...]
+        Comma-separated list of resource field key names to sort by. The
+        default order is ascending. Prefix a field with ``~'' for descending
+        order on that field. This flag interacts with other flags that are
+        applied in this order: --flatten, --sort-by, --filter, --limit.
+
+     --uri
+        Print a list of resource URIs instead of the default output, and change
+        the command output to a list of URIs. If this flag is used with
+        --format, the formatting is applied on this URI list. To display URIs
+        alongside other keys instead, use the uri() transform.
+
+GCLOUD WIDE FLAGS
+    These flags are available to all commands: --access-token-file, --account,
+    --billing-project, --configuration, --flags-file, --flatten, --format,
+    --help, --impersonate-service-account, --log-http, --project, --quiet,
+    --trace-token, --user-output-enabled, --verbosity.
+
+    Run $ gcloud help for details.
+
+API REFERENCE
+    This command uses the gkebackup/v1 API. The full documentation for this API
+    can be found at:
+    https://cloud.google.com/kubernetes-engine/docs/add-on/backup-for-gke
+
+NOTES
+    This command is currently in beta and might change without notice. This
+    variant is also available:
+
+        $ gcloud alpha container backup-restore operations list
+

gcloud/beta/container/clusters/create

@@ -612,10 +612,20 @@ FLAGS
         IP if --enable-private-endpoint is not enabled.
 
      --enable-ip-alias
-        Enable use of alias IPs
-        (https://cloud.google.com/compute/docs/alias-ip/) for Pod IPs. This
-        will require at least two secondary ranges in the subnetwork, one for
-        the pod IPs and another to reserve space for the services range.
+        --enable-ip-alias creates a VPC-native cluster. If you set this option,
+        you can optionally specify the IP address ranges to use for Pods and
+        Services. For instructions, see
+        https://cloud.google.com/kubernetes-engine/docs/how-to/alias-ips.
+
+        --no-enable-ip-alias creates a routes-based cluster. This type of
+        cluster routes traffic between Pods using Google Cloud Routes. This
+        option is not recommended; use the default VPC-native cluster type
+        instead. For instructions, see
+        https://cloud.google.com/kubernetes-engine/docs/how-to/routes-based-cluster
+
+        You can't specify both --enable-ip-alias and --no-enable-ip-alias. If
+        you omit both --enable-ip-alias and --no-enable-ip-alias, the default
+        is a VPC-native cluster.
 
      --enable-kubernetes-alpha
         Enable Kubernetes alpha features on this cluster. Selecting this option