wyikeandGitHub
4540270813
[WIP]create tracker if needed and update components [WIP] add finalizer code and add logic for ac controller [WIP] refactor handle func to app handler [WIP] support helm cross namespace [WIP] rewrite application controller logic rebase master and solve conflict WIP add base cross namespace workload and fix some bugs add more e2e-test and fix some bugs rebase master and resolve confilict move resourceTracker to v1beta1 add v1beta1 to test scheme to fix test modify e2e test, change v1alpha2 application to v1beta1 delete resourceTracker crossplane catagory add controller logic test add unittest for finalizer related func add more unit test neet order import walk around check-diff error add docs add some comments in AC controller as review said modify some issues
Make shipping applications more enjoyable.
KubeVela
KubeVela is the platform engine to create PaaS-like experience on Kubernetes, in a scalable approach.
Community
- Slack: CNCF Slack #kubevela channel
- Gitter: Discussion
- Bi-weekly Community Call: Meeting Notes
NOTE: KubeVela is still iterating quickly. It's currently under pre-beta release.
What problems does it solve?
Building developer-centric platforms with Kubernetes requires higher level primitives which is out-of-scope of Kubernetes itself. Hence, we platform teams build abstractions.
However, great in flexibility and extensibility, the 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 allows platform teams to create developer-centric abstractions with IaC but maintain them with the battle tested Kubernetes Control Loop. Think about a plug-in that turns your Kubernetes cluster into a "PaaS" via abstractions designed by yourself.
Getting Started
Features
- Robust, repeatable and extensible approach to create and maintain abstractions - design your abstractions with CUE or Helm, ship them to end users by
kubectl apply -f, automatically generating GUI forms, upgrade your abstractions at runtime, 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-enviroment app delievry model (WIP) - built-in model to deliver or rollout your apps across multiple enviroments and/or clusters, seamless integration with Service Mesh for traffic management.
- Simple and Kubernetes native - KubeVela is just a simple custom controller, all its app delivery 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
Contributing
Check out CONTRIBUTING to see how to develop with KubeVela.
Code of Conduct
KubeVela adopts CNCF Code of Conduct.