imjasonh/gcloud-help
1
0
Fork 0
mirror of https://github.com/imjasonh/gcloud-help synced 2026-07-18 14:56:05 +00:00
Code Activity

gcloud: Wed Jan 10 10:17:49 UTC 2024

Browse source
This commit is contained in:
Automated 2024-01-10 10:17:49 +00:00
parent 08ad88258a
commit 5fec13c692
262 changed files with 3211 additions and 4501 deletions
Download patch file Download diff file Expand all files Collapse all files

104
gcloud/container/binauthz/attestations/create
View file

@ -5,8 +5,10 @@ NAME
SYNOPSIS
gcloud container binauthz attestations create --artifact-url=ARTIFACT_URL
--public-key-id=PUBLIC_KEY_ID --signature-file=SIGNATURE_FILE
(--attestor=ATTESTOR : --attestor-project=ATTESTOR_PROJECT)
[--payload-file=PAYLOAD_FILE] [--validate] [GCLOUD_WIDE_FLAG ...]
[--payload-file=PAYLOAD_FILE]
[[--note=NOTE : --note-project=NOTE_PROJECT]
| --validate [--attestor=ATTESTOR
: --attestor-project=ATTESTOR_PROJECT]] [GCLOUD_WIDE_FLAG ...]
DESCRIPTION
This command creates a Binary Authorization attestation for your project.
@ -24,6 +26,15 @@ EXAMPLES
--signature-file=signed_artifact_attestation.pgp.sig \
--public-key-id=AAAA0000000000000000FFFFFFFFFFFFFFFFFFFF
To create an attestation in the project "my_proj" in note
"projects/foo/notes/bar", run:
$ gcloud container binauthz attestations create --project=my_proj \
--artifact-url='gcr.io/example-project/example-image@sha256:abcd\
' --note=projects/foo/notes/bar \
--signature-file=signed_artifact_attestation.pgp.sig \
--public-key-id=AAAA0000000000000000FFFFFFFFFFFFFFFFFFFF
REQUIRED FLAGS
--artifact-url=ARTIFACT_URL
Container URL. May be in the gcr.io/repository/image format, or may
@ -42,35 +53,6 @@ REQUIRED FLAGS
Path to file containing the signature to store, or - to read signature
from stdin.
Attestor resource - The Attestor whose Container Analysis Note will be
used to host the created attestation. In order to successfully attach the
attestation, the active gcloud account (core/account) must be able to read
this attestor and must have the containeranalysis.notes.attachOccurrence
permission for the Attestor's underlying Note resource (usually via the
containeranalysis.notes.attacher role). The arguments in this group can be
used to specify the attributes of this resource.
This must be specified.
--attestor=ATTESTOR
ID of the attestor or fully qualified identifier for the attestor.
To set the name attribute:
▸ provide the argument --attestor on the command line.
This flag argument must be specified if any of the other arguments in
this group are specified.
--attestor-project=ATTESTOR_PROJECT
Project ID of the Google Cloud project for the attestor.
To set the project attribute:
▸ provide the argument --attestor on the command line with a fully
specified name;
▸ provide the argument --attestor-project on the command line;
▸ provide the argument --project on the command line;
▸ set the property core/project.
OPTIONAL FLAGS
--payload-file=PAYLOAD_FILE
Path to file containing the payload over which the signature was
@ -84,9 +66,63 @@ OPTIONAL FLAGS
formatting, you must explicitly provide the payload content via this
flag.
--validate
Whether to validate that the Attestation can be verified by the
provided Attestor.
At most one of these can be specified:
Note resource - The Container Analysis Note which will be used to host
the created attestation. In order to successfully attach the
attestation, the active gcloud account (core/account) must have the
containeranalysis.notes.attachOccurrence permission for the Note
(usually via the containeranalysis.notes.attacher role). The arguments
in this group can be used to specify the attributes of this resource.
--note=NOTE
ID of the note or fully qualified identifier for the note.
To set the note attribute:
▫ provide the argument --note on the command line.
This flag argument must be specified if any of the other arguments
in this group are specified.
--note-project=NOTE_PROJECT
The Container Analysis project for the note.
To set the project attribute:
▫ provide the argument --note on the command line with a fully
specified name;
▫ provide the argument --note-project on the command line.
--validate
Whether to validate that the Attestation can be verified by the
provided Attestor.
Attestor resource - The Attestor whose Container Analysis Note will be
used to host the created attestation. In order to successfully attach
the attestation, the active gcloud account (core/account) must be able
to read this attestor and must have the
containeranalysis.notes.attachOccurrence permission for the Attestor's
underlying Note resource (usually via the
containeranalysis.notes.attacher role). The arguments in this group can
be used to specify the attributes of this resource.
--attestor=ATTESTOR
ID of the attestor or fully qualified identifier for the attestor.
To set the name attribute:
▫ provide the argument --attestor on the command line.
This flag argument must be specified if any of the other arguments
in this group are specified.
--attestor-project=ATTESTOR_PROJECT
Project ID of the Google Cloud project for the attestor.
To set the project attribute:
▫ provide the argument --attestor on the command line with a
fully specified name;
▫ provide the argument --attestor-project on the command line;
▫ provide the argument --project on the command line;
▫ set the property core/project.
GCLOUD WIDE FLAGS
These flags are available to all commands: --access-token-file, --account,

