tekton EventListener资源

最新推荐文章于 2025-05-20 17:06:18 发布
最新推荐文章于 2025-05-20 17:06:18 发布
阅读量835 收藏 1
点赞数
分类专栏： k8s实战之kubectl源码分析 文章标签： git
版权声明：本文为博主原创文章，遵循 CC 4.0 BY-SA 版权协议，转载请附上原文出处链接和本声明。
本文链接：https://blog.youkuaiyun.com/hxpjava1/article/details/118441290
版权

 欢迎关注我的公众号：

 目前刚开始写一个月，一共写了18篇原创文章，文章目录如下：

istio多集群探秘，部署了50次多集群后我得出的结论

istio多集群链路追踪，附实操视频

istio防故障利器，你知道几个,istio新手不要读，太难！

istio业务权限控制，原来可以这么玩

istio实现非侵入压缩，微服务之间如何实现压缩

不懂envoyfilter也敢说精通istio系列-http-rbac-不要只会用AuthorizationPolicy配置权限

不懂envoyfilter也敢说精通istio系列-02-http-corsFilter-不要只会vs

不懂envoyfilter也敢说精通istio系列-03-http-csrf filter-再也不用再代码里写csrf逻辑了

不懂envoyfilter也敢说精通istio系列http-jwt_authn-不要只会RequestAuthorization

不懂envoyfilter也敢说精通istio系列-05-fault-filter-故障注入不止是vs

不懂envoyfilter也敢说精通istio系列-06-http-match-配置路由不只是vs

不懂envoyfilter也敢说精通istio系列-07-负载均衡配置不止是dr

不懂envoyfilter也敢说精通istio系列-08-连接池和断路器

不懂envoyfilter也敢说精通istio系列-09-http-route filter

不懂envoyfilter也敢说精通istio系列-network filter-redis proxy

不懂envoyfilter也敢说精通istio系列-network filter-HttpConnectionManager

不懂envoyfilter也敢说精通istio系列-ratelimit-istio ratelimit完全手册

 

tekton新课发布：ci/cd之tekton实战--其他视频教程-系统/网络/运维-优快云程序员研修院

什么是EventListener

连接 TriggerBinding 和 TriggerTemplate 到事件接收器，使用从各个 TriggerBinding 中提取的参数来创建 TriggerTemplate 中指定的 resources，同样通过 interceptor 字段来指定外部服务对事件属性进行预处理

资源详解

triggers

ServiceAccountName

name

bindings

template

eventListener/triggers/sa-rbac.yaml

apiVersion: v1
kind: ServiceAccount
metadata:
  name: tekton-triggers-example-sa
---
apiVersion: rbac.authorization.k8s.io/v1
kind: Role
metadata:
  name: tekton-triggers-example-minimal
rules:
# EventListeners need to be able to fetch all namespaced resources
- apiGroups: ["triggers.tekton.dev"]
  resources: ["eventlisteners", "triggerbindings", "triggertemplates", "triggers"]
  verbs: ["get", "list", "watch"]
- apiGroups: [""]
# configmaps is needed for updating logging config
  resources: ["configmaps"]
  verbs: ["get", "list", "watch"]
# Permissions to create resources in associated TriggerTemplates
- apiGroups: ["tekton.dev"]
  resources: ["pipelineruns", "pipelineresources", "taskruns"]
  verbs: ["create"]
- apiGroups: [""]
  resources: ["serviceaccounts"]
  verbs: ["impersonate"]
- apiGroups: ["policy"]
  resources: ["podsecuritypolicies"]
  resourceNames: ["tekton-triggers"]
  verbs: ["use"]
---
apiVersion: rbac.authorization.k8s.io/v1
kind: RoleBinding
metadata:
  name: tekton-triggers-example-binding
subjects:
- kind: ServiceAccount
  name: tekton-triggers-example-sa
roleRef:
  apiGroup: rbac.authorization.k8s.io
  kind: Role
  name: tekton-triggers-example-minimal
---
kind: ClusterRole
apiVersion: rbac.authorization.k8s.io/v1
metadata:
  name: tekton-triggers-example-clusterrole
rules:
  # EventListeners need to be able to fetch any clustertriggerbindings
- apiGroups: ["triggers.tekton.dev"]
  resources: ["clustertriggerbindings", "clusterinterceptors"]
  verbs: ["get", "list", "watch"]
---
apiVersion: rbac.authorization.k8s.io/v1
kind: ClusterRoleBinding
metadata:
  name: tekton-triggers-example-clusterbinding
subjects:
- kind: ServiceAccount
  name: tekton-triggers-example-sa
  namespace: tekton
roleRef:
  apiGroup: rbac.authorization.k8s.io
  kind: ClusterRole
  name: tekton-triggers-example-clusterrole

eventListener/triggers/task-pipeline.yaml

apiVersion: tekton.dev/v1beta1
kind: Task
metadata:
  name: say-hello
