Kelsey was able to convey a point that wasn't to said well by CP itself. Wont blame them cause he's a monument of it own.

It was helpfull , Great Work 👍

42:20 KubeZero - GH: DevOpsHiveHQ/kubezero

I have no idea why this video has no comment. Thank you though.

Echo

How about more videos on Crossplane tutorials from basic to advanced level???

How do we access the community meeting agendas and next updates in the pipeline ?

It was helpful in building my understanding, I need to go further but it provides some clarity!

It was quite informative in a structured way. Thanks!

@vfarcic Is this solution open source ?

difficult to read the document in this video

Hi, basically ArgoCD support this kind of templating of Appliactions as well. Can you elaborate on the difference between Crossplane or ArgoCD "Compositions

Can you link the Google Docs with the Community meeting notes in the Video Description ?

100%. Devs ALWAYS mess up their Kubernetes config. They dont have the experience or need to learn the metal.

Victor/Hasn, while you showing the actual PODs of the hosted cluster, I did notice it is not etcd ? So are you using the etcd from the base k8s cluster? Asking because at the start of the slide was mentioned etcd is included component.

starts at 06:35

I KNEW IT. I literally searched "should a developer learn kubernetes" and was not surprised.

Excellent! Your presentation brought clarity into my understanding.

Kelsey as usual you just helped me solve a problem I’ve been trying to understand/rectify/solve (and like a year ago, oy). For those of us who like writing modules in HCL and enjoy the verifiability and policy enforcement BEFORE code even hits the infra, this is exactly what I’ve been trying to achieve. Currently I have no idea how policy enforcement would work in a cross plane only environment - there’s gotta be some phase before any code reaches the cloud provider apis to really enforce anything. Building module definitions in HCL for CRDs can be incredibly useful for scoping declarative, modular, permission scoped workflows. Props to the Hashicorp team for working on this. Props to the cross plane team for recognizing and leveraging the control plane loops available in k8s for this type of infrastructure management. Now my question is: how do we develop patterns for logging and alerting on success/fail/unexpected change/cross plane-initiated change back? Meaning, if I have a user changing infra through some unexpected means (say, the web console) and cross plane wants to change it back, how does one alert and control the change back process in the hopes of a sounding data loss? Would that be done with more customized CRDs in cross plane? I imagine we would we enforce policy through code in something like Hashicorp Sentinel before those changes even hit the K8s control plane? Or, I suppose we just cut off change access to devs and let the robots manage the change that devs describe in code, and that’s the answer… Still doesn’t solve the problem of notifying people things are about to change because robots found a diff in our infrastructure from what Crossplane thinks it’s supposed to be.

Great talk!

Great content! Thank you both for that! I followed the steps from the video and make the same example works but I note that the Terraform Version used by Crossplane Experimental Terraform Provider is 1.0.1 (checking the contents of Terraform State) even when I set the "required_version = ">= 1.0.5, < 2.0.0" block on Terraform Code. I have an use case that we'll need to support multiple Terraform versions for some time and, because of that, we're packaging the Terraform Code + Terraform Binary + Modules into a Container Image and running it using Pipelines while we work on the update in smaller pieces. I'd like to know if is there a way to accomplish that using Crossplane? I see that a Workspace Kind is used to reference a Terraform Module or Inline Terraform Code but, if it could be possible to tell to Crossplane to only execute our customized Container Images with some Environment Variables and get the Terraform Outputs from there (it could be as text plain or json format). Maybe we need to create a Provider for that? I'll be grateful if you could give any thoughts about it.

The points about managing configuration as data, how the API has “shifted” to variables and moving away from templates is really salient and the basis for the success and simplicity of Kustomize, which I’m finding I really love. Formerly, I was using a fairly powerful but somewhat esoteric templating language called “ytt”. However, I’m finding Kustomize to be suitable for my needs and realized I was dramatically over complicating things, at least for my particular use case. The concept of overlays was just right and also made it _so much easier_ to *reason* about what the code was doing and required much less cognitive overhead to interpret when compared to the extra logic/abstraction caused by using templates and variables.

Video gets stuck here and there often .

can I create a VM on GCP(cant find any api in docs to do that)

promise of a magic was good! Thanks! :-) Otherwise it was too high level and too fast to follow for a casual devops

Good starting video. Please add such more videos.

Thanks! That's a great conceptional positioning of crossplane and terraform in the context of k8s.

well donw, ttey to adapt tthis to a Networking model

kzbin.info/www/bejne/q4rQn42tqMuVoqs (Cryptojacking exploit i mentioned): sysdig.com/blog/detecting-cryptojacking/

By the way, what's the song in the beginning?