Quick Start
Login or Sign Up
- Go to the Utho Cloud Platform login page.
- Enter your credentials and click Login .
- If you don’t have an account, sign up here.
Accessing Elastic Block Storage
- Open the Utho Cloud Platform dashboard.
- Click on “Container Registry” in the sidebar.
- You will be redirected to the Container Registry listing page.
- Click on Create Repository to open the deployment page.
On the Deploy Page , configure the following:
- Select DC Location: DC location in a container registry refers to the data center location where the container images are stored. It determines the physical or geographical region of the registry, impacting latency and performance. Choosing the right DC location helps optimize speed, reduce costs, and ensure compliance with data residency regulations.
- Container Registry Type: There are 2 types of container registry
- Public Container Registry : This type of registry allows anyone to access, pull, and use container images. Examples include Docker Hub and Google Container Registry (GCR). It’s ideal for open-source projects or sharing images with a wide audience.
- Private Container Registry : This registry restricts access to authorized users or services only. It is used for storing sensitive or proprietary images that need to be kept secure. Examples include AWS Elastic Container Registry (ECR) and Azure Container Registry (ACR).
- Name Your Registry Container:
- Organization : It helps organize and categorize container images, making it easier to manage and identify different projects, environments, or application versions.
- Access Control : Naming conventions can be used to enforce access policies, like differentiating between public and private images or separating different teams’ images within the same registry.
- Clarity : A well-named container registry clearly indicates its purpose (e.g., production , staging , dev ), helping teams understand where to push or pull images for specific environments.
- Versioning : The naming structure can include versioning information, ensuring different versions of the same image can be stored and retrieved easily.
Click on the Create Registry button to deploy the container registry into your account container registry.
Verify Registry Addition:
- Once added, the new container registry should appear in the public/private tab based on the container type selected at deployment time.
Manage Container Registry
At the top of the Manage section, users can view the configuration information of the selected Container Registry. This includes:
- Container Registry Name: The unique name assigned to the Container Registry.
- Make Private/Public: Click the Make Private/Public button to change the visibility of your container registry.
- View Credentials: Click the View Credentials button to open a modal where you can copy the username and password.
- View Push Commands: Click the View Push Commands button to open a drawer where user can see and copy the commands.
The “View Credential” in a container registry allows you to access the authentication credentials needed to interact with the registry. These credentials are essential for securely pulling or pushing container images to and from the registry. Here’s how it’s useful:
- Access Management : It helps you retrieve the credentials (like username/password or access tokens) required to authenticate your identity when accessing private container images.
- Secure Interactions : Ensures that only authorized users or services can upload or download images from the registry, maintaining security.
- Automation : The credentials provided can be used in CI/CD pipelines or automated deployment scripts to enable seamless and secure interaction with the container registry.
The “View Push Commands” in a container registry provides the necessary commands to upload (push) container images to the registry. It is used to guide users or automation tools in pushing their locally built or modified container images to the registry for storage and deployment. Here’s how it’s useful:
- Simplifies Workflow : It provides the exact Docker CLI commands or tools for pushing images, making it easier for developers to upload images without having to remember complex syntax.
- Automation : The push commands can be integrated into CI/CD pipelines , allowing for automated pushing of container images during build and deployment processes ayush.
- Security & Authentication : The commands typically include necessary authentication steps (e.g., login credentials or token usage), ensuring secure interaction with the container registry.
Manage Repository
In the Manage Repository section, users can view the Repositories and remove the repository. This section provides the following functionalities:
Pull Count refers to the number of times a specific container image has been pulled (downloaded) from the registry by users or systems. It provides insight into how frequently the image is being accessed or used in deployments, updates, or development environments.
Benefits:
- Usage Insights : It helps understand the popularity or demand for a particular container image.
- Monitoring and Analytics : It can assist in tracking which images are actively being used and which may be outdated or underutilized.
- Performance Optimization : High pull counts may indicate frequent deployment or testing, which could prompt optimizations in access speed or caching strategies.
- Delete: Click the Delete button to remove the repository from the container registory.
Destroy
In the Destroy section, users can terminate the Container Registry instance. This action is irreversible and will permanently delete the Container Registry and all associated data. To destroy a Container Registry
Click the Destroy Container Registry button.
Confirmation:
A confirmation dialog will appear. Copy the name of the Container Registry and paste it into the input box. Confirm the action to proceed with destroying the Container Registry.
When you provide the confirmation then your Container Registry will destroy.