How To Apply GitOps To Everything Using Crossplane And Flux

How can we leverage the extensibility of Crossplane and Flux features to apply GitOps not only to applications running in Kubernetes but to everything (infrastructure, services, applications running anywhere, etc.)?
▬▬▬▬▬▬ 🔗 Additional Info 🔗 ▬▬▬▬▬▬
➡ Gist with the commands: gist.github.com/0c56f8b8a8201...
🎬 eksctl - How to Create and Manage AWS EKS clusters: • eksctl - How to Create...
🎬 Flux CD v2 With GitOps Toolkit - Kubernetes Deployment And Sync Mechanism: • Flux CD v2 With GitOps...
🎬 How To Shift Left Infrastructure Management Using Crossplane Compositions: • How To Shift Left Infr...
🎬 How To Manage Applications With Databases Using Helm, Crossplane, And Schemahero: • How To Manage Applicat...

[@kevinfernandes4097]

Nice practical video. I would be interested in video with examples with a sample app on managing multiple K8s clusters with a single Flux/ArgoCD instance.

[@Upbound]

Adding it to the TODO list... :)

[@haimari871]

Great Video, instead of waiting for flux you can run "flux reconcile kustomization whatever --with-source"

[@Upbound]

True

[@arns9006]

Will crossplane work with Karpenter or they will conflict ?

[@Upbound]

It would work without any problem. You'd probably create a Crossplane composition that contains all AWS resource (e.g., EKS, NodeGroup, Subnets, VPCs, etc.) plus a Kubernetes or Helm resource for Karpenter. That is, in case you'd like to have it all together.

[@arns9006]

@@Upbound The nodes created via karpenter autoscaling won't be remove by crossplane ?

[@Upbound]

By default, karpenter does not affect the existing node pool but creates its own nodes.