spec:
  params:
  - name: contenttype
    description: The Content-Type of the event
    type: string
  resources:
    inputs:
      - name: git-source
        type: git
  steps:
  - name: say-hi
    image: bash
    command: ["bash", "-c"]
    args:
      - echo -e 'Hello Triggers!\nContent-Type is $(params.contenttype)'
---
apiVersion: tekton.dev/v1beta1
kind: Task
metadata:
  name: say-message
spec:
  params:
  - name: message
    description: The message to print
    default: This is the default message
    type: string
  resources:
    inputs:
    - name: git-source
      type: git
  steps:
  - name: say-message
    image: bash
    command: ["bash", "-c"]
    args:
      - echo '$(params.message)'
---
apiVersion: tekton.dev/v1beta1
kind: Task
metadata:
  name: say-bye
spec:
  resources:
    inputs:
    - name: git-source
      type: git
  steps:
  - name: say-bye
    image: bash
    command: ["bash", "-c"]
    args:
    - echo 'Goodbye Triggers!'
---
apiVersion: tekton.dev/v1beta1
kind: Pipeline
metadata:
  name: simple-pipeline
spec:
  params:
  - name: message
    description: The message to print
    default: This is the default message
    type: string
  - name: contenttype
    description: The Content-Type of the event
    type: string
  resources:
  - name: git-source
    type: git
  tasks:
  - name: say-hello
    taskRef:
      name: say-hello
    params:
    - name: contenttype
      value: $(params.contenttype)
    resources:
      inputs:
      - name: git-source
        resource: git-source
  - name: say-message
    runAfter: [say-hello]
    taskRef:
      name: say-message
    params:
    - name: message
      value: $(params.message)
    resources:
      inputs:
      - name: git-source
        resource: git-source
  - name: say-bye
    runAfter: [say-message]
    taskRef:
      name: say-bye
    resources:
      inputs:
      - name: git-source
        resource: git-source

eventListener/triggers/trigger-template.yaml

apiVersion: triggers.tekton.dev/v1alpha1
kind: TriggerTemplate
metadata:
  name: pipeline-template
spec:
  params:
  - name: gitrevision
    description: The git revision
    default: main
  - name: gitrepositoryurl
    description: The git repository url
  - name: message
    description: The message to print
    default: This is the default message
  - name: contenttype
    description: The Content-Type of the event
  resourcetemplates:
  - apiVersion: tekton.dev/v1beta1
    kind: PipelineRun
    metadata:
      generateName: simple-pipeline-run-
    spec:
      pipelineRef:
        name: simple-pipeline
      params:
      - name: message
        value: $(tt.params.message)
      - name: contenttype
        value: $(tt.params.contenttype)
      resources:
      - name: git-source
        resourceSpec:
          type: git
          params:
          - name: revision
            value: $(tt.params.gitrevision)
          - name: url
            value: $(tt.params.gitrepositoryurl)

eventListener/triggers/message-binding.yaml

apiVersion: triggers.tekton.dev/v1alpha1
kind: TriggerBinding
metadata:
  name: message-binding
spec:
  params:
  - name: message
    value: Hello from the Triggers EventListener!

eventListener/triggers/pipeline-binding.yaml

apiVersion: triggers.tekton.dev/v1alpha1
kind: TriggerBinding
metadata:
  name: pipeline-binding
spec:
  params:
  - name: gitrevision
    value: $(body.head_commit.id)
  - name: gitrepositoryurl
    value: $(body.repository.url)
  - name: contenttype
    value: $(header.Content-Type)

eventListener/triggers/listener.yaml

apiVersion: triggers.tekton.dev/v1alpha1
kind: EventListener
metadata:
  name: listener
spec:
  serviceAccountName: tekton-triggers-example-sa
  triggers:
    - name: foo-trig
      bindings:
        - ref: pipeline-binding
        - ref: message-binding
      template:
        ref: pipeline-template

curl -v -H 'X-GitHub-Event: pull_request' -H 'X-Hub-Signature: sha1=9c971b694ecd99a5753653032e5ceb332e29f2d1' -H 'Content-Type: application/json' -d '{"action": "opened", "pull_request":{"head":{"sha": "28911bbb5a3e2ea034daf1f6be0a822d50e31e73"}},"repository":{"url": "https://github.com/tektoncd/triggers.git"}}' http://10.68.194.93:8080

interceptors

Event Interceptors can take several different forms today:

webhook

eventListener/interceptors/webhook-deployment.yaml

apiVersion: apps/v1
kind: Deployment
metadata:
  name: gh-validate
  namespace: tekton
spec:
  replicas: 1
  selector:
    matchLabels:
      app: gh-validate
  template:
    metadata:
      labels:
        app: gh-validate
    spec:
      serviceAccountName: default
      containers:
        - name: validate
          image: registry.cn-shanghai.aliyuncs.com/hxpdocker/webhook-interceptors:latest
          env:
            - name: GITHUB_SECRET_TOKEN
              valueFrom:
                secretKeyRef:
                  name: github-secret
                  key: secret-token
---
apiVersion: v1
kind: Service
metadata:
  name: gh-validate
  namespace: tekton
