1
0
Fork 0
mirror of https://github.com/imjasonh/gcloud-help synced 2026-07-13 00:18:35 +00:00

gcloud: Wed Feb 8 10:13:59 UTC 2023

This commit is contained in:
Automated 2023-02-08 10:13:59 +00:00
parent fc11b54760
commit 11068cb123
240 changed files with 8982 additions and 619 deletions

View file

@ -3,8 +3,8 @@ NAME
SYNOPSIS
gcloud container azure clients create (CLIENT : --location=LOCATION)
--application-id=APP_ID --tenant-id=TENANT_ID [--validate-only]
[GCLOUD_WIDE_FLAG ...]
--application-id=APP_ID --tenant-id=TENANT_ID [--async]
[--validate-only] [GCLOUD_WIDE_FLAG ...]
DESCRIPTION
Create an Azure client.
@ -52,6 +52,10 @@ REQUIRED FLAGS
client.
OPTIONAL FLAGS
--async
Return immediately, without waiting for the operation in progress to
complete.
--validate-only
Validate the creation of the client, but don't actually perform it.

View file

@ -3,7 +3,7 @@ NAME
SYNOPSIS
gcloud container azure clients delete (CLIENT : --location=LOCATION)
[--allow-missing] [GCLOUD_WIDE_FLAG ...]
[--allow-missing] [--async] [GCLOUD_WIDE_FLAG ...]
DESCRIPTION
Delete an Azure client.
@ -45,6 +45,10 @@ FLAGS
Allow idempotent deletion of cluster. The request will still succeed in
case the cluster does not exist.
--async
Return immediately, without waiting for the operation in progress to
complete.
GCLOUD WIDE FLAGS
These flags are available to all commands: --access-token-file, --account,
--billing-project, --configuration, --flags-file, --flatten, --format,

View file

@ -45,72 +45,73 @@ DESCRIPTION
avaible.
EXAMPLES
Register a non-GKE or GKE On-Prem cluster referenced from a specific kubeconfig file, and install the Connect agent:
Register a non-GKE or GKE On-Prem cluster referenced from a specific
kubeconfig file, and install the Connect agent:
$ gcloud container fleet memberships register my-cluster \
--context=my-cluster-context \
--kubeconfig=/home/user/custom_kubeconfig \
--service-account-key-file=/tmp/keyfile.json
--context=my-cluster-context \
--kubeconfig=/home/user/custom_kubeconfig \
--service-account-key-file=/tmp/keyfile.json
Register a non-GKE or GKE On-Prem cluster referenced from the default
kubeconfig file, and install the Connect agent:
Register a non-GKE or GKE On-Prem cluster referenced from the default
kubeconfig file, and install the Connect agent:
$ gcloud container fleet memberships register my-cluster \
--context=my-cluster-context \
--service-account-key-file=/tmp/keyfile.json
--context=my-cluster-context \
--service-account-key-file=/tmp/keyfile.json
Register a non-GKE or GKE On-Prem cluster, and install a specific version
of the Connect agent:
Register a non-GKE or GKE On-Prem cluster, and install a specific version
of the Connect agent:
$ gcloud container fleet memberships register my-cluster \
--context=my-cluster-context \
--version=gkeconnect_20190802_02_00 \
--service-account-key-file=/tmp/keyfile.json
--context=my-cluster-context \
--version=gkeconnect_20190802_02_00 \
--service-account-key-file=/tmp/keyfile.json
Register a non-GKE or GKE On-Prem cluster and output a manifest that can be
used to install the Connect agent:
Register a non-GKE or GKE On-Prem cluster and output a manifest that can be
used to install the Connect agent:
$ gcloud container fleet memberships register my-cluster \
--context=my-cluster-context \
--manifest-output-file=/tmp/manifest.yaml \
--service-account-key-file=/tmp/keyfile.json
--context=my-cluster-context \
--manifest-output-file=/tmp/manifest.yaml \
--service-account-key-file=/tmp/keyfile.json
Register a GKE cluster referenced from a GKE URI:
Register a GKE cluster referenced from a GKE URI:
$ gcloud container fleet memberships register my-cluster \
--gke-uri=my-cluster-gke-uri
--gke-uri=my-cluster-gke-uri
Register a GKE cluster referenced from a GKE URI, and install the Connect
agent using service account key file:
$ gcloud container fleet memberships register my-cluster \
--gke-uri=my-cluster-gke-uri --install-connect-agent \
--service-account-key-file=/tmp/keyfile.json
--gke-uri=my-cluster-gke-uri --install-connect-agent \
--service-account-key-file=/tmp/keyfile.json
Register a GKE cluster first, and install the Connect agent later.
Register a GKE cluster first, and install the Connect agent later.
$ gcloud container fleet memberships register my-cluster \
--gke-cluster=my-cluster-region-or-zone/my-cluster
--gke-cluster=my-cluster-region-or-zone/my-cluster
$ gcloud container fleet memberships register my-cluster \
--gke-cluster=my-cluster-region-or-zone/my-cluster \
--install-connect-agent --enable-workload-identity
--gke-cluster=my-cluster-region-or-zone/my-cluster \
--install-connect-agent --enable-workload-identity
Register a GKE cluster, and install a specific version of the Connect
agent:
Register a GKE cluster, and install a specific version of the Connect
agent:
$ gcloud container fleet memberships register my-cluster \
--gke-cluster=my-cluster-region-or-zone/my-cluster \
--install-connect-agent --version=20220819-00-00 \
--service-account-key-file=/tmp/keyfile.json
--gke-cluster=my-cluster-region-or-zone/my-cluster \
--install-connect-agent --version=20220819-00-00 \
--service-account-key-file=/tmp/keyfile.json
Register a GKE cluster and output a manifest that can be used to install the
Connect agent:
Register a GKE cluster and output a manifest that can be used to install
the Connect agent:
$ gcloud container fleet memberships register my-cluster \
--gke-uri=my-cluster-gke-uri --install-connect-agent \
--manifest-output-file=/tmp/manifest.yaml \
--service-account-key-file=/tmp/keyfile.json
--gke-uri=my-cluster-gke-uri --install-connect-agent \
--manifest-output-file=/tmp/manifest.yaml \
--service-account-key-file=/tmp/keyfile.json
POSITIONAL ARGUMENTS
MEMBERSHIP_NAME

