deploy-devops

Environment

2 Ubuntu20.04 LTS VM (The minimum resource configuration of a virtual machine is 4 vcore, 8G ram, 32G HD; however, for production environment, it should be 3 or more VMs with 8 vcore, 16G ram, 120G SSD)
- VM1(iiidevops1, 10.20.0.71): GitLab ce-12.10.6 Server, Harbor 2.1 Server, Rancher Server, NFS Server
- VM2(iiidevops2, 10.20.0.72): Kubernetes node(control plane + etcd + worker node)
Before installation, you should decide on these configuration settings
1. External access IP or domain name of VM1 and VM2
2. GitLab root password
3. Rancher admin password
4. Redmine admin password
5. Harbor admin passowrd
6. III-devops super user account ('admin' and 'root' are not allowed)
7. III-devops super user E-Mail
8. III-devops super user password
During the installation process, you should be able to get the following setup information through GitLab Web UI
1. GitLab private token
You can scale out the Kubernetes nodes (VM3, VM4, VM5...) or scale up the VM1 according to actual performance requirements.

Step 1. Download deploy-devops and Install docker (VM1)

wget https://github.com/raw/iii-org/deploy-devops/master/bin/iiidevops_install.pl;
perl ./iiidevops_install.pl local

If everything is correct, you will see that all check items are OK shown below.

localadmin@iiidevops-71:~$ perl ./iiidevops_install.pl local
:
:
:
-----Validation results-----
Install docker 19.03.14 ..OK!
Install kubectl v1.18 ..OK!

Step 2. Generate configuration setting information file "env.pl" (VM1)

~/deploy-devops/bin/generate_env.pl
After entering, please check whether the configuration setting information is correct. You can also edit this env.pl configuration file data.

vi ~/deploy-devops/env.pl

Step 3. Deploy Gitlab / Harbor / Rancher / NFS (VM1)

sudo ~/deploy-devops/bin/iiidevops_install_mainapps.pl

After the deployment is complete, you should be able to see the URL information of these services as shown below.

Harbor - https://10.20.0.71:5443/

Rancher - https://10.20.0.71:6443/

GitLab - http://10.20.0.71/

Step 4. Setting Harbor server

Harbor - https://10.20.0.71:5443/

Log in with the account admin and password ($harbour_admin_password) you entered in step 2.(~/deploy-devops/env.pl)

Check Project - dockerhub (Access Level : Public , Type : Proxy Cache) was added.

If the project dockerhub is not created, you can exectue the command to manually create it.

sudo ~/deploy-devops/harbor/create_harbor.pl create_dockerhub_proxy

Step 5. Set up Rancher from the web UI

Rancher - https://10.20.0.71:6443/

Use the $rancher_admin_password entered in Step 2.(~/deploy-devops/env.pl) to set the admin password

set Rancher Server URL

Create a Kubernetes by rancher

add cluster/ From existing nodes(Custom)

Cluster name: iiidevops-k8s

Kubernetes Version: Then newest kubernetes version Exp. **v.118.12-rancher1-1 **

Network provider: Calico

CNI Plugin MTU Override: 1440

Click Next to save the setting (It will take a while. If you receive the error message "Failed while: Wait for Condition: InitialRolesPopulated: True", just click 'Next' again.)

Node Options: Chose etcd, Control plane, worker

Copy the command to add-k8s.sh and make VM2 join the K8S cluster

Copy the command to /iiidevopsNFS/deploy-config/add_k8s.sh

vi /iiidevopsNFS/deploy-config/add_k8s.sh
Execute the following command on VM1 to make VM2 join the K8S cluster.

~/deploy-devops/bin/add-k8s-node.pl [user@vm2_ip]

It should display as below.
localadmin@iiidevops-71:~$ ~/deploy-devops/bin/add-k8s-node.pl [email protected]
:
:
:
-----Validation results-----
Docker          : OK!
Kubectl         : OK!
NFS Client      : OK!
Harbor Cert     : OK!

