gcloud alpha container fleet cloudrun apply

NAME
gcloud alpha container fleet cloudrun apply - deploy or update the CloudRun feature
SYNOPSIS
gcloud alpha container fleet cloudrun apply (--gke-cluster=LOCATION/CLUSTER_NAME     | --gke-uri=GKE_URI     | [--context=CONTEXT : --kubeconfig=KUBECONFIG]) [--config=CONFIG] [GCLOUD_WIDE_FLAG]
DESCRIPTION
(ALPHA) Deploy or update a user-specified config file of the CloudRun custom resource. The config file should be a YAML file.
EXAMPLES
To apply the CloudRun YAML file, run:
gcloud alpha container fleet cloudrun apply --kubeconfig=/path/to/kubeconfig --config=/path/to/cloud-run-cr.yaml
REQUIRED FLAGS
Cluster identifier.

Exactly one of these must be specified:

--gke-cluster=LOCATION/CLUSTER_NAME
The location/name of the GKE cluster. The location can be a zone or a region for e.g us-central1-a/my-cluster.
--gke-uri=GKE_URI
The URI of a GKE cluster that you want to register to Hub; for example, 'https://container.googleapis.com/v1/projects/my-project/locations/us-central1-a/clusters/my-cluster'. To obtain the URI, you can run 'gcloud container clusters list --uri'. Note that this should only be provided if the cluster being registered is a GKE cluster. The service will validate the provided URI to confirm that it maps to a valid GKE cluster."
Non-GKE cluster identifier.
--context=CONTEXT
The cluster context as it appears in the kubeconfig file. You can get this value from the command line by running command: kubectl config current-context.

This flag argument must be specified if any of the other arguments in this group are specified.

--kubeconfig=KUBECONFIG
The kubeconfig file containing an entry for the cluster. Defaults to $KUBECONFIG if it is set in the environment, otherwise defaults to $HOME/.kube/config.
OPTIONAL FLAGS
--config=CONFIG
The path to CloudRun custom resource config file.
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.

NOTES
This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early access allowlist. These variants are also available:
gcloud container fleet cloudrun apply
gcloud beta container fleet cloudrun apply