Container Image Deployments

Learn how to deploy pre-built container images. Kubeletto pulls image layers, validates security compliance digests, and runs the workload in isolated compute environments.

Supported OCI Registries

Specify container references directly. Kubeletto supports public and authenticated registries:

• Docker Hub: docker.io/library/node:lts-alpine (or shorthand node:lts-alpine)
• GitHub Container Registry: ghcr.io/orgname/service-pkg:v1.2.0
• Quay.io: quay.io/username/api-worker:latest
• Private Registries: Configure registry authentication tokens via the web console settings panel or CLI secrets store before triggering deployment.

Networking and Port Mapping

By default, Kubeletto routes traffic to port 8080 and injects PORT=8080 into your container automatically. If your application listens on a different port, specify it at deploy time using the --port flag:

$ kubeletto deploy --app my-api --image nginx:alpine --port 80 --wait

You can also update the port for an existing service in the web console under Service → Settings → Container Port. Note: PORT is managed by the platform and cannot be set as a custom environment variable.