spec:
  type: ClusterIP
  selector:
    app: gh-validate
  ports:
    - protocol: TCP
      port: 80
      targetPort: 8080

eventListener/interceptors/github-secret.yaml

apiVersion: v1
kind: Secret
metadata:
  name: github-secret
type: Opaque
stringData:
  secretToken: "1234567"

eventListener/interceptors/webhook-listener.yaml

apiVersion: v1
kind: Secret
metadata:
  name: github-secret
type: Opaque
stringData:
  secretToken: "1234567"
---
apiVersion: triggers.tekton.dev/v1alpha1
kind: EventListener
metadata:
  name: listener
spec:
  serviceAccountName: tekton-triggers-example-sa
  triggers:
    - name: foo-trig
      interceptors:
        - ref:
            name: "github"
          params:
          - name: "secretRef"
            value:
              secretName: github-secret
              secretKey: secretToken
          - name: "eventTypes"
            value: ["pull_request"]
        - webhook:
            header:
              - name: Foo-Trig-Header1
                value: string-value
              - name: Foo-Trig-Header2
                value:
                  - array-val1
                  - array-val2
            objectRef:
              kind: Service
              name: gh-validate
              apiVersion: v1
              namespace: tekton
      bindings:
        - ref: pipeline-binding
        - ref: message-binding
      template:
        ref: pipeline-template

curl -v -H 'X-GitHub-Event: pull_request' -H 'X-Hub-Signature: sha1=9c971b694ecd99a5753653032e5ceb332e29f2d1' -H 'Content-Type: application/json' -d '{"action": "opened", "pull_request":{"head":{"sha": "28911bbb5a3e2ea034daf1f6be0a822d50e31e73"}},"repository":{"url": "https://github.com/tektoncd/triggers.git"}}' http://10.68.194.93:8080

github

eventListener/interceptors/github-secret.yaml

apiVersion: v1
kind: Secret
metadata:
  name: github-secret
type: Opaque
stringData:
  secretToken: "1234567"

eventListener/interceptors/github-01.yaml

apiVersion: triggers.tekton.dev/v1alpha1
kind: EventListener
metadata:
  name: listener
spec:
  serviceAccountName: tekton-triggers-example-sa
  triggers:
    - name: foo-trig
      interceptors:
      - github:
          eventTypes: ["pull_request"]
      bindings:
        - ref: pipeline-binding
        - ref: message-binding
      template:
        ref: pipeline-template


curl -v -H 'X-GitHub-Event: pull_request' -H 'X-Hub-Signature: sha1=9c971b694ecd99a5753653032e5ceb332e29f2d1' -H 'Content-Type: application/json' -d '{"action": "opened", "pull_request":{"head":{"sha": "28911bbb5a3e2ea034daf1f6be0a822d50e31e73"}},"repository":{"url": "https://github.com/tektoncd/triggers.git"}}' http://10.68.194.93:8080

eventListener/interceptors/github-02.yaml

apiVersion: triggers.tekton.dev/v1alpha1
kind: EventListener
metadata:
  name: listener
spec:
  serviceAccountName: tekton-triggers-example-sa
  triggers:
    - name: foo-trig
      interceptors:
        - ref:
            name: "github"
          params:
            - name: "secretRef"
              value:
                secretName: github-secret
                secretKey: secretToken
            - name: "eventTypes"
              value: ["pull_request"]
      bindings:
        - ref: pipeline-binding
        - ref: message-binding
      template:
        ref: pipeline-template

curl -v -H 'X-GitHub-Event: pull_request' -H 'X-Hub-Signature: sha1=9c971b694ecd99a5753653032e5ceb332e29f2d1' -H 'Content-Type: application/json' -d '{"action": "opened", "pull_request":{"head":{"sha": "28911bbb5a3e2ea034daf1f6be0a822d50e31e73"}},"repository":{"url": "https://github.com/tektoncd/triggers.git"}}' http://10.68.194.93:8080

产生X-Hub-Signature

Free Online HMAC Generator / Checker Tool (MD5, SHA-256, SHA-512) - FreeFormatter.com

gitlab

eventListener/interceptors/gitlab-secret.yaml

apiVersion: v1
kind: Secret
metadata:
  name: gitlab-secret
type: Opaque
stringData:
  secretToken: "1234567"

eventListener/interceptors/gitlab-listener.yaml

apiVersion: triggers.tekton.dev/v1alpha1
kind: EventListener
metadata:
  name: listener
spec:
  serviceAccountName: tekton-triggers-example-sa
  triggers:
    - name: foo-trig
      interceptors:
        - name: "verify-gitlab-payload"
          ref:
            name: "gitlab"
            kind: ClusterInterceptor
          params:
            - name: secretRef
              value:
                secretName: "gitlab-secret"
                secretKey: "secretToken"
            - name: eventTypes
              value:
                - "Push Hook"
      bindings:
        - ref: pipeline-binding
        - ref: message-binding
      template:
        ref: pipeline-template

gitlab-push-event.json

