Skip to content
Snippets Groups Projects
Commit 2c53abe6 authored by Tomohiro Ono's avatar Tomohiro Ono Committed by Yas Naoi
Browse files

Issue #3273962 by onotm, yas: Add instructions to deploy Cloud Orchestrator on a K8s cluster

parent 2a3d28e9
No related branches found
No related tags found
3 merge requests!1316Issue #3310263: Release 4.5.0,!1260Issue #3307397: Release 4.4.0,!833Issue #3273962: Describe instructions to deploy Cloud Orchestrator on a K8s cluster
USAGE INSTRUCTIONS
==================
**1. Build a Cloud Orchestrator image**
```
$ git clone https://git.drupalcode.org/project/cloud.git
$ cd cloud/deployments/kubernetes
$ docker image build -t cloud_orchestrator:latest .
```
**2. Push the image to your Docker repository**
```
$ docker image tag cloud_orchestrator:latest your/repository:latest
$ docker image push your/repository:latest
```
**3. Edit `cloud_orchestrator.yml`**
* [Line 18- 24](https://git.drupalcode.org/project/cloud/-/blob/5.x/deployments/kubernetes/cloud_orchestrator.yml#L18-24): Set your usernames, passwords, e-mail address and database name
* [Line 113](https://git.drupalcode.org/project/cloud/-/blob/5.x/deployments/kubernetes/cloud_orchestrator.yml#L113): Set `your/repository:latest`
**4. Apply `cloud_orchestrator.yml` to your K8s cluster**
```
$ kubectl apply -f cloud_orchestrator.yml
```
**5. (Optional) Add a load balancer to access Cloud Orchestrator from your browser**
If you are using EKS, you can add a load balancer to access Cloud Orchestrator
from your browser as follows. Initially, this load balancer accepts all inbound
traffic. To restrict access to Cloud Orchestrator, change the security group
associated with that load balancer.
```
$ kubectl expose service cloud_orchestrator \
--namespace=cloud_orchestrator \
--type=LoadBalancer \
--name=cloud_orchestrator-lb
```
**6. Remove Cloud Orchestrator from your K8s cluster**
```
$ kubectl delete -f cloud_orchestrator.yml
```
`cloud_orchestrator.yml` installs Cloud Orchestrator and stores MariaDB database
on a filesystem of one of the K8s nodes via PersistentVolumes of the type
hostPath. When these PersistentVolumes are deleted, files stored in the node's
filesystem are NOT deleted. If you want to delete them, log in to the node and
execute the following command:
* Cloud Orchestrator
- `rm -r /var/www/cloud_orchestrator`
* MariaDB
- `rm -r /var/cloud_orchestrator/mysql`
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Please register or to comment