An image is a "lightweight, standalone, executable package of software that includes everything needed to run an application: code, runtime, system tools, system libraries, and settings".

Control Plane offers its users their own hosted private image registry. Your application will be packaged and stored as an image and will be served by a workload.

When configuring the source of the workload's container image, you have the option of using either an external private/public image registries, such as Docker Hub, or the internal private image registry offered by the platform.

The CLI contains the functionality to build and push your application to your private image registry.


The benefits of using your org's private image registry are:

  • No Pull Secrets are required when configuring your workload
  • Minimizes latency when pulling the image into your container
  • Requires access permissions when pulling from outside the platform (e.g. using Docker pull)

Push an image

Refer to the Push an Image guide for additional details.


The permissions below are used to define policies together with one or more of the four principal types:

createCreate new image. You can push if you can create images.pull
editModify existing image (only tags can be changed)view
manageFull accesscreate, delete, edit, manage, pull, view
pullImage can be pulledview
viewRead-only access

Access Report

Displays the permissions granted to principals for the image.


To view the CLI documentation for images, click here

Copyright © 2021 Control Plane Corporation. All rights reserved. Revision 30221ec6