[[["わかりやすい","easyToUnderstand","thumb-up"],["問題の解決に役立った","solvedMyProblem","thumb-up"],["その他","otherUp","thumb-up"]],[["わかりにくい","hardToUnderstand","thumb-down"],["情報またはサンプルコードが不正確","incorrectInformationOrSampleCode","thumb-down"],["必要な情報 / サンプルがない","missingTheInformationSamplesINeed","thumb-down"],["翻訳に関する問題","translationIssue","thumb-down"],["その他","otherDown","thumb-down"]],["最終更新日 2025-02-11 UTC。"],[[["\u003cp\u003eYou can configure how container images are built when running or debugging applications on Kubernetes through the "Develop on Kubernetes" run configuration.\u003c/p\u003e\n"],["\u003cp\u003eCloud Code supports various builders like Docker, Jib, and Buildpacks, and the selection can be made through the UI if a \u003ccode\u003eskaffold.yaml\u003c/code\u003e file is not present.\u003c/p\u003e\n"],["\u003cp\u003eBuilding locally uses your own resources and is free, while Cloud Build is suitable for slower machines or different processor architectures, and is cost-based.\u003c/p\u003e\n"],["\u003cp\u003eSkaffold profiles enable the configuration of different build or deployment environments and can be added to your \u003ccode\u003elaunch.json\u003c/code\u003e file for multiple profile use.\u003c/p\u003e\n"],["\u003cp\u003eWhen importing or running an application without a \u003ccode\u003eskaffold.yaml\u003c/code\u003e file, you will be prompted to specify settings during initialization via the Cloud Code UI, and the settings will be saved to a \u003ccode\u003eskaffold.yaml\u003c/code\u003e file.\u003c/p\u003e\n"]]],[],null,["# Explore your build options with buildpacks, Jib, or Docker\n\nTo run or debug an application on Kubernetes, you'll need to set your\npreference for how your container image is built by configuring it in the\n**Develop on Kubernetes** run configuration.\n\nIn a project that doesn't contain a `skaffold.yaml` file at the root or doesn't\nreference `skaffold.yaml` you can use the Cloud Code UI to choose\na builder and build environment.\n\nBuilding locally is free of charge since it uses your own resources. Building\nwith [Cloud Build](/build) is good for slower machines or machines that\ndon't match the processor architecture of the target cluster. For information\nabout the cost of building your application using Cloud Build, see\n[Cloud Build Pricing](/build/pricing).\n\nSpecify how your images are built\n---------------------------------\n\nCloud Code supports\n[Docker](https://skaffold.dev/docs/pipeline-stages/builders/docker/),\n[Jib](https://skaffold.dev/docs/pipeline-stages/builders/jib/), and\n[Buildpacks](https://skaffold.dev/docs/pipeline-stages/builders/buildpacks/)\n[artifact types](https://skaffold.dev/docs/builders/).\n\n### Without a skaffold.yaml\n\nWhen importing an existing application without a `skaffold.yaml` file or running\nan application that doesn't have a `skaffold.yaml`, you're prompted to specify\nsettings when initializing.\n\nIf you're using one of the Cloud Code sample applications, to use\nthe UI, delete the `skaffold.yaml` file before running a build action. For steps\nto choose a builder and build environment without the UI, see\n[Manually creating a Skaffold configuration](/code/docs/vscode/use-existing-kubernetes-app#manually_create_a_skaffold_configuration).\n\n1. In a project without a `skaffold.yaml` file, open the command palette (press `Ctrl`/`Cmd`+`Shift`+`P` or click **View** \\\u003e **Command Palette** ) and then run **Cloud Code: Run on Kubernetes** or **Cloud Code: Debug on Kubernetes**.\n2. In the **Build environment** section, choose a build environment.\n3. In the **Deploy settings** section, if you chose Cloud Build, specify the image registry you want Cloud Build to push images to.\n4. In the **Build settings** section, specify a builder (Docker, Jib, or buildpacks) for each image and its settings.\n5. Select or clear any of the configuration options and then click **Debug** or **Run**.\n\nThe options you choose are saved to a\n[`skaffold.yaml`](https://skaffold.dev/docs/references/yaml) file that you can\nedit directly for further customization.\n\n### With an existing skaffold.yaml\n\nFor a project with an existing `skaffold.yaml` file, you need to manually edit your build options. Cloud Code provides snippets for common YAML schema viewable by pressing `Command/Ctrl + Space`. See the the [Skaffold Build documentation](https://skaffold.dev/docs/builders/) for more details.\n\nUse Skaffold profiles in Cloud Code\n-----------------------------------\n\nCloud Code uses the Skaffold tool under the hood to power Cloud Code's build functionality. To configure Cloud Code for different build or deploy environments such as local or remote builds, [Skaffold profiles](https://skaffold.dev/docs/environment/profiles/) are used\n\nCreate a new skaffold profile\n-----------------------------\n\nIf you'd like to define build, test and deployment configurations for\ndifferent contexts, you can have different Skaffold profiles.\nThe following sample shows a profile named `cloudbuild` used to to build images with Cloud Build:\n\n\u003cbr /\u003e\n\n profiles:\n # use the cloudbuild profile to build images using Google Cloud Build\n - name: cloudbuild\n build:\n googleCloudBuild: {}\n\nIf you have multiple profiles, add the profile you want to use to your `launch.json` file. For more information on Skaffold profiles, see the [Skaffold profiles documentation](https://skaffold.dev/docs/environment/profiles/)\n\n\u003cbr /\u003e\n\nWhat's next\n-----------\n\n- Use [file sync and hot reloading](/code/docs/vscode/speed-up-k8s-development#enable-skaffold-file-sync-and-hot-reloading) to speed up development.\n- Learn more about [Cloud Native Buildpacks](https://buildpacks.io/).\n- Read about the benefits of [Cloud Build](/build)."]]