{
  "object_kind": "push",
  "event_name": "push",
  "before": "1a1736ec3d7b03349b31218a2f2c572c7c7206d6",
  "after": "1a1736ec3d7b03349b31218a2f2c572c7c7206d6",
  "ref": "refs/heads/main",
  "checkout_sha": "1a1736ec3d7b03349b31218a2f2c572c7c7206d6",
  "message": null,
  "user_id": 111448,
  "user_name": "Dibyo Mukherjee",
  "user_username": "dibyom",
  "user_email": "",
  "user_avatar": "https://secure.gravatar.com/avatar/1d56773f447d86b8ffa33efb7a5d0cb5?s=80&d=identicon",
  "project_id": 16507326,
  "project": {
    "id": 16507326,
    "name": "triggers",
    "description": "",
    "web_url": "https://gitlab.com/dibyom/triggers",
    "avatar_url": null,
    "git_ssh_url": "git@gitlab.com:dibyom/triggers.git",
    "git_http_url": "https://gitlab.com/dibyom/triggers.git",
    "namespace": "Dibyo Mukherjee",
    "visibility_level": 20,
    "path_with_namespace": "dibyom/triggers",
    "default_branch": "main",
    "ci_config_path": null,
    "homepage": "https://gitlab.com/dibyom/triggers",
    "url": "git@gitlab.com:dibyom/triggers.git",
    "ssh_url": "git@gitlab.com:dibyom/triggers.git",
    "http_url": "https://gitlab.com/dibyom/triggers.git"
  },
  "commits": [
    {
      "id": "1a1736ec3d7b03349b31218a2f2c572c7c7206d6",
      "message": "Add new file",
      "timestamp": "2020-01-24T17:05:48+00:00",
      "url": "https://gitlab.com/dibyom/triggers/-/commit/1a1736ec3d7b03349b31218a2f2c572c7c7206d6",
      "author": {
        "name": "Dibyo Mukherjee",
        "email": "foo@bar.com"
      },
      "added": ["Readme.md"],
      "modified": [],
      "removed": []
    }
  ],
  "total_commits_count": 1,
  "push_options": {},
  "repository": {
    "name": "triggers",
    "url": "https://github.com/tektoncd/triggers.git",
    "description": "",
    "homepage": "https://gitlab.com/dibyom/triggers",
    "git_http_url": "https://gitlab.com/dibyom/triggers.git",
    "git_ssh_url": "git@gitlab.com:dibyom/triggers.git",
    "visibility_level": 20
  }
}

curl -v \
-H 'X-GitLab-Token: 1234567' \
-H 'X-Gitlab-Event: Push Hook' \
-H 'Content-Type: application/json' \
--data-binary "@gitlab-push-event.json" \
http://10.68.194.93:8080

bitbucket

eventListener/interceptors/bitbucket-secret.yaml

apiVersion: v1
kind: Secret
metadata:
  name: bitbucket-secret
type: Opaque
stringData:
  secretToken: "1234567"

eventListener/interceptors/bitbucket-binding.yaml

apiVersion: triggers.tekton.dev/v1alpha1
kind: TriggerBinding
metadata:
  name: bitbucket-binding
spec:
  params:
    - name: gitrevision
      value: $(body.changes[0].ref.displayId)
    - name: gitrepositoryurl
      value: $(body.repository.links.clone[0].href)

eventListener/interceptors/bitbucket-listener.yaml

apiVersion: triggers.tekton.dev/v1alpha1
kind: EventListener
metadata:
  name: listener
spec:
  serviceAccountName: tekton-triggers-example-sa
  triggers:
    - name: foo-trig
      interceptors:
        - ref:
            name: "bitbucket"
          params:
            - name: secretRef
              value:
                secretName: bitbucket-secret
                secretKey: secretToken
            - name: eventTypes
              value:
                - repo:refs_changed
      bindings:
        - ref: bitbucket-binding
        - ref: message-binding
      template:
        ref: pipeline-template


curl -v \
-H 'X-Event-Key: repo:refs_changed' \
-H 'X-Hub-Signature: sha1=e3978add92171e0b3a5b37539064d784d0b1b731' \
-d '{"repository": {"links": {"clone": [{"href": "https://github.com/tektoncd/triggers.git", "name": "http"}, {"href": "ssh://git@localhost:7999/~test/helloworld.git", "name": "ssh"}]}}, "changes": [{"ref": {"displayId": "main"}}]}' \
http://10.68.194.93:8080

cel

eventListener/interceptors/cel-01.yaml

apiVersion: triggers.tekton.dev/v1alpha1
kind: EventListener
metadata:
  name: listener
spec:
  serviceAccountName: tekton-triggers-example-sa
  triggers:
    - name: cel-trig-with-matches
      interceptors:
        - ref:
            name: "cel"
          params:
            - name: "filter"
              value: "header.match('X-GitHub-Event', 'pull_request')"
            - name: "overlays"
              value:
                - key: truncated_sha
                  expression: "body.pull_request.head.sha.truncate(7)"
      bindings:
        - name: sha
          value: $(extensions.truncated_sha)
        - ref: pipeline-binding
        - ref: message-binding
      template:
        ref: pipeline-template

