Skip to content

Latest commit

 

History

History
100 lines (68 loc) · 2.46 KB

progress.md

File metadata and controls

100 lines (68 loc) · 2.46 KB
Raw

Environments

  • Kubernetes cluster is setup in one node;
  • Ingress controller is installed; (Optional)
  • Details:
# docker --version
Docker version 19.03.5, build 633a0ea

# kubectl version
Client Version: version.Info{Major:"1", Minor:"15", GitVersion:"v1.15.7", GitCommit:"6c143d35bb11d74970e7bc0b6c45b6bfdffc0bd4", GitTreeState:"clean", BuildDate:"2019-12-11T12:42:56Z", GoVersion:"go1.12.12", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"15", GitVersion:"v1.15.7", GitCommit:"6c143d35bb11d74970e7bc0b6c45b6bfdffc0bd4", GitTreeState:"clean", BuildDate:"2019-12-11T12:34:17Z", GoVersion:"go1.12.12", Compiler:"gc", Platform:"linux/amd64"}

# kubectl get nodes
NAME     STATUS   ROLES    AGE   VERSION
ecs-00   Ready    master   33d   v1.15.7

# kubectl -n kube-system get deployment
NAME                       READY   UP-TO-DATE   AVAILABLE   AGE
coredns                    2/2     2            2           33d
nginx-ingress-controller   1/1     1            1           26d

Progress

Phase 1

Goals:

  • Setup Jenkins instance;
  • Create initial jobs;
  • Manage the configurations in github;
  • Apply further configurations for instance;
  • The instance can be re-built relies on the configurations.

Steps:

  1. Setup Jenkins instance
# ./deploy.sh
  1. Export service by either way below:
    If your ingress controller is working: Update value for 'basic-auth-secret' in ingress/ingress.yaml, and then perform command:
# kubectl apply -f ingress/ingress.yaml

otherwise:

kubectl apply -f master/service-nodeport.yaml

  1. Access Jenkins UI Dashboard will look like below: Jenkins Dashboard

  2. Apply further configuration

# ./load-file-as-code.sh ./casc_configs/
  1. Login Jenkins UI to apply new configurations Login Jenkins UI, open "Manage Jenkins", select "Congifuration as Code", and then click "Apply new Configuration" button. Dashboard of Jenkins UI will becomes below: Jenkins Dashboard

Success.

Phase 2

Goals:

  • Automate all the actions in Phase 1 (> 95%);
  • Create Tekton pipeline for the deployment;

Success.

Phase 3

(on going)

Goals

  • Create Jobs based on human-readable declative codes;
  • Automate the process and apply it into Gitops;