Use a Docker image deployment when you already have a built container image, such as nginx:latest or an image stored in a private registry.
- Runs a container image as a Kubly application.
- Creates the workload, service, generated access URL, and optional supporting resources.
- Can use registry credentials when the image is private.
- Your CI/CD pipeline already builds and pushes images.
- You want the fastest way to launch a known image.
- You do not need Kubly to build source code.
- A container image reference and tag.
- Registry access if the image is private.
- The port your app listens on.
- CPU and memory settings appropriate for the app.
Screenshot Required
- Open Applications and create a new deployment.
- Choose the image or Docker image source.
- Enter the image name and tag.
- Select the project and namespace.
- Enter the container port.
- Set CPU, memory, environment variables, secrets, storage, and scaling.
- Create the deployment.
- Open the deployment detail page and check readiness, logs, events, and generated URL.
- Using an image tag that does not exist.
- Forgetting registry credentials for a private image.
- Entering the wrong app port.
- Use immutable image tags for production when possible.
- Test with the generated URL before adding a custom domain.
- If the pod shows
ImagePullBackOff, check the image name, tag, and registry credentials.