# 1 trigger binding wordt geconfigureerd, en dan worden meerdere trigger templates aangemaakt # voor de verschillende service mesh types. Op deze manier moet ik niet elke keer een aparte pipeline aanmaken per service mesh type. Het nadeel hieraan is dat dan elke keer elke pipeline gerunned wordt, maar uiteindelijk maakt dit niet veel uit zolang de deploy.yaml files leeg zijn wanneer de commits door gaan --- apiVersion: tekton.dev/v1alpha1 kind: TriggerBinding metadata: name: github-trigger-binding namespace: stage-tekton-pipeline spec: params: - name: gitrevision value: $(body.pull_request.head.sha) - name: gitrepositoryurl value: $(body.pull_request.head.repo.clone_url) - name: prurl value: $(body.pull_request.html_url) - name: repo value: $(body.pull_request.base.repo.full_name) - name: source value: github --- apiVersion: tekton.dev/v1alpha1 kind: TriggerTemplate metadata: name: github-trigger-template namespace: stage-tekton-pipeline spec: params: - name: gitrevision description: The git revision default: master - name: gitrepositoryurl description: The git repository url resourcetemplates: - apiVersion: tekton.dev/v1alpha1 kind: PipelineRun metadata: name: application-pipeline-run namespace: stage-tekton-pipeline spec: serviceAccountName: service-acc pipelineRef: name: application-pipeline #gebruik dit om de pipeline aan te passen naar andere versies, zolang ze zich in dezelfde namespace bevinden kunnen we deze pipeline hergebruiken om deployments op de cluster uit te voeren. service-mesh agnostisch. resources: - name: git-master resourceRef: name: git-master - name: git-experimental resourceRef: name: git-experimental --- kind: Role apiVersion: rbac.authorization.k8s.io/v1 metadata: name: tekton-trigger-role namespace: stage-tekton-pipeline rules: # Permissions for every EventListener deployment to function - apiGroups: ["tekton.dev"] resources: ["eventlisteners", "triggerbindings", "triggertemplates"] verbs: ["get"] - apiGroups: [""] resources: ["configmaps", "secrets"] # secrets are only needed for Github/Gitlab interceptors verbs: ["get", "list", "watch"] # Permissions to create resources in associated TriggerTemplates - apiGroups: ["tekton.dev"] resources: ["pipelineruns", "pipelineresources", "taskruns"] verbs: ["create"] --- apiVersion: rbac.authorization.k8s.io/v1beta1 kind: ClusterRoleBinding metadata: name: tekton-trigger-role-binding namespace: stage-tekton-pipeline roleRef: apiGroup: rbac.authorization.k8s.io kind: ClusterRole name: tekton-trigger-role subjects: - kind: ServiceAccount name: service-acc namespace: stage-tekton-pipeline --- apiVersion: tekton.dev/v1alpha1 kind: EventListener metadata: name: github-event-listener namespace: stage-tekton-pipeline spec: serviceAccountName: service-acc triggers: - binding: name: github-trigger-binding template: name: github-trigger-template ---