Skip to main content

Container Registry Overview

KakaoCloud Container Registry is a private image repository that allows you to safely store and manage Docker container images in the cloud environment. It is also linked to KakaoCloud Kubernetes Engine, and supports efficient management and deployment of container images for container-based applications and services.
Additionally as it is based on KakaoCloud IAM, you can properly manage access to the storage. It is designed to manage user permissions, optimize development and operation processes while maintaining image stability and security, and successfully operate containerized application.

Purpose and use cases​

Using a container image requires space to store the image. Individuals can use the free plan of GitHub or DockerHub, but companies need a private repository, so building their own repository incurs development and operation costs. By utilizing the KakaoCloud Container Registry, you can save resources required for new storage development, manage images centrally, and deploy applications using the same image in multiple environments.

Features​

Private container image repository​

  • Distribution and storage of images by repository
  • Easy to deploy container images to various environments such as development, testing, staging, and production
  • Able to use consistent images in various environments
  • Provides image access and permission management
  • Supports Docker standard image

Image vulnerability scan via Trivy​

  • Automatically scan for vulnerabilities when uploading or updating images
  • Check packages, dependencies, runtime environment
  • Check scan results in the form of vulnerability information and reports
  • Repeated inspection to maintain image stability
  • Quick action possible by sending warnings and notifications when vulnerabilities are discovered

Image history management​

  • Manage images using tags that indicate image versions
  • Track and record image change history and updates
  • Restore the image version
  • Automatic deletion and storage period can be specified through retention policy settings for image history management
  • Provides branch and flow management similar to Git
  • Control access to important changes through logging

Access control​

  • As it is IAM-based, user permissions to access storage can be managed.