View file

@ -44,72 +44,73 @@ DESCRIPTION
avaible.
EXAMPLES
Register a non-GKE or GKE On-Prem cluster referenced from a specific kubeconfig file, and install the Connect agent:
Register a non-GKE or GKE On-Prem cluster referenced from a specific
kubeconfig file, and install the Connect agent:
$ gcloud container hub memberships register my-cluster \
--context=my-cluster-context \
--kubeconfig=/home/user/custom_kubeconfig \
--service-account-key-file=/tmp/keyfile.json
--context=my-cluster-context \
--kubeconfig=/home/user/custom_kubeconfig \
--service-account-key-file=/tmp/keyfile.json
Register a non-GKE or GKE On-Prem cluster referenced from the default
kubeconfig file, and install the Connect agent:
Register a non-GKE or GKE On-Prem cluster referenced from the default
kubeconfig file, and install the Connect agent:
$ gcloud container hub memberships register my-cluster \
--context=my-cluster-context \
--service-account-key-file=/tmp/keyfile.json
--context=my-cluster-context \
--service-account-key-file=/tmp/keyfile.json
Register a non-GKE or GKE On-Prem cluster, and install a specific version
of the Connect agent:
Register a non-GKE or GKE On-Prem cluster, and install a specific version
of the Connect agent:
$ gcloud container hub memberships register my-cluster \
--context=my-cluster-context \
--version=gkeconnect_20190802_02_00 \
--service-account-key-file=/tmp/keyfile.json
--context=my-cluster-context \
--version=gkeconnect_20190802_02_00 \
--service-account-key-file=/tmp/keyfile.json
Register a non-GKE or GKE On-Prem cluster and output a manifest that can be
used to install the Connect agent:
Register a non-GKE or GKE On-Prem cluster and output a manifest that can be
used to install the Connect agent:
$ gcloud container hub memberships register my-cluster \
--context=my-cluster-context \
--manifest-output-file=/tmp/manifest.yaml \
--service-account-key-file=/tmp/keyfile.json
--context=my-cluster-context \
--manifest-output-file=/tmp/manifest.yaml \
--service-account-key-file=/tmp/keyfile.json
Register a GKE cluster referenced from a GKE URI:
Register a GKE cluster referenced from a GKE URI:
$ gcloud container hub memberships register my-cluster \
--gke-uri=my-cluster-gke-uri
--gke-uri=my-cluster-gke-uri
Register a GKE cluster referenced from a GKE URI, and install the Connect
agent using service account key file:
$ gcloud container hub memberships register my-cluster \
--gke-uri=my-cluster-gke-uri --install-connect-agent \
--service-account-key-file=/tmp/keyfile.json
--gke-uri=my-cluster-gke-uri --install-connect-agent \
--service-account-key-file=/tmp/keyfile.json
Register a GKE cluster first, and install the Connect agent later.
Register a GKE cluster first, and install the Connect agent later.
$ gcloud container hub memberships register my-cluster \
--gke-cluster=my-cluster-region-or-zone/my-cluster
--gke-cluster=my-cluster-region-or-zone/my-cluster
$ gcloud container hub memberships register my-cluster \
--gke-cluster=my-cluster-region-or-zone/my-cluster \
--install-connect-agent --enable-workload-identity
--gke-cluster=my-cluster-region-or-zone/my-cluster \
--install-connect-agent --enable-workload-identity
Register a GKE cluster, and install a specific version of the Connect
agent:
Register a GKE cluster, and install a specific version of the Connect
agent:
$ gcloud container hub memberships register my-cluster \
--gke-cluster=my-cluster-region-or-zone/my-cluster \
--install-connect-agent --version=20220819-00-00 \
--service-account-key-file=/tmp/keyfile.json
--gke-cluster=my-cluster-region-or-zone/my-cluster \
--install-connect-agent --version=20220819-00-00 \
--service-account-key-file=/tmp/keyfile.json
Register a GKE cluster and output a manifest that can be used to install the
Connect agent:
Register a GKE cluster and output a manifest that can be used to install
the Connect agent:
$ gcloud container hub memberships register my-cluster \
--gke-uri=my-cluster-gke-uri --install-connect-agent \
--manifest-output-file=/tmp/manifest.yaml \
--service-account-key-file=/tmp/keyfile.json
--gke-uri=my-cluster-gke-uri --install-connect-agent \
--manifest-output-file=/tmp/manifest.yaml \
--service-account-key-file=/tmp/keyfile.json
POSITIONAL ARGUMENTS
MEMBERSHIP_NAME