curl -v -H 'X-GitHub-Event: pull_request' -H 'X-Hub-Signature: sha1=9c971b694ecd99a5753653032e5ceb332e29f2d1' -H 'Content-Type: application/json' -d '{"action": "opened", "pull_request":{"head":{"sha": "28911bbb5a3e2ea034daf1f6be0a822d50e31e73"}},"repository":{"url": "https://github.com/tektoncd/triggers.git"}}' http://10.68.194.93:8080

compareSecret

eventListener/interceptors/cel-02.yaml

apiVersion: v1
kind: Secret
metadata:
  name: mysecret
type: Opaque
data:
  token: dGVzdC1zZWNyZXQ=
---
apiVersion: triggers.tekton.dev/v1alpha1
kind: EventListener
metadata:
  name: listener
spec:
  serviceAccountName: tekton-triggers-example-sa
  triggers:
    - name: cel-trig-with-matches
      interceptors:
      - ref:
          name: "cel"
        params:
        - name: "filter"
          value: "'test-secret'.compareSecret('token', 'mysecret')"
      bindings:
        - ref: pipeline-binding
        - ref: message-binding
      template:
        ref: pipeline-template

curl -v -H 'X-GitHub-Event: pull_request' -H 'X-Hub-Signature: sha1=9c971b694ecd99a5753653032e5ceb332e29f2d1' -H 'Content-Type: application/json' -d '{"action": "opened", "pull_request":{"head":{"sha": "28911bbb5a3e2ea034daf1f6be0a822d50e31e73"}},"repository":{"url": "https://github.com/tektoncd/triggers.git"}}' http://10.68.194.93:8080

triggerRef

eventListener/interceptors/triggerRef-trigger.yaml

apiVersion: triggers.tekton.dev/v1alpha1
kind: Trigger
metadata:
  name: trigger
spec:
  interceptors:
    - cel:
        filter: "header.match('X-GitHub-Event', 'pull_request')"
        overlays:
        - key: extensions.truncated_sha
          expression: "body.pull_request.head.sha.truncate(7)"
  bindings:
  - ref: pipeline-binding
  template:
    ref: pipeline-template

eventListener/interceptors/triggerRef-listener.yaml

apiVersion: triggers.tekton.dev/v1alpha1
kind: EventListener
metadata:
  name: listener
spec:
  serviceAccountName: tekton-triggers-example-sa
  triggers:
  - triggerRef: trigger

curl -v -H 'X-GitHub-Event: pull_request' -H 'X-Hub-Signature: sha1=9c971b694ecd99a5753653032e5ceb332e29f2d1' -H 'Content-Type: application/json' -d '{"action": "opened", "pull_request":{"head":{"sha": "28911bbb5a3e2ea034daf1f6be0a822d50e31e73"}},"repository":{"url": "https://github.com/tektoncd/triggers.git"}}'  http://10.68.194.93:8080

serviceaccount

eventListener/interceptors/serviceaccount-listener.yaml

apiVersion: triggers.tekton.dev/v1alpha1
kind: EventListener
metadata:
  name: listener
spec:
  serviceAccountName: tekton-triggers-example-sa
  triggers:
    - name: foo-trig
      serviceAccountName: tekton-triggers-example-sa
      interceptors:
      - github:
          eventTypes: ["pull_request"]
      bindings:
        - ref: pipeline-binding
        - ref: message-binding
      template:
        ref: pipeline-template

curl -v -H 'X-GitHub-Event: pull_request' -H 'X-Hub-Signature: sha1=9c971b694ecd99a5753653032e5ceb332e29f2d1' -H 'Content-Type: application/json' -d '{"action": "opened", "pull_request":{"head":{"sha": "28911bbb5a3e2ea034daf1f6be0a822d50e31e73"}},"repository":{"url": "https://github.com/tektoncd/triggers.git"}}' http://10.68.194.93:8080

template/ spec

eventListener/interceptors/template-spec-listener.yaml

apiVersion: triggers.tekton.dev/v1alpha1
kind: EventListener
metadata:
  name: listener
spec:
  serviceAccountName: tekton-triggers-example-sa
  triggers:
  - name: foo-trig
    interceptors:
    - github:
        eventTypes: ["pull_request"]
    bindings:
    - ref: pipeline-binding
    - ref: message-binding
    template:
      spec: 
        params:
        - name: "message"
        - name: gitrevision
          description: The git revision
          default: main
        resourceTemplates:
        - apiVersion: "tekton.dev/v1beta1"
          kind: TaskRun
          metadata:
            generateName: "pr-run-"
          spec:
            taskSpec:
              steps:
              - image: ubuntu
                script: echo "$(tt.params.message)"