Please goto Rancher Web - https://10.20.0.71:6443 to get the status of added node of k8s cluster!
After executing this command, it takes about 5 to 10 minutes to build the cluster.

Rancher Web UI will automatically refresh to use the new SSL certificate. You need to login again. After the iiidevops-k8s cluster is activated, you can get kubeconfig file.

Get Kubeconfig File

Put on kubeconfig file to ~/.kube/config and /iiidevopsNFS/kube-config/config on VM1, and also keep it.
 vi /iiidevopsNFS/kube-config/config
 ln -s /iiidevopsNFS/kube-config/config ~/.kube/config
Use the following command to check if the config is working

kubectl cluster-info

It should display as below.
localadmin@iiidevops-71:~$ kubectl cluster-info
Kubernetes master is running at https://10.20.0.71:6443/k8s/clusters/c-fg42q
CoreDNS is running at https://10.20.0.71:6443/k8s/clusters/c-fg42q/api/v1/namespaces/kube-system/services/kube-dns:dns/proxy

To further debug and diagnose cluster problems, use 'kubectl cluster-info dump'.

Set up Rancher pipeline and Gitlab hook

Choose Global/ Cluster(iiidevops-k8s)/ Project(Default)

Choose Tools/Pipline, select Gitlab

Get the "Redirect URI" and then open GitLab web UI

Step 5. Set up GitLab from the web UI

GitLab - http://10.20.0.71/

Log in with the account root and password ($gitlab_root_passwd) you entered in step 2.(~/deploy-devops/env.pl)

Set up Rancher pipeline and Gitlab hook(continue)

Use root account/ settings/ Applications

Setting Applications
insert Name : iiidevops-k8s, Redirect URI: [from Rancher] and chose all optional, and save application.

Take the "Application ID" and "Secret", go to rancher pipeline, insert application id, secret and private gitlab url.

Authorize

Done

Switch back to GitLab web UI

Generate root personal access tokens

User/Administrator/User seetings, generate the root personal access tokens and keep it.

Access Tokens / Name : root-pat / Scopes : Check all / Create personal access token

Keep Your New Personal Access Token
Modify the $gitlab_private_token value in env.pl

~/deploy-devops/bin/generate_env.pl ask_gitlab_private_token [Personal Access Token]

It should display as below.
localadmin@iiidevops-71:~$ ~/deploy-devops/bin/generate_env.pl ask_gitlab_private_token 535wZnCJDTL5y22xYYzv
A4. Set GitLab Token OK!

Q21. Do you want to generate env.pl based on the above information?(Y/n)
The original env.pl has been backed up as /home/localadmin/deploy-devops/bin/../env.pl.bak
-----
11c11
< $gitlab_private_token = '535wZnCJDTL5y22xYYzv'; # Get from GitLab Web
---
> $gitlab_private_token = 'skip'; # Get from GitLab Web
-----

Enable Outbound requests from web hooks

Admin Area/Settings/Network/Outbound reuests, enable allow request to the local network from web hooks and service / Save changes

Step 7. Deploy Redmine on kubernetes cluster

~/deploy-devops/bin/iiidevops_install_apps.pl

After the deployment is complete, you should be able to see the URL information of these services as shown below.

Redmine - http://10.20.0.72:32748/

Redmine

Redmine URL - http://10.20.0.72:32748/

Log in with the account admin and password ($redmine_admin_passwd) you entered in step 2.(~/deploy-devops/env.pl)

Step 8. Deploy III-DevOps

~/deploy-devops/bin/iiidevops_install_core.pl

You should wait 3 to 5 minutes to complete the deployment and initial system setup. Then, you can access the URL as shown below.
:
:
.

Add Secrets Credentials
-----
nexus : Create Secrets /home/localadmin/deploy-devops/devops-api/secrets/nexus-secret.json..OK!
checkmarx : Create Secrets /home/localadmin/deploy-devops/devops-api/secrets/checkmarx-secret.json..OK!
webinspect : Create Secrets /home/localadmin/deploy-devops/devops-api/secrets/webinspect-secret.json..OK!

