Registries

A registry is where Ownkube gets container images from when you deploy. Connect a source once and use it across every deployment. Manage them under Settings.

You have three ways to give Ownkube an image:

GitHub repository

Available now. Connect the GitHub App so Ownkube can build an image from your source and store it, then redeploy on every push. The most common path on Ownkube-hosted compute.

Public image

Available now. Any publicly pullable image reference works with no connection at all.

Amazon ECR (own cloud)

Available now. On the Advanced own-cloud path, Ownkube uses the IAM role you connected during AWS onboarding to pull from your private ECR repositories. No access keys to store or rotate.

Build from a GitHub repository

If your code is on GitHub, you don’t need to build and push images yourself. Connect the GitHub App and Ownkube builds the image for you and stores it, ready to deploy. This is the most common path on Ownkube-hosted compute.

The GitHub App install gives Ownkube scoped access to the repositories you choose. Benefits:

No expiring tokens: rotation happens automatically
Scoped per repository: revoke access to individual repos without touching anything else
Repository picker at deploy time: Ownkube can list your installed repos when you create a deployment
Auto-generated build workflows: Ownkube can open a PR adding a build-and-push workflow to your repo so each push ships a new image

You can connect more than one GitHub App installation per organization, for example your personal account plus one or more GitHub organizations. Each deployment remembers which connection it builds from.

How to connect

Open Settings

Go to Settings and open the registries section.
Start the GitHub App install

Click Connect GitHub App.
Pick your target

GitHub asks whether to install on a personal account or an organization. Pick the owner of the repositories you want to deploy.
Choose repositories

Either All repositories or Select repositories. You can change this later on GitHub at any time.
Finish

You’re redirected back to Ownkube with the connection in the active state.

Public image

Any publicly pullable image reference works with no connection at all. Point a deployment at the image (e.g. nginx:1.27 or ghcr.io/org/app:v1.2.3) and Ownkube pulls it. Pin a specific tag so every deploy is traceable.

Amazon ECR (own cloud)

On the Advanced own-cloud path, Ownkube can pull from your private Amazon ECR repositories. It reuses the same IAM role you set up during AWS onboarding, so there are no registry credentials to manage separately.

Connect AWS

If you haven’t already, finish AWS onboarding. The least-privilege role Ownkube assumes includes scoped pull access to ECR.
Open Settings

Go to Settings and open the registries section. Your connected AWS account’s ECR is available to deployments in that account.
Pick a repository and tag at deploy time

When you create a deployment, Ownkube autocompletes your ECR repositories and their tags. Pick the image, pick the tag, deploy.

Using an image in a deployment

When you create a deployment, pick where the image comes from: a GitHub repository to build, a public image reference, or (in your own cloud) an ECR repository. Ownkube autocompletes repositories and tags from whatever you’ve connected.

Verifying a connection

If a GitHub App install is removed or revoked, Ownkube marks the connection as failed. Click Verify on the connection card to re-test it without deleting anything. Re-verification checks the install is still present and hasn’t been revoked.

If verification fails, reinstall the GitHub App.

Removing a connection

The Remove action is a soft-delete. The row stays in the database but is marked revoked, and any stored credentials are cleared. Existing deployments keep running from cached images, but new pulls or builds will fail. Reconnect to restore access.

Deploy your first app Use your registry to ship a deployment.

Environment variables Configure secrets your app needs at runtime.