Container registry
Every Aether organization gets a private container registry. Push your images to it, then pull them from your clusters’ workloads. Images are vulnerability-scanned on push, and you can configure cleanup/retention policies from the portal.
The registry is hosted at registry.eu-fi.aetherplatform.cloud.
Image naming
Section titled “Image naming”Your images live under a path that includes your organization’s slug:
registry.eu-fi.aetherplatform.cloud/aether/<org-slug>/<image>:<tag><org-slug> is your organization’s slug — the short, URL-safe identifier shown in
the portal. Replace it (and <image> / <tag>) with your own values.
Push an image
Section titled “Push an image”-
In the portal, open Registry and generate registry credentials. You’ll get a username and a token to use as the password.
-
Log in with Docker:
Terminal window docker login registry.eu-fi.aetherplatform.cloudEnter the credentials you generated.
-
Tag your local image for the registry:
Terminal window docker tag my-app:latest \registry.eu-fi.aetherplatform.cloud/aether/<org-slug>/my-app:v1 -
Push it:
Terminal window docker push registry.eu-fi.aetherplatform.cloud/aether/<org-slug>/my-app:v1
Pull from a cluster
Section titled “Pull from a cluster”Reference the full image path in your workload spec:
spec: containers: - name: my-app image: registry.eu-fi.aetherplatform.cloud/aether/<org-slug>/my-app:v1If your repository requires authentication to pull, create an image pull secret from your registry credentials and reference it in the pod spec:
kubectl create secret docker-registry aether-registry \ --docker-server=registry.eu-fi.aetherplatform.cloud \ --docker-username=<username> \ --docker-password=<token>Scanning and cleanup
Section titled “Scanning and cleanup”- Scan on push — every pushed image is automatically scanned for known vulnerabilities. Review results in the portal.
- Cleanup policies — configure retention rules in the portal to automatically remove old or untagged images and keep your storage tidy.
Next steps
Section titled “Next steps”- Observability — watch your cluster’s health and metrics.