4
gcloud/container/binauthz/attestors/create
View file

@ -34,8 +34,8 @@ POSITIONAL ARGUMENTS
▸ provide the argument ATTESTOR on the command line.
REQUIRED FLAGS
Note resource - The Container Analysis ATTESTATION_AUTHORITY Note to which
the created attestor will be bound.
Note resource - The Container Analysis Note to which the created attestor
will be bound.
For the attestor to be able to access and use the Note, the Note must
exist and the active gcloud account (core/account) must have the

11
gcloud/container/clusters/create
View file

@ -676,7 +676,7 @@ FLAGS
The maximum number of nodes to allocate per default initial node pool.
Kubernetes Engine will automatically create enough nodes pools such
that each node pool contains less than --max-nodes-per-pool nodes.
Defaults to 1000 nodes, but can be set as low as 100 nodes per pool on
Defaults to 2000 nodes, but can be set as low as 100 nodes per pool on
initial create.
--max-pods-per-node=MAX_PODS_PER_NODE
@ -1251,8 +1251,8 @@ FLAGS
At most one of these can be specified:
--dataplane-v2-observability-mode=DATAPLANE_V2_OBSERVABILITY_MODE
Select Advanced Datapath Observability mode for the cluster. Defaults
to DISABLED.
(DEPRECATED) Select Advanced Datapath Observability mode for the
cluster. Defaults to DISABLED.
Advanced Datapath Observability allows for a real-time view into
pod-to-pod traffic within your cluster.
@ -1268,6 +1268,11 @@ FLAGS
$ gcloud container clusters create \
--dataplane-v2-observability-mode=EXTERNAL_LB
The --dataplane-v2-observability-mode flag is deprecated and will be
removed in an upcoming release. Please use
--enable-dataplane-v2-flow-observability or
--disable-dataplane-v2-flow-observability.
DATAPLANE_V2_OBSERVABILITY_MODE must be one of:
DISABLED

18
gcloud/container/clusters/create-auto
View file

@ -236,16 +236,21 @@ FLAGS
--logging=[COMPONENT,...]
Set the components that have logging enabled. Valid component values
are: SYSTEM, WORKLOAD, API_SERVER, CONTROLLER_MANAGER, SCHEDULER, NONE
are: SYSTEM, WORKLOAD, API_SERVER, CONTROLLER_MANAGER, SCHEDULER
The default is SYSTEM,WORKLOAD. If this flag is set, then SYSTEM must
be included.
For more information, see
https://cloud.google.com/stackdriver/docs/solutions/gke/installing#available-logs
Examples:
$ gcloud container clusters create-auto --logging=SYSTEM
$ gcloud container clusters create-auto --logging=SYSTEM,WORKLOAD
$ gcloud container clusters create-auto \
--logging=SYSTEM,API_SERVER,WORKLOAD
--logging=SYSTEM,WORKLOAD,API_SERVER,CONTROLLER_MANAGER,\
SCHEDULER
--monitoring=[COMPONENT,...]
Set the components that have monitoring enabled. Valid component values
@ -383,8 +388,8 @@ FLAGS
At most one of these can be specified:
--dataplane-v2-observability-mode=DATAPLANE_V2_OBSERVABILITY_MODE
Select Advanced Datapath Observability mode for the cluster. Defaults
to DISABLED.
(DEPRECATED) Select Advanced Datapath Observability mode for the
cluster. Defaults to DISABLED.
Advanced Datapath Observability allows for a real-time view into
pod-to-pod traffic within your cluster.
@ -400,6 +405,11 @@ FLAGS
$ gcloud container clusters create-auto \
--dataplane-v2-observability-mode=EXTERNAL_LB
The --dataplane-v2-observability-mode flag is deprecated and will be
removed in an upcoming release. Please use
--enable-dataplane-v2-flow-observability or
--disable-dataplane-v2-flow-observability.
DATAPLANE_V2_OBSERVABILITY_MODE must be one of:
DISABLED

9
gcloud/container/clusters/update
View file

@ -859,8 +859,8 @@ REQUIRED FLAGS
At most one of these can be specified:
--dataplane-v2-observability-mode=DATAPLANE_V2_OBSERVABILITY_MODE
Select Advanced Datapath Observability mode for the cluster.
Defaults to DISABLED.
(DEPRECATED) Select Advanced Datapath Observability mode for the
cluster. Defaults to DISABLED.
Advanced Datapath Observability allows for a real-time view into
pod-to-pod traffic within your cluster.
@ -876,6 +876,11 @@ REQUIRED FLAGS
$ gcloud container clusters update \
--dataplane-v2-observability-mode=EXTERNAL_LB
The --dataplane-v2-observability-mode flag is deprecated and will
be removed in an upcoming release. Please use
--enable-dataplane-v2-flow-observability or
--disable-dataplane-v2-flow-observability.
DATAPLANE_V2_OBSERVABILITY_MODE must be one of:
DISABLED