Cloud-Native Apps With Open Application Model (OAM) And KubeVela

Can we define cloud-native applications without dealing with resources related to underlying platforms? One possible solution is to use the Open Application Model (OAM) combined with KubeVela.

#oam #kubevela #k8s #kubernetes #cloud-native

▬▬▬▬▬▬ Timecodes ⏱ ▬▬▬▬▬▬
00:00 What is Open Application Model (OAM) and Kubevela?
04:27 Setup
05:10 Defining OAM applications
10:28 Defining custom OAM components
16:54 Defining custom OAM traits
18:43 Deploying a custom OAM applications
24:13 Should we use Open Application Model (OAM) and Kubevela?

▬▬▬▬▬▬ 🔗 Additional Info 🔗 ▬▬▬▬▬▬

▬▬▬▬▬▬ 🚀 Courses, books, and podcasts 🚀 ▬▬▬▬▬▬

▬▬▬▬▬▬ 👋 Contact me 👋 ▬▬▬▬▬▬

[DevOpsToolkit]

What are you thinking? Does it make sense to define applications as applications instead of Kubernetes resources?

[TimberDeng]

Hi. KubeVela & OAM committer here. I have been subscribing to your channel for a long time. Loved the materials and learned a lot of stuff. It's fantastic to see something that I build show up in your channel here! I just want to say thanks for making this video and feel wonderful open source life is.

[arturmaciag]

Great video. I'm interested to see video about existing platforms you mentioned in the video.

[xarantaur]

Thank you for the video. Very insightful and informative 👍

[jacksonchristopher]

All meat and no filler! Awesome breakdown as usual. Wearing the hat on both sides was a great perspective.OAM might have earned the "VSA" (Viktor Seal of Approval)
currently watching your conversation with Kelsey Hightower right now. Would have been fun to be in the chat for that one. Stay well good sir, I look forward to the next one.

[happypathway]

I was watching this video thinking wow, this guy is doing a great job of explaining this... Then I saw that you're Victor Farcic, and was no longer amazed at how good of a job you were doing explaining.... sorry but I'm no longer amazed when I see great presentations and articles from you. I've seen too many and it's no longer surprising. lol.

[JeffMcLamb]

This is fantastic. I can easily see the power of Flux/Argo combined with KubeVela. But where do you see the split when incorporating Crossplane? It seems as though I could create a Crossplane XRD that abstracts away and does a lot of what KubeVela does at the app layer? I guess the proper separating line would be to have XRDs that provide developer-friendly infrastructure abstractions that will instantiate clusters and resources that can then be referenced by OAM/KubeVela ... All of course actuated via GitOps :)

[JurgoBoemo]

Thanks for the amazing video, I'm playing a little with kubevela in those days and this was pretty useful.
Do you think is possible to use it combined with DevSpace? Would it make sense?

[chriwas]

@DevOps Toolkit
Hi, thanks for the great video. Has you opinion about OAM and KubeVela changed since the release of the video? Has OAM progressed to become the „standard“ and did KubeVela improve on docs and scope?

[rajeshreddyn]

Victor, How do you differentiate the apps of app in Argocd, Crossplane compositions and Kubevela + Helm and Helm with multiple dependencies ? However Helm can be integrated with any of the tools.

[christianibiri]

Thanks Victor for this video, have you seen companies that use Kubevela in production environments?

[qnicks]

Templating yaml again.
But this looks promising, tbh. I'll give it a try.

[GuruprasadBhavsar]

Hi, Great video, kubevela seems to be a really great. Do you have any documentation link for schematic definition using kube? I only found the component definition doc using cue but no luck with kube. Any resource would you have, please share.

[TheEmc]

Great video as always Victor. I have a question regarding this, creating the crds for different products, what would I gain vs using my own custom helm chart where the dev commits the value.yaml vs the oam kind yaml. I might be missing the bigger picture (first time seeing oam)

[mehdimosbah]

First thank you for the video, but I want to ask in frontend definition when creating the component you have fixed the port with the value 80. Does that mean 80 would be the default value and we can changed it or is it already fixed when defining the application?

[yojano]

Fighting game stuff in the background?

[deathknight]

Thanks so much for the video. However, I do not really see difference between writing a componentdefinition and writing a helm chart and re use it!

[shinebayar]

CUE looks much better than go templating lang ...

[underlecht]

Amazing stuff and looks very powerful. I really do not like many yaml, manifests, and this is a way to simplify and to focus on application. Other thing that I see on projects that expands the application config is extensive environment setting. Meaning variables from configmaps and secrets, many apps use many of those, as they are shared in between. I see that app declaration can be very nicely simplified with OAM, but env config can still make it big. I know it is somehow unrelated, but wonder if there is a way to simplify the env settings as well as they really explode the manifests. (including full configmaps and full secrets to env should not be desired - app should only "see" its dedicated variables)