kubevela / kube-trigger Goto Github PK

View Code? Open in Web Editor NEW

52.0 52.0 16.0 658 KB

kube-trigger watches events and triggers actions in a programmable way.

License: Apache License 2.0

Go 83.25% Makefile 10.77% Shell 2.67% Python 3.31%

controller crd kubernetes trigger

kube-trigger's Introduction

Make shipping applications more enjoyable.

Introduction

KubeVela is a modern application delivery platform that makes deploying and operating applications across today's hybrid, multi-cloud environments easier, faster and more reliable.

Highlights

KubeVela practices the "render, orchestrate, deploy" workflow with below highlighted values added to existing ecosystem:

Deployment as Code

Declare your deployment plan as workflow, run it automatically with any CI/CD or GitOps system, extend or re-program the workflow steps with CUE. No ad-hoc scripts, no dirty glue code, just deploy. The deployment workflow in KubeVela is powered by Open Application Model.

Built-in observability, multi-tenancy and security support

Choose from the wide range of LDAP integrations we provided out-of-box, enjoy enhanced multi-tenancy and multi-cluster authorization and authentication, pick and apply fine-grained RBAC modules and customize them as per your own supply chain requirements. All delivery process has fully automated observability dashboards.

Multi-cloud/hybrid-environments app delivery as first-class citizen

Natively supports multi-cluster/hybrid-cloud scenarios such as progressive rollout across test/staging/production environments, automatic canary, blue-green and continuous verification, rich placement strategy across clusters and clouds, along with automated cloud environments provision.

Lightweight but highly extensible architecture

Minimize your control plane deployment with only one pod and 0.5c1g resources to handle thousands of application delivery. Glue and orchestrate all your infrastructure capabilities as reusable modules with a highly extensible architecture and share the large growing community addons.

Getting Started

Documentation

Full documentation is available on the KubeVela website.

Blog

Official blog is available on KubeVela blog.

Community

We want your contributions and suggestions! One of the easiest ways to contribute is to participate in discussions on the Github Issues/Discussion, chat on IM or the bi-weekly community calls. For more information on the community engagement, developer and contributing guidelines and more, head over to the KubeVela community repo.

Contact Us

Reach out with any questions you may have and we'll make sure to answer them as soon as possible!

Slack: CNCF Slack kubevela channel (English)
DingTalk Group: 23310022 (Chinese)
Wechat Group (Chinese): Broker wechat to add you into the user group.

Community Call

Every two weeks we host a community call to showcase new features, review upcoming milestones, and engage in a Q&A. All are welcome!

Bi-weekly Community Call:
- Meeting Notes.
- Video Records.
Bi-weekly Chinese Community Call:
- Video Records.

Talks and Conferences

Check out KubeVela videos for these talks and conferences.

Contributing

Check out CONTRIBUTING to see how to develop with KubeVela.

Report Vulnerability

Security is a first priority thing for us at KubeVela. If you come across a related issue, please send email to [email protected] .

Code of Conduct

KubeVela adopts CNCF Code of Conduct.

kube-trigger's People

Contributors

Stargazers

Watchers

Forkers

charlie0129 leil24 mcduller yangsoon fogdong rayoluo somefive semmet95 luis-sousa-pinto web-logs2 sanyu

kube-trigger's Issues

Support notification events from communication system

Add api group to clusterrole's first rule in config/manager

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:

Follow the Quick Start guide.
Apply all the files in config/crd, config/definition, and config/manager respectively.
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 .

User experience enhancements

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

make kind name "KubeTriggerConfig" to be "TriggerService"

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.

Support data stream events from middle-ware services (e.g kafka)

[Question] Execute kubectl command / create k8s resource

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!

support collecting event of pods in vela application

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

Real scenario： kubevela/kubevela#1365

[Feature] Add badges into README along with code coverage configuration (codecov.yml) into the repo

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

[Feature] Support more unit tests to make the test coverage to 60%