Skip to content

Commit 1408645

Browse files
committed
docs: start documenting what goes into the deploy repo
Create some documentation around what goes into the deploy repo.
1 parent 638ec14 commit 1408645

File tree

2 files changed

+76
-5
lines changed

2 files changed

+76
-5
lines changed

docs/deploy-guide/deploy-repo.md

+67
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,67 @@
1+
# Creating the Deploy Repo
2+
3+
A deployment of UnderStack includes many different services, some of
4+
which will require specific configuration about your environment such
5+
as details about the hardware you will use or details on how you will
6+
connect to the hardware.
7+
8+
These details will be accumulated in your Deployment Repository with
9+
some data being shared while most being scoped to a
10+
[Global cluster](./welcome.md#system-division) or
11+
a [Site cluster](./welcome.md#system-division).
12+
13+
## Initial Structure
14+
15+
To begin we will create our directory structure inside our Deployment Repository.
16+
17+
```bash title="From the Deployment Repo"
18+
# where 'my-global' is the environment name you've used for your global cluster
19+
mkdir -p my-global/{manifests,helm-configs,inventory}
20+
# where 'my-site' is the environment name you've used for your site cluster
21+
mkdir -p my-site/{manifests,helm-configs,inventory}
22+
23+
cat <<- EOF > my-global/deploy.yaml
24+
---
25+
name: my-global
26+
understack_url: https://github.com/rackerlabs/understack.git
27+
understack_ref: v0.0.5 # replace with the tag or git reference you want to use
28+
deploy_url: git@github.com:my-org/my-deploy.git
29+
deploy_ref: HEAD
30+
EOF
31+
32+
cat <<- EOF > my-site/deploy.yaml
33+
---
34+
name: my-site
35+
understack_url: https://github.com/rackerlabs/understack.git
36+
understack_ref: v0.0.5
37+
deploy_url: git@github.com:my-org/my-deploy.git
38+
deploy_ref: HEAD
39+
EOF
40+
```
41+
42+
For `dev` focused deployments, you do not need to specify the refs directly
43+
as they can be set on the ArgoCD cluster secret to allow more flexibility
44+
during testing.
45+
46+
### manifests directory
47+
48+
Inside of the `manifests` directory you'll create child directories that will
49+
be named after each application that we will deploy. These directories are
50+
expected to hold a `kustomization.yaml` as `kustomize` will be used to apply
51+
these manifests to your cluster.
52+
53+
### helm-configs directory
54+
55+
The `helm-configs` directory holds YAML files which are Helm `values.yaml`
56+
files that are used as additional values files that will be merged together
57+
by Helm.
58+
59+
### inventory directory
60+
61+
This directory contains an Ansible inventory file along with Ansible
62+
group_vars that are used as data by Ansible executions within the cluster
63+
to configure different services
64+
65+
This directory contains an Ansible inventory file along with Ansible
66+
group_vars that are used as data by Ansible executions within the cluster
67+
to configure different services.

mkdocs.yml

+9-5
Original file line numberDiff line numberDiff line change
@@ -121,11 +121,15 @@ nav:
121121
- deploy-guide/welcome.md
122122
- deploy-guide/getting-started.md
123123
- Quick Start: deploy-guide/gitops-install.md
124-
- deploy-guide/management-cluster.md
125-
- deploy-guide/auth.md
126-
- deploy-guide/extra-sites.md
127-
- deploy-guide/add-remove-app.md
128-
- deploy-guide/override-openstack-svc-config.md
124+
- Preparing Our Deployment:
125+
- deploy-guide/deploy-repo.md
126+
- deploy-guide/auth.md
127+
- Starting the Deployment:
128+
- deploy-guide/management-cluster.md
129+
- Further Actions:
130+
- deploy-guide/extra-sites.md
131+
- deploy-guide/add-remove-app.md
132+
- deploy-guide/override-openstack-svc-config.md
129133
- 'Operator Guide':
130134
- operator-guide/index.md
131135
- 'OpenStack':

0 commit comments

Comments
 (0)