Add Registry Credentials
-----
harbor-local : Create Registry /home/localadmin/deploy-devops/devops-api/secrets/harbor-local-registry.json..OK!

The deployment of III-DevOps services has been completed. Please try to connect to the following URL.
III-DevOps URL - http://10.20.0.72:30775
Go to Web UI to login

III-DevOps URL - http://10.20.0.72:30775/

Use the $admin_init_login and $admin_init_password entered in Step 2.(~/deploy-devops/env.pl) to login to III-DevOps

Step 9. Scale-out K8s Node

Execute the following command on VM1 to make VM3 join the K8s cluster.

~/deploy-devops/bin/add-k8s-node.pl [user@vm3_ip]

It should display as below.
localadmin@iiidevops-71:~$ ~/deploy-devops/bin/add-k8s-node.pl [email protected]
:
:
:
-----Validation results-----
Docker          : OK!
Kubectl         : OK!
NFS Client      : OK!
Harbor Cert     : OK!
-----
NAME           STATUS   ROLES                      AGE   VERSION
iiidevops-72   Ready    controlplane,etcd,worker   23h   v1.18.12
After executing this command, it will take about 3 to 5 minutes for the node to join the cluster.

Name		Name	Last commit message	Last commit date
Latest commit History 293 Commits
bin		bin
devops-api		devops-api
devops-db		devops-db
devops-ui		devops-ui
doc		doc
gitlab		gitlab
harbor		harbor
kubernetes/namespaces		kubernetes/namespaces
png		png
rancher		rancher
redmine		redmine
sonarqube		sonarqube
.gitignore		.gitignore
LICENSE		LICENSE
README.md		README.md
env.pl.tmpl		env.pl.tmpl

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

Repository files navigation

deploy-devops

Environment

Step 1. Download deploy-devops and Install docker (VM1)

Step 2. Generate configuration setting information file "env.pl" (VM1)

Step 3. Deploy Gitlab / Harbor / Rancher / NFS (VM1)

Step 4. Setting Harbor server

Step 5. Set up Rancher from the web UI

Create a Kubernetes by rancher

Copy the command to add-k8s.sh and make VM2 join the K8S cluster

Get Kubeconfig File

Set up Rancher pipeline and Gitlab hook

Step 5. Set up GitLab from the web UI

Set up Rancher pipeline and Gitlab hook(continue)

Generate root personal access tokens

Enable Outbound requests from web hooks

Step 7. Deploy Redmine on kubernetes cluster

Redmine

Step 8. Deploy III-DevOps

Go to Web UI to login

Step 9. Scale-out K8s Node

About

Uh oh!

Releases

Packages

Contributors 6

Uh oh!

Languages

License

farziengineer/deploy-devops

Folders and files

Latest commit

History

Repository files navigation

deploy-devops

Environment

Step 1. Download deploy-devops and Install docker (VM1)

Step 2. Generate configuration setting information file "env.pl" (VM1)

Step 3. Deploy Gitlab / Harbor / Rancher / NFS (VM1)

Step 4. Setting Harbor server

Step 5. Set up Rancher from the web UI

Create a Kubernetes by rancher

Copy the command to add-k8s.sh and make VM2 join the K8S cluster

Get Kubeconfig File

Set up Rancher pipeline and Gitlab hook

Step 5. Set up GitLab from the web UI

Set up Rancher pipeline and Gitlab hook(continue)

Generate root personal access tokens

Enable Outbound requests from web hooks

Step 7. Deploy Redmine on kubernetes cluster

Redmine

Step 8. Deploy III-DevOps

Go to Web UI to login

Step 9. Scale-out K8s Node

About

Resources

License

Uh oh!

Stars

Watchers

Forks

Releases

Packages 0

Contributors 6

Uh oh!

Languages

Packages