kubevela / kube-trigger Goto Github PK

Let's refactor the schema to be:

triggers:
  -   k8s-resource-watcher:
       apiVersion: v1
       kind: ConfigMap
       namespace: default
       # Only watch update event.
       events:
         - update
    filters:
      # Filter the events above.
      - cue-validator:
          template: |
            metadata: name: =~"this-will-trigger-update-.*"
    actions:
      - bump-application-revision:
          namespace: default
          labelSelectors:
            my-label: my-value

It can be more convenient as trigger config.

Describe the bug
Getting the error

The ClusterRole "kube-trigger-manager-role" is invalid: rules[0].apiGroups: Required value: resource rules must supply at least one api group

when applying config/manager/role.yaml file.

To Reproduce
Steps to reproduce the behavior:

1. Follow the Quick Start guide.
2. Apply all the files in config/crd, config/definition, and config/manager respectively.
3. kubectl apply -f will throw the error when trying to apply role.yaml.

Expected behavior
Successful creation of ClusterRole kube-trigger-manager-role

Kube Trigger Version

• kube-trigger version: 1.0.0 (kube-trigger addon)

Cluster information

• Minikube version: v1.30.1
• Kuberentes version: v1.24.13
• Kubevela version: v1.8.1

Additional context
I enabled the kube-trigger addon after installing kubevela .

1. vela ql can get the pods from application, with resource topology featrues.
2. kube-trigger could watch and filter events from pods.
3. kube-trigger could send the event to loki/clickhouse or other storage for log.
4. o11y addon can read that events.
5. we can also add vector addon for transform logs.

Real scenario： kubevela/kubevela#1365

Is your feature request related to a problem? Please describe.

Support more unit tests to make the test coverage to 60%

Describe the solution you'd like

Describe alternatives you've considered

Additional context

Is your feature request related to a problem? Please describe.

And please also add badges into README Including :

• CI codecov
• GitHub release
• Docker Pulls
• Go Report
• TODOs
• gitter
• license
• etc..

refer to the kubevela repo for details.

Describe the solution you'd like

Describe alternatives you've considered

Additional context

• Start a default TriggerInstance once controller is deployed, named default (optionally this feature can be disabled)
• TriggerService without selectors automatically uses the default instance
• change label app: xxx to instance: xxx

There is the following task - need to create a kubernetes job (or triger it from a cronjob) or execute a kubectl command at a certain Kubernetes event.

I couldn't find such functionality (v0.1.1).
Please tell me if such functionality is available now or these are plans for the future.
Where can I view all possible "actions"?

Thank you!