Automate Everything: How One Manifest Powers Your Entire DevOps Pipeline

Рет қаралды 12,967

Күн бұрын

Пікірлер: 58

@DevOpsToolkit 4 ай бұрын

The link to the transcript and commands was broken. Appologies for that... Please use devopstoolkit.live/internal-developer-platforms/automate-everything-how-one-manifest-powers-your-entire-devops-pipeline.

@IndigoVFX 4 ай бұрын

May I suggest you pin your comment?

@DevOpsToolkit 4 ай бұрын

Good suggestion. Done.

@richardpierce-jones2896 4 ай бұрын

I would love to see a backstage demo. It is a much easier sell to my clients than a managed solution (like port).

@DevOpsToolkit 3 ай бұрын

Here's the first video about Backstage/Roadie: kzbin.info/www/bejne/gnrLn5yZgd6tqc0. It's not about Backstage directly but about Roadie. I already started working on Backstage-specific videos that will be in the form of tutorials.

@TiggyProph 4 ай бұрын

This is how my organization works with the only difference being an app-of-apps pattern with a managed shared helm chart as the interface. Otherwise, the overall pattern is identical. The self-service capabilities are incredible. It's so easy to slap an IDP in front of this to take it to that next level. I have no regrets. Seeing so much chatter about claims though has me wondering how much they could replace or augment our helm charts for future steps.

@edwardpius5367 4 ай бұрын

Thanks for this (as well as the other videos you post). It is really a pleasure watching your videos and I look forward to these to light up my week! Since you mentioned Developer Portals, I would like to know if you are going to be doing any videos on Backstage and this whole pipeline using Backstage as well. In appreciation,

@DevOpsToolkit 4 ай бұрын

This is already a third request to hook it to backstage so I'll certainly do it. I expect it to go live in a few weeks.

@kaokakelvin6202 4 ай бұрын

Hello Viktor, would like to see if the Port api schema auto-discovery has been improved.

@DevOpsToolkit 4 ай бұрын

I believe they are still working on it.

@emreo4656 3 ай бұрын

Backstage!

@DevOpsToolkit 3 ай бұрын

Here's the first video about Backstage/Roadie: kzbin.info/www/bejne/gnrLn5yZgd6tqc0. More will come...

@cedriclamalle 3 ай бұрын

Great video! Would like a tutorial about Backstage too!!

@DevOpsToolkit 3 ай бұрын

Here's the first video about Backstage/Roadie: kzbin.info/www/bejne/gnrLn5yZgd6tqc0. More will come and will be tutorials instead of comparisons like that one.

@cedriclamalle 3 ай бұрын

@@DevOpsToolkit Great! Thanks a lot!!

@renaud72 3 ай бұрын

Hello , thank you for the great video. One thing bothers me: the multiple git repos, and especialy app repo / gitops repo. 1 ) Dont you have indirection here ( the account pushing to one repo nit tge same as enduser)which is a security concern for access control ? 2) from my experience, git to git introduces synch issues ( for exampke in case of conflicts), adds complexity and prevents proper observability to the end user ( in your case gitops repo versus the enduser). How do you solve this ? Cheers

@DevOpsToolkit 3 ай бұрын

1) You can push it to the same repo but, in that case, you'd need to create Argo CD Application for each app instead of using something like an App of Apps model. You won't have a repo where the whole production is described but it can certainly be done. 2) I haven't experienced Git coflicts in those cases since each app is described in a different file and the operation is very fast. It's not impossible to get a conflict but very unlikely.

@phillipsma 3 ай бұрын

Any plans to review Kargo for multi-stage gitops deployments?

@DevOpsToolkit 3 ай бұрын

It's on my to-do list but not (yet) at the top. Probably in a few months...

@phillipsma 3 ай бұрын

@@DevOpsToolkit perfect. Love the format so will look forward to that.

@DevOpsToolkit Ай бұрын

Here it goes: kzbin.info/www/bejne/iKC8aISrapatrbc

