wyikeandGitHub b33b6fbead garbage collection for cross-namespace workloads and traits in application layer (#1421)
* add logic for gc cross ns resources

WIP regenerate api and charts

rewrite handle resourceTracker logic

WIP add e2e test logic

add more e2e  test

* WIP refactor sevral funs name and add comments for code

* WIP add more corener case e2e test

* add unit test and fix bug

* WIP refactor handleResouceTracker  logic

* refactor func name aglin with others and add comments

* make generate to fix check-diff ci error

* change resourceTracker status as a subresource
2021-04-07 21:34:48 +08:00
2021-03-26 15:24:19 +08:00
2021-03-24 17:15:20 -07:00
2021-03-26 15:24:19 +08:00
2021-03-30 16:37:46 +08:00
2020-10-10 17:35:16 +08:00
2021-03-30 16:37:46 +08:00
2021-03-28 18:18:47 -07:00
2021-03-28 18:18:47 -07:00
2020-12-23 21:51:31 -08:00
2021-01-29 18:42:03 +09:00

Build status Go Report Card Docker Pulls codecov LICENSE Releases TODOs Twitter Artifact HUB

alt

Make shipping applications more enjoyable.

KubeVela

KubeVela is a modern application engine that exposes higher level API for self-service experience.

Community

What problems does it solve?

Managing microservices on hybrid infrastructure with constantly changing user requirements is painful. This in turn makes continuous delivery at scale a nearly impossible task.

Hence, as the platform team, we build abstractions to manage such complexity and enforce best practices in the deployment workflow.

However, great in flexibility and extensibility, existing solutions such as IaC (Infrastructure-as-Code) and client-side templating tools all lead to Configuration Drift (i.e. the generated instances are not in line with the expected configuration) which is a nightmare in production.

KubeVela solves this by allowing platform teams to manage complexities with IaC, expose abstractions as self-service capabilities, and enforce the consistent standard with Kubernetes Control Loop. Rollout model and strategies are also built-in so deployment confidence in hybrid environments is guaranteed.

Think about a Heroku fully designed by yourself.

Getting Started

Features

  • Robust, repeatable and extensible approach to manage abstractions - design and enforce best practices with CUE or Helm templates, ship them to end users with kubectl, automatically generating GUI forms for capabilities, and let Kubernetes controller guarantee determinism of the abstractions, no configuration drift.
  • Generic progressive rollout framework - built-in rollout framework and strategies to upgrade your microservice regardless of its workload type (e.g. stateless, stateful, or even custom operators etc), seamless integration with observability systems.
  • Multi-cluster multi-revision application deployment - built-in model to deploy or rollout your apps across multiple enviroments and/or clusters, seamless integrated with Service Mesh for traffic shifting.
  • Simple and Kubernetes native - KubeVela is just a simple custom controller, all its abstractions and features are defined as Kubernetes Custom Resources so they naturally work with any CI/CD or GitOps tools.

Documentation

Visit the KubeVela documentation site to find Installation Instruction, Platform Builder Guide and Developer Experience Guide.

Talks and Conferences

Engagement Link
🎤 Talks - KubeVela - The Modern App Delivery System in Alibaba
🌎 KubeCon - [NA 2020] Standardizing Cloud Native Application Delivery Across Different Clouds
- [EU 2021] Zero Pain Microservice Development and Deployment with Dapr and KubeVela
📺 Conferences - Dapr, Rudr, OAM: Mark Russinovich presents next gen app development & deployment
- Mark Russinovich presents "The Future of Cloud Native Applications with OAM and Dapr"

Contributing

Check out CONTRIBUTING to see how to develop with KubeVela.

Code of Conduct

KubeVela adopts CNCF Code of Conduct.

Languages
Go 95.4%
CUE 3.4%
Mustache 0.4%
Shell 0.4%
Makefile 0.3%