curl -v -H 'X-GitHub-Event: pull_request' -H 'X-Hub-Signature: sha1=9c971b694ecd99a5753653032e5ceb332e29f2d1' -H 'Content-Type: application/json' -d '{"action": "opened", "pull_request":{"head":{"sha": "28911bbb5a3e2ea034daf1f6be0a822d50e31e73"}},"repository":{"url": "https://github.com/tektoncd/triggers.git"}}' http://10.68.194.93:8080

ServiceType

eventListener/ServiceType-01.yaml

apiVersion: triggers.tekton.dev/v1alpha1
kind: EventListener
metadata:
  name: listener
spec:
  serviceAccountName: tekton-triggers-example-sa
  triggers:
    - name: foo-trig
      bindings:
        - ref: pipeline-binding
        - ref: message-binding
      template:
        ref: pipeline-template
  resources:
    kubernetesResource:
      serviceType: NodePort

Replicas

eventListener/Replicas-listener-01.yaml

apiVersion: triggers.tekton.dev/v1alpha1
kind: EventListener
metadata:
  name: listener
spec:
  serviceAccountName: tekton-triggers-example-sa
  triggers:
    - name: foo-trig
      bindings:
        - ref: pipeline-binding
        - ref: message-binding
      template:
        ref: pipeline-template
  resources:
    kubernetesResource:
      replicas: 2

eventListener/Replicas-listener-02.yaml

apiVersion: triggers.tekton.dev/v1alpha1
kind: EventListener
metadata:
  name: listener
spec:
  serviceAccountName: tekton-triggers-example-sa
  triggers:
    - name: foo-trig
      bindings:
        - ref: pipeline-binding
        - ref: message-binding
      template:
        ref: pipeline-template
  replicas: 2

PodTemplate

eventListener/PodTemplate-01.yaml

apiVersion: triggers.tekton.dev/v1alpha1
kind: EventListener
metadata:
  name: listener
spec:
  serviceAccountName: tekton-triggers-example-sa
  resources:
    kubernetesResource:
      spec:
        template:
          spec:
            nodeSelector:
              kubernetes.io/hostname: 192.168.198.154
  triggers:
    - name: foo-trig
      bindings:
        - ref: pipeline-binding
        - ref: message-binding
      template:
        ref: pipeline-template

eventListener/PodTemplate-02.yaml

apiVersion: triggers.tekton.dev/v1alpha1
kind: EventListener
metadata:
  name: listener
spec:
  podTemplate:
    nodeSelector:
      kubernetes.io/hostname: 192.168.198.154
  serviceAccountName: tekton-triggers-example-sa
  triggers:
    - name: foo-trig
      bindings:
        - ref: pipeline-binding
        - ref: message-binding
      template:
        ref: pipeline-template

Resources

Right now the allowed values as part of podSpec are

ServiceAccountName
NodeSelector
Tolerations
Volumes
Containers
- Resources
- VolumeMounts
- Env


spec:
  resources:
    kubernetesResource:
      serviceType: NodePort
      spec:
        template:
          metadata:
            labels:
              key: "value"
            annotations:
              key: "value"
          spec:
            serviceAccountName: tekton-triggers-github-sa
            nodeSelector:
              app: test
            tolerations:
            - key: key
              value: value
              operator: Equal
              effect: NoSchedule

NamespaceSelector

This field determines the namespaces where EventListener can search for triggers and create Tekton resources. If this field isn’t provided, EventListener will only serve Triggers from its own namespace.

kubectl create clusterrolebinding listener-binding --clusterrole=cluster-admin --serviceaccount=tekton:tekton-triggers-example-sa

eventListener/NamespaceSelector-01.yaml

apiVersion: triggers.tekton.dev/v1alpha1
kind: EventListener
metadata:
  name: listener
spec:
  namespaceSelector:
    matchNames:
    - *
  serviceAccountName: tekton-triggers-example-sa
  triggers:
    - name: foo-trig
      bindings:
        - ref: pipeline-binding
        - ref: message-binding
      template:
        ref: pipeline-template

