[[["易于理解","easyToUnderstand","thumb-up"],["解决了我的问题","solvedMyProblem","thumb-up"],["其他","otherUp","thumb-up"]],[["很难理解","hardToUnderstand","thumb-down"],["信息或示例代码不正确","incorrectInformationOrSampleCode","thumb-down"],["没有我需要的信息/示例","missingTheInformationSamplesINeed","thumb-down"],["翻译问题","translationIssue","thumb-down"],["其他","otherDown","thumb-down"]],["最后更新时间 (UTC):2025-09-03。"],[],[],null,["# Setting up the technical components\n\nThis page outlines how to create the key technical components required for\ndistributing your container image product with Google Cloud Marketplace.\n\nIf you have questions during the onboarding process, talk to your\nCloud Marketplace Partner Engineer. If you don't know who your assigned\nPartner Engineer is, use the\n[Partner Support Desk](https://g.co/cloud/psd-partner) to request assistance,\nand include the word \"Marketplace\" in your description. For more information\nabout Partner Support Desk, visit\n[Request assistance with Cloud Marketplace](/marketplace/docs/partners/get-support).\n\nArtifact Registry and IAM setup\n-------------------------------\n\nBefore you can create your product in Producer Portal,\nyou need to create a staging Artifact Registry repository and push\nthe images you want to distribute in your product to that repository. In\nyour project, you must grant the Project Editor role to\n`cloud-commerce-marketplace-onboarding@twosync-src.google.com`.\n\n### Getting started with Container Registry\n\nTo push tagged container images to Container Registry, follow the\nsteps in **Before you begin** in the\n[Artifact Registry documentation](/container-registry/docs/quickstart#before-you-begin).\nThen use the steps below to enable the Artifact Analysis API.\n| **For existing VM partners**: Your staging Artifact Registry repository can be within your dev project instead of your public project.\n\nAfter you install `gcloud` and Docker, you must enable the following APIs\nfrom the\n[API Library page](https://console.cloud.google.com/apis/library?&q=Container):\n\n- Artifact Registry API\n- Artifact Analysis API\n\nThe Artifact Registry API lets you to push to\nArtifact Registry, and the Artifact Analysis API allows for\nsecurity scanning.\n\nIf you have trouble accessing either of these APIs, contact your Partner\nEngineer.\n\n### Tagging and pushing images\n\n1. Choose your Artifact Registry staging repository path. It is\n recommended that your repository follow the structure\n `us-docker.pkg.dev/`\u003cvar translate=\"no\"\u003eYOUR-PARTNER-ID\u003c/var\u003e`/`\u003cvar translate=\"no\"\u003eYOUR-SOLUTION-ID\u003c/var\u003e.\n\n - Staging repository must be within `us-docker.pkg.dev` or `gcr.io` (other regions, such as `europe-docker.pkg.dev` or `eu.gcr.io`, are not yet supported).\n - Save or copy your staging repository path for product creation in Producer Portal.\n2. Build the image you want to push to your Artifact Registry staging\n repository.\n\n3. Tag the image via Docker with `latest`.\n\n `docker tag `\u003cvar translate=\"no\"\u003eimage_name\u003c/var\u003e` `\u003cvar translate=\"no\"\u003estaging_repo_path\u003c/var\u003e`:tag`\n\n For example,\n `docker tag test-image us-docker.pkg.dev/testpartner/testsolution:latest`\n\n Note that the image tagged `latest` is pulled if a user does not specify a\n tag.\n4. Push your image using `gcloud`:\n\n `gcloud docker push `\u003cvar translate=\"no\"\u003estaging_repo_path\u003c/var\u003e`:tag`\n5. Repeat for any additional tags or images you'd like to add to your staging\n repository. A single image may have multiple tags.\n\n - Remember that pushing an image to your staging repository won't automatically make it visible to users; this only happens to the images of the tags that you select, after they are published.\n - A repository's scope is the single level of the folder its path specifies. Any images which are within another folder in the repository are not actually in the repository itself. In other words, if an image is in `us-docker.pkg.dev/testpartner/testsolution/1.0`, it is NOT in the `us-docker.pkg.dev/testpartner/testsolution` repository. `us-docker.pkg.dev/testpartner/testsolution/1.0` is a separate repository.\n\nCreating your product in Producer Portal\n----------------------------------------\n\nThis section describes how to create and publish your container image product in\nProducer Portal.\n\nTo publish your product in Producer Portal, you create an entry for your\nproduct, and then you submit the following information for review:\n\n- **Product details**: Add listing and marketing information about your product.\n- **Container images**: Provide the Google Container Registry repository that includes your container images.\n\nYou can submit these reviews at any time and in any order.\n\nTo create your product's Cloud Marketplace entry:\n\n1. Open Producer Portal in the Google Cloud console:\n\n ```\n https://console.cloud.google.com/producer-portal?project=YOUR_PUBLIC_PROJECT_ID\n ```\n\n Replace \u003cvar translate=\"no\"\u003eYOUR_PUBLIC_PROJECT_ID\u003c/var\u003e with the ID for the public\n project that you created for Cloud Marketplace---for example,\n `my-organization-public`.\n | **Note:** If you don't see the link, or can't access the URL, verify that you've selected the correct project and have the Editor (`roles/editor`) role for the project. If you still can't access the URL, use the [Partner Support Desk](https://g.co/cloud/psd-partner) to request assistance, and include the word \"Marketplace\" in your description. For more information about Partner Support Desk, visit [Request assistance with Cloud Marketplace](/marketplace/docs/partners/get-support).\n2. At the top of the page, click **Add product**.\n\n3. Select **Container image**.\n\n4. Under **Product name**, name your product and check the Product ID. The\n Product ID is used in the URL for your Cloud Marketplace listing.\n\n | **Caution:** The Product ID and product type cannot be changed after the product is created. You can change your product name before you submit it.\n5. Click **Create**. It might take a few seconds to create your product.\n\n### Adding product details\n\nThe product details include your product listing on Cloud Marketplace,\nmarketing information, and links to documentation.\n\nTo add your product details:\n\n1. In the list of products, click the product ID.\n\n2. On the **Overview** page of your product, go to **Product details** ,\n and click **Edit**.\n\n3. Complete the **PRODUCT INFO** tab of the **Product details** section. While\n completing **PRODUCT INFO**, you can add Category IDs. Category IDs allow\n customers to find your product under select categories or filters as they\n search Cloud Marketplace.\n\n4. To add tutorials, documentation, and, optionally, additional\n license agreements, complete the **DOCUMENTATION** tab of the **Product\n details** section. Your documentation must meet the\n [requirements for user guides](/marketplace/docs/partners/kubernetes/create-app-package#user-guide).\n\n5. To add search metadata or keywords, or to customize the URL of the details\n page for your product, complete the **PRODUCT METADATA** tab of the\n **Product details** section.\n\n6. When you are ready to submit your product details for processing, click\n **Submit**.\n\nIt takes approximately 2-5 days for the Partner Engineering team\nto review and approve your product details. You can start editing details now\nand submit the review later.\n\n### Adding your container images\n\nYou're required to create one version corresponding to the Container\nRegistry tag `latest` (case-sensitive). This is the default version in\nproduct page.\n\nTo add your container images:\n\n1. In the list of products, click the product ID.\n\n2. On the **Overview** page of your product, go to **Container images** ,\n and click **Edit**.\n\n3. In the **Container images** section, enter the URL for your staging\n Artifact Registry repository.\n\n4. Click **Specify Release**. It might take a few seconds to read the\n repository and load your tags.\n\n5. Select the **Display tag** for the release you want to include in your\n product. You must include the `latest` release in your product, but\n you can add additional versions. We recommend limiting the number of\n releases available to your product for your users' convenience.\n\n6. Optionally add a **Version title** and a short description of the release.\n These help your users deploy the version they want.\n\n7. Enter operating system that this release supports. You can specify the\n operating system version, if necessary.\n\n8. After you've added all the information for the release, click **Done**.\n\n9. To add another version, click **Add Release**, and enter the information\n for that release.\n\n10. When you're done adding supported releases to your product, click\n **Save and Validate**. The images are copied into a public repository,\n and then we run a series of tests against the images.\n\n11. Click **Submit** to submit the container images for review.\n\n### Preview your container image product\n\nTo preview your Cloud Marketplace listing before it's visible to users:\n\n1. In the list of products, click the product ID.\n\n2. On the **Overview** page of your product, click **Full preview**.\n\nIf you've changed any tags in your staging repository since you validated your\ncontainer images in Producer Portal, the images referenced in the preview might\nbe inaccurate.\n\n### Publish your container image product\n\nTo publish your product on Cloud Marketplace, you must:\n\n- Complete the **Product details** and **Container images** reviews.\n\n- Be approved as a\n [Google Cloud Build partner](/partners/become-a-partner).\n\nAfter all reviews have been approved, you can publish and launch the product\nwithin a few minutes. To publish your product:\n\n1. In the list of products, click the product ID.\n\n2. On the **Overview** page of your product, click **Publish**."]]