Version Updates, Deprecation and Deletion for Container Image Solutions

Update images in Container Registry

Following the same process as in your initial image push(es) to your Container Registry staging repository, add your new image(s) to Container Registry with the proper tag:

  1. Build the image your wish to push to your Container Registry staging repository.
  2. Tag your image via Docker using the tag of the existing version you'd like to update (or with a new tag if you want the image under a new version):

    docker tag {image_name} {staging_repo_path}:{tag}

    For example, docker tag test-image

  3. Push your image via gcloud:

    gcloud docker push {staging_repo_path}:{tag}

  4. Repeat for any additional tags you'd like to add or update to add to your staging repository. Note that a single image may have multiple tags.

    Remember that pushing an image to your staging repository won't automatically make it visible to users (even if you use a tag that is already associated with a version); this only happens after you update the version in Partner Portal and your submitted draft is published.

You can also manage tags directly (add, edit, or delete) on images already in your Container Registry staging repository using the Container Registry UI.

Update versions in Partner Portal

Step 1. Navigate to the Versions solution editor page in Partner Portal

The direct link for Partner Portal is:

Launch the solution editor for your solution by clicking on its solution ID, and then clicking on the Edit button for versions.

Step 2. Update the digest for outdated versions

For images pushed with a new tag (or a tag that has not yet had a version created for it), follow the steps to create a new version.

For images updates to existing tags associated with versions:

  1. Click on the Container Registry tag of the version to edit it (not the sync status icon).

    If a version's digest needs to be updated (the current draft digest is out of sync with the Container Registry digest with the associated tag), then there will be an error symbol instead of a checkmark in the Sync status column.

  2. Click the Update to current digest button.

    If the digest for this version on your draft is out of sync with the digest in your staging repository with the corresponding tag, then the button will be enabled. The current digest with the tag in your staging repository will be shown below the button. If the button is disabled, then the digests are in sync so no image update is needed.

  3. Update the OS and packaged software for this particular digest.

    Remember that OS and packaged software are specific to each particular digest and cannot be changed after publishing.

    Any OS and packaged software previously entered will be copied over for your convenience. Modify the info to make it accurate to this particular digest.

  4. Save the changes to this version by clicking Save.

  5. Repeat for any other outdated versions.

Step 3. Submit your solution for review

Click Save to leave the version section and navigate back to the main menu of the solution editor.

Click Submit to submit your solution for review. Upon approval, your changes will be published.

Version deprecation and deletion

Your container versions must have a deprecation period of at least 190 days. This gives your customers time to plan for the deprecation and upgrade to a newer version of your software.

To deprecate a version, you must schedule it for deletion, which sends a request to the GCP Marketplace team to approve the deprecation. While the version is scheduled for deletion, users see a warning that the version is deprecated, but can still pull the container images from the Container Registry repository.

After the deletion date, the version is removed from GCP Marketplace entirely.

You cannot deprecate the "latest" version of your container, because this version is required.

To schedule a deprecation:

  1. Open Partner Portal. The direct link to Partner Portal is:
  2. Click on the solution that you want to edit, and edit the Versions section

  3. Click the Container Registry tag of the version that you want to edit.

  4. In the Edit version panel, select Deprecate and schedule for deletion.

  5. Choose the date on which you want your version to be deleted.

    The date must be at least 190 days from the date on which your request is approved. If there are issues with verification or approval, or if you cannot submit your draft immediately, you might need to adjust your date.

  6. Click Save.

  7. Repeat these steps for any other versions that you want to deprecate.

  8. Click Submit to submit your solution for review.

Оцените, насколько информация на этой странице была вам полезна:

Оставить отзыв о...

Текущей странице
GCP Marketplace