Add new DevOps agent for Golang 1.16

[JohnNiang]

What this PR dose?

Add a new pod template for Golang 1.16.

Why we need it?

Please see #28.

Which issue dose this PR fix?

Fix #28

How to test?

1. Install ks-devops via helm charts

make install-chart

2. Create a test Pipeline

Pipeline script example:

pipeline {
  agent {
    node {
      label 'go16'
    }
  }
  stages {
    stage('Greet') {
      steps {
        container('go') {
          sh '''go version'''
        }
      }
    }
  }
}

[JohnNiang]

/kind feature

[JohnNiang]

/cc @kubesphere-sigs/sig-devops

[AbdelouahabMbarki]

I've left some comments here, nice Job

[AbdelouahabMbarki]

golang16 --> Golang16

[JohnNiang]

Thanks for you patient review!

In fact, helm recommends that variable name should begin with a lowercase letter, and words should be separated with camelcase, please see https://helm.sh/docs/chart_best_practices/values/.

Meanwhile, we have plan to refine other variable names in Jenkins charts, please see issue #26 I've submitted before.

---

But now, I agree with you to keep the naming style of variable name same with others. I will change them later, and thank you for pointing out this again.

[AbdelouahabMbarki]

golang16 -- > Golang16

[LinuxSuRen]

/lgtm

I have tested manually. The Jenkinsfile is:

pipeline {
  agent {
    label 'go16'
  }
  
  stages{
    stage('test'){
      steps{
        container('go') {
          sh 'go version'
        }
      }
    }
  }
}

Test output:

Running on go16-3w3t7 in /home/jenkins/agent/workspace/my-devops-projectwgvcm/test
[Pipeline] {
[Pipeline] stage
[Pipeline] { (test)
[Pipeline] container
[Pipeline] {
[Pipeline] sh
+ go version
go version go1.16.8 linux/amd64
[Pipeline] }
[Pipeline] // container
[Pipeline] }
[Pipeline] // stage
[Pipeline] }
[Pipeline] // node
[Pipeline] End of Pipeline
Finished: SUCCESS