ContainerRegistry
A ContainerRegistry is a managed image repository. On AWS this is ECR, on GCP Artifact Registry, and on DigitalOcean a container registry. Hetzner has no equivalent.
This type does not push or pull images and does not manage lifecycle policies.
Config
Section titled “Config”| Property | Type | Required | Description |
|---|---|---|---|
name |
string |
yes | Unique resource name |
id |
string |
no | Explicit ID (auto-generated UUID if omitted) |
provider |
string |
no | Provider label for multi-provider configs |
tags |
Record<string, string> |
no | Arbitrary key-value metadata |
region |
string |
no | Abstract region |
public |
boolean |
no | Whether the registry is public (default false) |
Example
Section titled “Example”import { ContainerRegistry } from '@kykucloud/types'
const images = new ContainerRegistry({ name: 'app-images', region: 'us-east',})Provider Support
Section titled “Provider Support”| Provider | Supported | Backend |
|---|---|---|
| AWS | ✅ | ECR (CreateRepository) |
| GCP | ✅ | Artifact Registry (Docker) |
| Hetzner | ❌ | Unsupported |
| DigitalOcean | ✅ | Container Registry (one per account) |
- Outputs:
urlis the push/pull endpoint. - DigitalOcean allows a single registry per account. Create is idempotent via
GET /v2/registry. - No image CLI:
kykudoes not push or pull images. - No lifecycle policies: expiry and tag rules are out of scope.