gcloud alpha local setup

gcloud alpha local setup - command for creating a skaffold local development environment
gcloud alpha local setup [--build-context-directory=BUILD_CONTEXT_DIRECTORY] [--builder=BUILDER] [--dockerfile=DOCKERFILE; default="Dockerfile"] [--image-name=IMAGE_NAME] [--kubernetes-file=KUBERNETES_FILE; default="pods_and_services.yaml"] [--local-port=LOCAL_PORT] [--service-account=SERVICE_ACCOUNT] [--service-name=SERVICE_NAME] [--skaffold-file=SKAFFOLD_FILE; default="skaffold.yaml"] [GCLOUD_WIDE_FLAG]
(ALPHA) Command for creating a skaffold local development environment.
If set, use this as the context directory when building the container image. Otherwise, the directory of the Dockerfile will be used.
Build with a given Cloud Native Computing Foundation Buildpack builder.
--dockerfile=DOCKERFILE; default="Dockerfile"
Dockerfile for the service image.
Name for the built docker image.
--kubernetes-file=KUBERNETES_FILE; default="pods_and_services.yaml"
File containing yaml specifications for kubernetes resources.
Local port to which the service connection is forwarded. If this flag is not set, then a random port is chosen.
When connecting to Google Cloud Platform services, use a service account key.
Name of the service.
--skaffold-file=SKAFFOLD_FILE; default="skaffold.yaml"
Location of the generated skaffold.yaml file.
These flags are available to all commands: --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.

This command is currently in ALPHA and may change without notice. If this command fails with API permission errors despite specifying the right project, you may be trying to access an API with an invitation-only early access whitelist.
Was this page helpful? Let us know how we did:

Send feedback about...

Cloud SDK: Command Line Interface