-
Notifications
You must be signed in to change notification settings - Fork 4
Deploy the Software Stack
./menu.sh
Please choose the target environment:
1) gcp 3) esx 5) switch_to_gcp 7) switch_to_esx
2) aws 4) site_secrets 6) switch_to_aws
Choose 1-3
Please choose the playbook:
1) site 8) pause_scheduled_cancel
2) deploy 9) resume
3) deploy_endpoints 10) terminate
4) jenkins_create_credentials 11) terminate_site
5) deploy_gitlab_runners 12) configuration
6) pause 13) manual
7) pause_scheduled
Choose 2
During the deployment, a directory called ./site_<type>
is created and populated with information on how to access your environment including setup logs. Example:
cat site_gcp/jenkins.log
NAME: jenkins
LAST DEPLOYED: Sat Oct 26 10:38:54 2019
NAMESPACE: jenkins
STATUS: DEPLOYED
RESOURCES:
==> v1/ConfigMap
NAME DATA AGE
jenkins 6 1s
jenkins-tests 1 1s
==> v1/Deployment
NAME READY UP-TO-DATE AVAILABLE AGE
jenkins 0/1 1 0 1s
==> v1/PersistentVolumeClaim
NAME STATUS VOLUME CAPACITY ACCESS MODES STORAGECLASS AGE
jenkins Bound pvc-cefb4273-f7dc-11e9-8699-42010a9c0018 8Gi RWO rook-ceph-block 1s
==> v1/Pod(related)
NAME READY STATUS RESTARTS AGE
jenkins-7447ddf9db-2pfdv 0/1 Pending 0 0s
...
$ cat site_gcp/jenkins.txt
URL: http://10.0.2.250:30013
URL: http://jenkins-3-127-104-211.nip.io
Username: admin
Password: XXXXXXXXX
Use this info to access the services or to troubleshoot.
Note: The k8s master is tainted, which means that it does not run Kubernetes workload (which is best practice).
For that reason, services Rook-Ceph will initialize themselves only after workers did join the cluster. Therefore, the deploy.yml
waits for the following condition to be met:
Number of rook-ceph-osd-#- pods equal count of worker nodes in the cluster
That typically takes in between two to three minutes. The deployment of Smart Check, Jenkins, etc. will take place after that initial initialization process.
- Deploy the Endpoints _ Pause the Environment
- [Deep Security]
- [Deep Security Smart Check]
- Container Orchestration
- Container Registry
- Cluster Storage
- Jenkins
- GitLab
- Linkerd
Wiki
About MOADSD-NG
Getting Started
MOADSD-NG Containerized
MOADSD-NG Manual Setup
- Configure your Server
- Preparing to work with Google GCP
- Preparing to work with Amazon AWS
- Preparing to work with VMware ESXi
Adapt MOADSD-NG to Your Needs
The MOADSD-NG Life-Cycle
- Setup the Environment
- Deploy the Software Stack
- Deploy the Endpoints
- Pause the Environment
- Resume the Environment
- Terminate the Environment
- Update the Environment
Software Components
- [Deep Security]
- [Deep Security Smart Check]
- Container Orchestration
- Container Registry
- Cluster Storage
- Jenkins
- GitLab
- Linkerd
- [Prometheus]
- [Grafana]
Tipps
Final Words
Deprecated Chapters