[Feature] Integration with developing time

[resouer]

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

Developing micro services is also challenging.

Describe the solution you'd like

Have a integration with Tilt: https://github.com/tilt-dev/tilt

Describe alternatives you've considered

Additional context

[wonderflow]

Yes, the idea is interesting, we can easily contribute vela as a tilt-extension. But it's hard to show what's the value of kubevela if users are already using tilt.

vela and tilt are very similar in deveper interface. If user uses tiltfile, they won't want to learn appfile. If we give up appfile and directly use tiltfile, It's hard to show using vela is better than using K8s. The complexity of K8s can be easily hidden by tilt-extension.

[wonderflow]

Let's hold until we have more Capability such as rolling update with traffic management.

[wonderflow]

Nocalhost is also an option to integrate, it's a developing tool similar with tilt.

refer to : https://nocalhost.dev/blog/api-six

Add a nocalhost trait to debug app in developing time.

[wonderflow]

Let's re-visit this issue, I think it's a good time to integrate tilt with KubeVela now.

Developing tools such as Tilt and Nocalhost can help users using KubeVela easily by integrate with IDE doing local development. By using KubeVela, users can have a consistent experience from local development, testing to production deploy. The same KubeVela application yaml with components/traits/workflow specified can work in all these environments.

So what's benifit for users who are already using tilt to manage K8s resources?

1. KubeVela can help launch an environment very easily. The environment includes a new K8s cluster, cloud resources or anything that need to be prepared previously.
2. KubeVela has a very good workflow mechanism, it can help developers to manage dependencies, especially for micro services. The developer may need to setup a lot of microservices that was maintained by other teams. With the help of KubeVela, these dependency and resources lifecycle can be managed easily with only one KubeVela application yaml.
3. One KubeVela application can orchestrate and manage as many K8s resources as you need, you can bundle them as a whole in one application yaml.
4. KubeVela has lots of operational management capabilities, such sa rollout, traffic management, etc.. These capabilities can help developers to test the real production deployment.

[lakshya8066]

Hey @wonderflow, this seems pretty interesting! I would like to work on it. Could you guide me where to start from?

[wonderflow]

For anyone whoe want to try this issue, I suggest these steps to get started:

1. Get familiar with what KubeVela and tilt is. Read docs of both projects.
2. Deploy KubeVela by using kind or minikube, run application.
3. Try write a tilt plugin to integrate with KubeVela.

The final goal is users using tilt developing with a KubeVela application yaml locally and any change could deployed in the K8s cluster and preview.

[jj551]

@wonderflow I would like apply for this project under the LFX . I have read the previous comments and the requirements you mentioned. Looking forward to it.

[wonderflow]

@lakshya8066 @MarcaWitt Thanks for your interest, you could write a proposal for your plan on this issue.

[lakshya8066]

Thank you @wonderflow. I am working on that.

[kaustubhsharma-009]

The issue looks pretty interesting. I have a few ideas regarding the same based on whatever I have worked on or have some experience about. I'd like to apply for this project under LFX if possible. Hope I get the opportunity
Thanks!!

[wonderflow]

@kaustubhsharma-009 Sure, you're welcome and please send your proposal here.

[kaustubhsharma-009]

I had submitted my proposal along with a cover letter on the LFX mentorship application @wonderflow
Thanks!

[wonderflow]

ref #2577 #2545