You need to select your newly created `my-ship-app` cluster.
You will have next project structure.
```shell theme={null}
/my-ship-app
/.github
/apps
/api
/web
/deploy
...
```
## Container registry
You need to create [Container Registry](https://www.digitalocean.com/products/container-registry) for storing Docker images. The deployment script will upload images to Container Registry during the build step, and Kubernetes will automatically pull these images from Container Registry to run a new version of service during the deployment step.
Name container registry as the name of organization, which usually is equals to the name of the project: `my-ship-app`.
After some time, you will get registry endpoint.
`registry.digitalocean.com/my-ship-app` is registry endpoint, where `my-ship-app` is registry name.
Docker images for each service are stored in separate repository.
In Digital Ocean repositories are created automatically when something is uploaded by specific paths.
During deployment process script will automatically create paths to repositories in next format:
* [**API**](/api-reference/overview) - registry.digitalocean.com/my-ship-app/api;
* [**Scheduler**](/scheduler) - registry.digitalocean.com/my-ship-app/scheduler;
* [**Migrator**](/migrator) - registry.digitalocean.com/my-ship-app/migrator;
* [**Web**](/web/overview) - registry.digitalocean.com/my-ship-app/web;
You need to select your newly created `my-ship-app` cluster.
We will need this token soon, so don't close this page yet.
Provider & Region:
Provider & Region:
**Example Connection String:**
```bash theme={null}
mongodb+srv://api-production:your-password@cluster0.xxxxx.mongodb.net/?retryWrites=true&w=majority
```
Now commit all changes to GitHub that will trigger deployment, or you can [run a workflow manually](https://docs.github.com/en/actions/managing-workflow-runs-and-deployments/managing-workflow-runs/manually-running-a-workflow)
Done! Application deployed and can be accessed by the provided domain.
```shell theme={null}
kubectl get pods -A
NAMESPACE NAME READY STATUS RESTARTS AGE
ingress-nginx ingress-nginx-controller-6bdff8c8fd-kwxcn 1/1 Running 0 6h50m
kube-system cilium-tb8td 1/1 Running 0 8h
kube-system cilium-x5w8n 1/1 Running 0 8h
kube-system coredns-5679ffb5c8-b7dzj 1/1 Running 0 8h
kube-system coredns-5679ffb5c8-d465r 1/1 Running 0 8h
kube-system cpc-bridge-proxy-ebpf-2gzfr 1/1 Running 0 8h
kube-system cpc-bridge-proxy-ebpf-jknzh 1/1 Running 0 8h
kube-system csi-do-node-jcqd2 2/2 Running 0 8h
kube-system csi-do-node-rpx6q 2/2 Running 0 8h
kube-system do-node-agent-ldhxq 1/1 Running 0 8h
kube-system do-node-agent-pdksz 1/1 Running 0 8h
kube-system hubble-relay-66f54dcd57-l7xjb 1/1 Running 0 8h
kube-system hubble-ui-785bdbc45b-6xd57 2/2 Running 0 8h
kube-system konnectivity-agent-h79mt 1/1 Running 0 8h
kube-system konnectivity-agent-hvv67 1/1 Running 0 8h
production api-57d7787d98-cj75s 1/1 Running 0 2m15s
production migrator-286bq 0/1 Completed 0 2m54s
production scheduler-6c497dfbcc-n6b5l 1/1 Running 0 2m6s
production web-54c6674974-lv94b 1/1 Running 0 71m
redis redis-master-0 1/1 Running 0 6h49m
staging api-689b75c786-97c4l 1/1 Running 0 71m
staging scheduler-57b984f6c-zcc44 1/1 Running 0 71m
staging web-55bdd955b-chswp 1/1 Running 0 70m
```
Region Selection: For Kubernetes deployments on AWS, choose the same AWS region as your EKS cluster to minimize latency and data transfer costs.
)} {provider_0 === 'do' && (Region Selection: For Kubernetes deployments on Digital Ocean, choose the same region as your cluster to minimize latency and data transfer costs.
)}