curl -v -H 'X-GitHub-Event: pull_request' -H 'X-Hub-Signature: sha1=9c971b694ecd99a5753653032e5ceb332e29f2d1' -H 'Content-Type: application/json' -d '{"action": "opened", "pull_request":{"head":{"sha": "28911bbb5a3e2ea034daf1f6be0a822d50e31e73"}},"repository":{"url": "https://github.com/tektoncd/triggers.git"}}' http://10.68.239.247:8080
理解和应用持续集成-Tekton
qiaotl的博客
07-19 756
通过实际例子演示Tekton如何从github拉取代码完成镜像生成和push，也演示了如何和gitlab的webhook集成，完成job的触发。
Tekton入门
qq_35311140的博客
11-17 9274
Tekton入门 什么是流水线 流水线是把一个重复的过程分解为若干个子过程，使每个子过程与其他子过程并行进行的技术，也叫 Pipeline。以“构建镜像更新应用”为例： 当一次代码变更之后，jenkins都需要拉取最新的代码，进行代码编译，构建镜像，推送镜像到镜像仓库，最后更新k8s资源对象。而且每次代码变更，此过程都是不变的。所以使用流水线工具可以极大的提升这一过程的效率，只需要进行简单的配置便可以轻松的完成重复性的工作，这样的过程也被称之为 CI。 什么是Tekton Tekton 是一个基于 Kube
tekton入门 - trigger
yevvzi的博客
07-03 811
trigger trigger使用户能够将事件有效负载中的字段映射到资源模板中。 换句话说，这允许事件既可以建模也可以将实例化为Kubernetes资源。 对于tektoncd/pipeline，这使得将配置封装到PipelineRuns和PipelineResources中变得容易。 安装 kubectl apply --filename https://storage.googleapis.com/tekton-releases/triggers/latest/release.yaml Trigger
Tekton 基于 cronjob 触发流水线
IT
12-14 914
因为 EventListener 最终需要创建 taskrun、pipelinerun 同时会查询一些其他信息，因此需要为其配置一个 serviceAccount，同时还需要为这个 serviceAccount 赋予相应的权限。EventListener 是一个 Kubernetes 对象，用于侦听 Kubernetes 集群上指定端口上的事件。TriggerTemplate 是指定资源蓝图的资源，例如 TaskRun 或 PipelineRun ，当您的EventListener 检测到事件。
云原生CI/CD：Tekton之trigger介绍
学习学习再学习
07-14 1689
云原生CI/CD：Tekton之trigger组件 简介 上面背景图片用了一张手枪扳机的图片，啥意思呢？trigger对于pipeline的作用就像扳机对于手枪的作用的，读完文章再来体会这句话。 前面我们学过tekton的pipeline组件，里面可以运行自定义工作流任务，而这些工作流任务例如task和pipeline都需要对象的触发对象例如taskrun和pipelineRun。触发的方式有两种：手动kubectl apply 文件触发和client-go触发。tekton为大家选择第三种方式，使用ap
云原生Tekton之触发器Trigger
学习学习再学习
07-07 1517
背景 前面的文章讲了tekton中pipeline的教程和使用案例，大家有没有想过，每次都要运行taskrun或者pipelineRun才能真正运行流水线。那怎么做到自动化执行taskrun和pipelineRun呢？我想了下有两种方式： 使用client-go去创建taskRun和pipelineRun 使用tekton的另一个组件trigger触发器。 单纯运行taskrun和pipelineRun，或者实例化以下task和pipeline,那么选用trigger会比较好，因为不需要额外开发，只需.
Tekton Interceptor拓展
m0_62729235的博客
05-13 244
关于Tekton Interceptor拓展
云原生 | 配置Tekton&Argo cd完成简单的CI/CD
杜小帅的博客
04-03 1018
实时监听git仓库中k8s资源清单当资源清单文件被修改是会自动更新将新的部署配置应用到k8s集群并且支持查看应用状态，回滚，健康检查。
云原生CICD-Tekton入门到精通
最新发布
小杨同学的博客
05-20 1795
Tekton是一个开源的云原生持续集成和持续交付/部署（Cloud Native CI/CD）解决方案，它使用Golang语言开发，允许开发人员通过Kubernetes（K8S）云平台快速灵活定义流水线，从而更加便捷地构建、测试和部署系统。
Kubernetes CICD系列之tekton工具使用
邢宁
03-11 2663
前言 Tekton是一种适用于创建持续集成和持续部署/交付(CI/CD)系统的谷歌开源的Kubernetes原生框架，它支持多云/多集群下进行搭建、测试和部署，可实现滚动部署、蓝/绿部署、金丝雀部署或 GitOps 工作流等高级部署。 Jenkins的不足 基于脚本的job配置复用率不足 代码调试困难 基于声明式API的流水线-Tekton 自定义 可重用 可扩展性 标准化 规模化支持 Tekton 核心组件 pipline: 对象定义了一个流水线作业，一个pipeline对象由一个或数个ta
Tekton 基于 gitlab 触发流水线
IT
12-14 1929
因为 EventListener 最终需要创建 taskrun、pipelinerun 同时会查询一些其他信息，因此需要为其配置一个 serviceAccount，同时还需要为这个 serviceAccount 赋予相应的权限。EventListener 是一个 Kubernetes 对象，用于侦听 Kubernetes 集群上指定端口上的事件。TriggerTemplate 是指定资源蓝图的资源，例如 TaskRun 或 PipelineRun ，当您的EventListener 检测到事件。
Tekton笔记(二)之github webhook
weixin_42574058的博客
09-13 796
本文使用github webhook来触发tekton。
云原生的 CI/CD 框架tekton - Trigger（二）
最美dee时光的博客
12-05 1248
上一篇为大家详细介绍了，由于里面涉及到的概念比较多，因此需要好好消化下。同样，今天在特别为大家分享下tekton - Trigger以及案例演示，希望可以给大家提供一种思路哈。
(译) Tekton 官方使用手册-入门篇
weixin_43014389的博客
04-20 574
Tekton是Kubernetes原生的持续集成和交付(CI/CD)解决方案之一。它允许开发人员在混合云或私有云中进行构建、测试和部署 Tekton官方提供了较多的交互式教程，便于开发者直接实践应用此工具。想快速上手可以点击： https://tekton.dev/try 前提条件： Kubernetes群集版本1.15或更高版本建议使用Tekton Pipeline v0.11.0或更高版...
OpenShift 4 Tekton (1) - OpenShift Pipeline入门-安装Pipeline Operator
多恩斯基的博客
09-05 1200
《OpenShift 4.x HOL教程汇总》 说明：本文已经在OpenShift 4.8环境中验证 文章目录Tekton 简介准备环境 Tekton 简介 Tekton，最初被称为Knative Build，但作为自己的开源项目分离出来，有自己的管理组织。Tekton试图填补集群内容器镜像构建和部署工作流程的空白，即持续集成（CI）和持续交付（CD）。Tekton的理念围绕三个方面展开： 容器 Tekton的座右铭是Kubernetes原生。容器是任何Kubernetes集群的核心，Tekton为容器化应
k8s全栈技术讲解+企业案例演示[带你快速掌握和使用k8s]【进阶版】
06-03
一、为什么学习kubernetes众所周知，随着容器的快速发展，容器管理工具kubernetes也应运而生，目前不仅百度、京东、阿里、google等大公司在使用kubernetes，一些中小企业也开始把业务迁移到kubernetes，那么作为运维、开发、测试或者架构师来说，必须要掌握这项技术，才能提现我们的工作价值，才能在行业具备保持较高的技术水平，kubernetes作为成熟的容器编排工具，具有容器集群的自动化部署、自动化伸缩和故障自恢复的能力，让容器的部署和管理变得更加容易，能够给企业和提供一个智能化的容器云管理平台，为企业快速上云提供一个安全可靠的解决方案，此课程主要介绍kubernetes1.14/kubernetes1.15版本高可用集群的安装部署和使用，通过我多年工作经验总结，带你深入体验企业实战案例，让您轻松快速的掌握k8s，接下来让我们一起出发吧。 二、课程亮点 三、讲师简介 先超（lucky）：高级运维工程师、资深DevOps工程师，在互联网上市公司拥有多年一线运维经验，主导过亿级pv项目的架构设计和运维工作 主要研究方向： 1.云计算方向：容器 （kubernetes、docker），虚拟化（kvm、Vmware vSphere），微服务（istio），PaaS（openshift），IaaS（openstack）等2.系统/运维方向：linux系统下的常用组件（nginx，tomcat，elasticsearch，zookeeper，kafka等），DevOps（Jenkins+gitlab+sonarqube+nexus+k8s），CI/CD，监控（zabbix、prometheus、falcon）等.
OpenShift 4 Tekton - 用Webhook实现CI/CD
多恩斯基的博客
03-27 1474
文章目录场景说明Tekton实现Webhook的过程和相关对象本文的Pipeline场景说明场景实现复制Github项目对pipelines-tutorial项目的操作创建Pipeline，然后直接运行Pipeline配置Webhook，然后通过Webhook运行Pipeline 场景说明 Tekton实现Webhook的过程和相关对象 为了实现Tekton Webhook需要先在OpenShif...
tekton试用
沈首二
04-16 7358
这里写自定义目录标题介绍部署修改依赖镜像安装示例任务的输入定义任务输出定义镜像仓库认证创建secret创建serviceaccount定义Task定义TaskRun完整的yaml执行示例 介绍 谷歌开源了一个 Kubernetes 原生 CI/CD 构建框架——Tekton Tekton 是一个功能强大且灵活的 Kubernetes 原生框架，用于创建 CI/CD 系统。通过抽象出底层实现细节，...
tekton入门 - pipline
yevvzi的博客
07-03 795
pipline总览 PipelineRun允许您实例化并执行集群上的。A 以所需的执行顺序Pipeline指定一个或多个Tasks。一个PipelineRun 执行Tasks中Pipeline，直到所有的顺序，他们被指定Tasks已成功执行或出现故障。 注意： A会PipelineRun自动TaskRuns为中的每个 创建对应Task的内容Pipeline。 该Status字段跟踪的当前状态PipelineRun，并可用于监视进度。此字段包含每个的状态TaskRun，以及PipelineSpec用于实例化此
tekton eventlisener
05-18
Tekton EventListener 是 Tekton Pipeline 的一个组件，用于监听事件并触发 Pipeline 的执行。通过 EventListener，我们可以在 Kubernetes 中创建一个服务，用于接收外部的事件，然后根据事件的内容触发相应的 ...
评论
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

当前余额3.43元 前往充值 >
需支付：10.00元
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包

打赏作者

hxpjava1

你的鼓励将是我创作的最大动力

¥1 ¥2 ¥4 ¥6 ¥10 ¥20
扫码支付：¥1
获取中
扫码支付

您的余额不足，请更换扫码支付或充值

打赏作者

实付元
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明：

1.余额是钱包充值的虚拟货币，按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载，可以购买VIP、付费专栏及课程。

余额充值