3 жыл бұрын
3 жыл бұрын
Пікірлер
@tomasferrari92 13 күн бұрын
hi viktor! thanks for the great content! question, what do you think is the best approach for using configmaps when defining applications with crossplane? do you have any examples? thanks!
@senecathestoic 4 ай бұрын
So far it's not clear how do you debug all of that? I am not very familiar with both tools, but it looks like layers upon layers of eventually consistent components which will be quite hard to reason about
@user-ow3lw8nh9m 4 ай бұрын
hey Viktor, where can I find the repo that contain all the code to deploy grafana/loki? I am looking something that I can change images and all the policy. I don't know if I can have something with all integration (prometheuse, grafana, promtail...)
@AndreiDinTheHouse 7 ай бұрын
Quick question: if you use yaml do you also use some kind of templating? My main use cases end up creating some yaml that get applied to a lot of apps with some tweaks.
@MarkusEicher70 7 ай бұрын
Thanks for this interesting viewpoint. I now want to see, how Crossplane might fit into my plans. Looking forward to keep track of your postings.
@countbrapcula-espana 7 ай бұрын
Buenas tardes Victor. In theory, on the local K3D cluster (bootstrap cluster) you also could have used the option to add config to Crossplane to apply a ProviderConfig for Helm (after installing the helm provider plugin for Crossplane) and a Release config that pointed to the Crossplane helm chart repository vs entering the helm install commands at the terminal, right?
@sandeshprasai5142 8 ай бұрын
I have question here, do you have resources that explains how to import existing cluster (EKS) in cross plane and get control of this cluster
@autohmae 6 ай бұрын
cross plane documentation: knowledge-base/guides/import-existing-resources
@alihussainia 9 ай бұрын
Tbh it isn't the real question for most of the folks whether which tech can get the job done. The MOST IMP of all is which one can get them a job to start with and then explore and learn things along the way.
@franssjostrom719 9 ай бұрын
Is there any update in this topic?
@amjads8971 10 ай бұрын
I have heard so much on crossplane but yet to see companies using it in production.. please provide some real time scenarios
@ycchiranjeevi 10 ай бұрын
Nice Intro to Crossplane, for the Business Leaders especially!
@GuruprasadBhavsar 10 ай бұрын
Great video. Thanks for efforts. I have a question on this, how to package controllerconfig required for provider? In my case, I want to pass debug arg to controller pod also, want 2 replicas and leader-election arg added, also need to pass service account name to be used. is there any way to package that as well? how could you address this? TIA
@UtkarshMishra-it4oc 10 ай бұрын
What if I have to deploy helm charts that are not available in any public git repo but available with me as files, how can I do this with this kind of setup. Does the Helm provider have anything for local charts ?
@UtkarshMishra-it4oc 10 ай бұрын
How to access the UI of the ArgoCD server deployed on EKS cluster ? I have tried port forwarding but can't get the password right. The password I am trying is the one I found in composition.yaml in patches section and username is admin.
@UtkarshMishra-it4oc 10 ай бұрын
How to access the UI of the ArgoCD server deployed on EKS cluster ? I have tried port forwarding but can't get the password right. The password I am trying is the one I found in composition.yaml in patches section and username is admin.
@nanonkay5669 10 ай бұрын
It's Pulumi because she BL-EW me 😵😫😩
@user-dj1vh9du2z 11 ай бұрын
Is there any approach to parameterized modules like helm Values.yaml file .on cross plane module.pkg
@alissonreinaldosilva1119 Жыл бұрын
Awesome content. I love the idea of using crossplane to provision cloud infrastructure. What do you think about using crossplane to install only ArgoCD in the eks cluster, and letting ArgoCD deploy things like istio, prometheus, grafana as ArgoCD Applications? I find ArgoCD slightly less verbose for installing manifests 😅
@marimuthum9434 Жыл бұрын
Thanks for the amazing video. Could you provide an example of how to match resources in crossplane composition. Use case: reject AWS resource creation ( from composition ) if they don't have proper tags.
@coffeezealot8535 Жыл бұрын
Great video!
@csabadobo Жыл бұрын
Hi Victor, I have just started with Crossplane and struggling to put together a very basic composition - claim demo, ie a VPC + subnet group with the official upbound provider. Do you perhaps have something like that?
@prinson001 Жыл бұрын
helm tpl files are way better than ytt
@IvanRizzante Жыл бұрын
Thanks for another great video! I have a question here: what happens when you delete the GitOpsClaim? As far as I can see there is nothing to prevent Crossplane to delete ArgoCD Pods before ArgoCD Application or AppProject.
@debkr Жыл бұрын
Hello Victor. How can I deploy a self/crossplane managed kubernetes cluster on AWS. I am looking to provision self-managed k8s cluster and not EKS. On your other video on Cluster API, we had some discussion. As you suggested, after going through the entire documentation and so far, I am liking the core concept of Crossplane.
@annusingh4694 Жыл бұрын
Very informative, thanks.
@fpvclub7256 Жыл бұрын
So many questions for the new upbound.. 1 - How do you ensure my CSPs are secure if upbound was compromised? 2 - When do you expect Azure support? 3 - Are the resource yamls being ingested by upbound the same ( cross compatible ) with my yaml running crossplane locally? or do I need to make a bunch of changes to migrate? 4 - you mentioned in the vid the CRD limitations don't apply, why is that the case?
@rodoherty1 Жыл бұрын
Very useful video, Victor - thanks, as always!
@nikhilrajan2370 Жыл бұрын
How is this different from using a helm chart..all that the dev team needs to change is change the values file
@viniciusfs Жыл бұрын
Amazing sir! Thank you so much. It's exactly what kind of demo I needed to deep dive into Crossplane. I'm pretty sure that is the tool to solve a lot of problems I'm facing in my daily work.
@pm71241 Жыл бұрын
Not Helm ... Tanka.
@ramonsong6707 Жыл бұрын
Victor is just too good to be free :D
@holgerwinkelmann6219 Жыл бұрын
why not putting external name into the Status?
@holgerwinkelmann6219 Жыл бұрын
hey, what about jet-rancher as payload cluster ,-)
@zoop2174 Жыл бұрын
Love ytt I use it to modify charts I get from upstream.
@villagefoodmysteries7906 Жыл бұрын
How to Download ytt ...i am unable to download the package..
@liciomatos9281 Жыл бұрын
Missing the links...
@Upbound Жыл бұрын
Good catch. Fixed!
@utube3805 Жыл бұрын
You should have more subscribers your videos are great
@ViktorFarcic Жыл бұрын
I only recently started posting to this channel, and do not do that often due to my other tasks. I hope to be able to dedicate more time to this channel and grow it faster.
@sebastianwth5838 Жыл бұрын
Does the provider-jet-aws ultimately replace the provider-aws git project? Des the provider-aws deperecate in the future?
@Upbound Жыл бұрын
There are no plans to deprecate either of the two providers.
@nulops 2 жыл бұрын
What happens if I destroy the cluster on my local cluster before I destroy the cluster on the cloud. Could I destroy it if I recreate a local cluster
@Upbound 2 жыл бұрын
If you destroy the cluster forcefully (without first deleting the resources), the infra will stay. If, later on, you create a new cluster and apply the same resources, crossplane will take over the command of the existing infra, as long as external names are defined.
@terionname 2 жыл бұрын
can't find configs from video in your repos :(
@Upbound 2 жыл бұрын
Is gist.github.com/vfarcic/57689b4095d9c7825baef3c2aec201ea#file-133-crossplane-apps-sh-L17 what you're looking for?
@terionname 2 жыл бұрын
@@Upbound yamls with crossplain definitions for apps
@Upbound 2 жыл бұрын
@@terionname All the packages used in that and other demos done by me (Viktor) are in github.com/vfarcic/devops-toolkit-crossplane/tree/master/packages. The one with the apps package is in the `app` directory.
@farsheed2009 2 жыл бұрын
Tnx for the presentation! How is it possible to add e.g. Prometheus to the crossplane composition?
@Upbound 2 жыл бұрын
Something like github.com/vfarcic/devops-toolkit-crossplane/blob/master/packages/monitoring/prom-loki.yaml?
@bmutziu 2 жыл бұрын
I believe this session deserves much more than this exquisite amount of silence ... Thanks Viktor !
@IIGrudge 2 жыл бұрын
Advantage to doing this instead of packaging and consuming as Helm charts?
@Upbound 2 жыл бұрын
Helm charts are just a way to define templates that will be processed on client side. Crossplane Compositions are a way to create new CRDs with new APIs that can be managed as any other API (e.g., Kubernetes Deployment) and with their own lifecycle. It is, among other things, a way to create your own Kubernetes operators.
@RammsteinGuevara 2 жыл бұрын
Great video. I have a question about claims and how we can "instruct" them to use a specific version of the package. Say for example we have package k8s and it is installed (for example version 0.0.1). And we apply a aws-eks.yaml claim, then we update the k8s package (change something in the composition, some parameters) and install it, so now we have version 0.0.2 (And this is the active version). How we can "update" our claim to use the new version 0.0.2?
@Upbound 2 жыл бұрын
The answer depends on the API versions used in Compositions. Byh default, if Composition versions stay the same, all resources using those compositions will be updated. On the other hand, if you do change the version, everything will stay the same until resources using those compositions update versions as well. It's the same model followed by Kubernetes itself. Now, the important thing to note is that Composition versions are not the same as package versions.
@RammsteinGuevara 2 жыл бұрын
@@Upbound Thanks a lot for the answer.
@HowToCureDepression 2 жыл бұрын
This is it!
@farzadmf 2 жыл бұрын
Although I always LOVE your videos and I agree with a lot of things, I can't say I agree with this one for a few reasons: 1. Bringing tools such as Pulumi and Terraform (and Ansible) into this mix, IMO, is a bit misleading; those tools can manage EVERYTHING not just a k8s cluster, so their abstractions are way more generic 2. I haven't used Crossplane, but I'm a bit familiar with it (thanks to your amazing videos), and I love its concept, but unfortunately, I somehow see this video as a sales pitch for Crossplane rather than a fair and unbiosed comparison between different tools 3. Even if we move "complexity" to the server side, someone has to take care of that complexity, and if we want to do that, I personally can argue that we can move the same complexity to Terraform modules or Pulumi classes/objects
@Upbound 2 жыл бұрын
Viktor speaking... 1. I am not saying not to use terraform/Pulumi/etc but to use them to create server-side definitions and convert the complexity into CRDs. Also, crossplane is not only for managing k8s. It is for managing anything. 2. I do my best not to be biased. I did think that crossplane is a better choice before I joined upbound. As a matter of choice, I that is the reasons I joined. So, I was biased before I had any commercial interest to be biased. 3. Complexity cannot disappear. The point I'm trying to make is that experts in some field should work on it and create services that others can consume. Heroku is a good example. It is complex, but not for end users. I believe that we should be doing something similar when creating internal services.. P.S. Since I joined upbound, I intentionally publish all crossplane videos on this channel instead of DevOps Toolkit. I hope that helps avoid confusion about my potential bias.
@farzadmf 2 жыл бұрын
Very well put Viktor. As I said, I love your videos and I watch every single one of them, but I agree, and the the points you made are complete valid
@subhadipbanerjee6791 2 жыл бұрын
It's really excellent approach to infra automation solution. I personally love crossplan composition. This encapsulation helps non infra/SRE/devops guys work with simple yamls.
@kevinfernandes4097 2 жыл бұрын
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 2 жыл бұрын
Adding it to the TODO list... :)
@haimari871 2 жыл бұрын
Great Video, instead of waiting for flux you can run "flux reconcile kustomization whatever --with-source"
@Upbound 2 жыл бұрын
True
@arns9006 2 жыл бұрын
Will crossplane work with Karpenter or they will conflict ?
@Upbound 2 жыл бұрын
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 2 жыл бұрын
@@Upbound The nodes created via karpenter autoscaling won't be remove by crossplane ?
@Upbound 2 жыл бұрын
By default, karpenter does not affect the existing node pool but creates its own nodes.