@DerekMurawsky 3 ай бұрын

Videos like this are great! Do you have one on how to sanely bootstrap the whole thing? For example, the chicken and egg of how to get the initial k8s cluster up and running with a repo backing it?

@DevOpsToolkit 3 ай бұрын

You need to create that initial cluster and install crossplane somehow. That can be minikube or kind cluster running locally or a "real" cluster. From there on, everything should work automatically. You can even transfer crossplane and argo CD to a cluster crested by crossplane. Alternative is to use Upbound Spaces which is Crossplane as a service.

@IvanRizzante 4 ай бұрын

Thank you for another great video! Please check the link for transcription, it is broken. I really like this approach and it's pretty similar to the one I adopted myself for platform engineering in my company! And yes, I'd be intrested in seeing this in action in Port!

@DevOpsToolkit 4 ай бұрын

sorry for that. It should be fixed now.

@peterfodor3068 4 ай бұрын

Fantastic, thank you. Port please :)

@michaelfornaro729 4 ай бұрын

Excellent video as always - Was half expecting to see some cuelang somewhere potentially in your demo, do you plan to share the source code for your demo?

@DevOpsToolkit 4 ай бұрын

The app is written in Go. It's a simple one though. The Compositon is using KCL that is similar to CUE but, in my opinion, better. There is a link to the transcript and all the commands (including the reference to the repo) is in the description.

@socrateshlapolosa2020 4 ай бұрын

Hi i would be interested in seeing how to translate this to Backstage and portal, busy trying to decide between the two. Also, how would you disable kubectl commands directly to the server?

@MrEvgheniDev 4 ай бұрын

It is easy could be done with Backstage Templates which are fully compatible with the Open API schema used in XRD and CRD ;)

@DevOpsToolkit 4 ай бұрын

I'll start working on backstage right away. You don't need to disable kubectl but not too give kubernetes config to anyone.

@DevOpsToolkit 4 ай бұрын

But can backstage discover kubernetes API endpoints (CRDs) too avoid duplication?

@MrEvgheniDev 4 ай бұрын

@@DevOpsToolkit We are just using XRD, because CRD is overloaded with some service properties, but XRD are pure, and just platform related entities, and is allowed to add some custom keys directly to there, like "ui:options", auto discovered by Backstage ;)

@DevOpsToolkit 4 ай бұрын

@MrEvgheniDev that's great! Can you point backstage to kube API to discover XRDs or you load them as files?

@tomasferrari92 3 ай бұрын

Do backstage pleasee 🙌🙌🙌. Great video as always

@DevOpsToolkit 3 ай бұрын

I'm already on it. It should go live in two weeks.

@DevOpsToolkit 3 ай бұрын

Here's the first video about Backstage/Roadie: kzbin.info/www/bejne/gnrLn5yZgd6tqc0. More will come...

@HadalSayer 4 ай бұрын

Yes please do a portal video with Backstage.

@DevOpsToolkit 3 ай бұрын

Here's the first video about Backstage/Roadie: kzbin.info/www/bejne/gnrLn5yZgd6tqc0. More will come...

@andreferreira.86 4 ай бұрын

Simply amazing! Thank you so much for such focused explanation! Do you have a tutorial or course with all these topics?

@caseyphillips 4 ай бұрын

He has videos on most of these topics. I don't know if he has them in playlist but if you search his videos for ArgoCD, CrossPlane, etc he has detailed videos explaining them in great detail.

@DevOpsToolkit 4 ай бұрын

Links to some are in the description. There are many more in the channel.

@gustavomelo6560 2 ай бұрын

Amazing tutorial! I understand that for you it is very simple to just change the tools like ArgoCD for Flux or cloud AWS for Azure, but I would be in love if you could show us how to make the same thing with Azure Pipelines + Git + AKS One more time, thanks for this content.

@DevOpsToolkit 2 ай бұрын

I just added it to my to-do list but I cannot confirm when it's turn will come. I'm sorry for not being able to commit to a date just yet.