Do you use GitOps to manage anything but apps running in Kubernetes clusters? If so, what is the most "exoctic" thing you manage with GitOps?
@vangelkrstevski566
Жыл бұрын
Mongo Atlas resources. They offer a Controller and we started managing the projects, users and clusters through Custom Resources. Very nice.
@micharudz5759
Жыл бұрын
Once I wrote an operator to manage the config of the SFTP server. I Managed users, ssh keys, folders, endpoint etc.. from Git repo, argoCD fetched the changes and my operator did the work.
@DevOpsToolkit
Жыл бұрын
@@micharudz5759 That's the way to go.
@SIMULATAN
6 ай бұрын
I consider writing an LDAP server that works using CRDs. Not too sure if this is even remotely possibly as I'm lacking the experience to know what LDAP really can do other than the basics, but I think this would be a nice light-weight alternative without databases or something for selfhosting setups. Most importantly though, the HA part is handled by k8s and etcd in the background so you don't have to bother with that.
@kevin22214
Жыл бұрын
Thanks for the video. We usually say "devportal" instead of IDP to avoid confusion
@2stoon
Жыл бұрын
Awesome content! Might follow in your footsteps and try this out for myself :)
@user-dw3vk6ji1i
Жыл бұрын
9:27 I'm excited about the fact that you're prepping a project that expands the previous IDP one, awesome content!
@davidcourtey1243
Жыл бұрын
Clear and use full ❤ Love to contribute to the idea of this video with my comment on the other one Keep up your hard work; I can say that we all really appreciate 😊
@mateuszszczecinski8241
Жыл бұрын
IDS - Internal developer services
@dandogamer
Жыл бұрын
Thanks for showing us this. I would love to see some policies being added to the dev portal. Guardrails are a must :)
@YonatanBoguslavski
Жыл бұрын
Which types of policies you would like to see added?
@DevOpsToolkit
Жыл бұрын
Great suggestion. Adding it to my to-do list...
@fasma
Жыл бұрын
ITP - Internal Tenant Platform ?! Where a tenant is some project or group inside your organisation that will use you internally created platform :-)
@fenarRH
Жыл бұрын
There shall be a way to classify app type before kicking the tire for repo creation, which may affect your container base image selection for example to start with.
@DevOpsToolkit
Жыл бұрын
That would be the purpose of helm templates.
@junpark8146
Жыл бұрын
Lovely as always! 🎉
@whitehatcomua
Жыл бұрын
Thank you for an interesting idea! I use TF cloud + github provider + gh repo to manage GH (repos, groups etc etc). The only part missing in your video - as I understand, in order to run crossplane, you need a fully working k8s cluster.. but how would you spin up a k8s cluster if you can't even create a GH repo for IaC for it?
@DevOpsToolkit
Жыл бұрын
You would need to create a management kubernetes cluster (the one with crossplane) manually but you can instruct it to manage itself later on. For example, you can run crossplane locally with, let's say, minikube, use it to create a "real" cluster, move crossplane there and, from there on, it'll manage itself.
@IvanRizzante
Жыл бұрын
@DevOpsToolkit Hi Victor and thanks for another great video! What about keeping the source code in a separated git repo from the k8s manifests?
@DevOpsToolkit
Жыл бұрын
Personally, i prefer keeping manifest in the app repo since that enables people working on the source code to run their apps without looking elsewhere for manifests. It's the same reason why I keep tests, build scripts, pipelines in app repos as well. What i do do is keep argo CD or flux manifests in a separate repo and referencing manifests in app repos. All that being said, many do keep manifests completely separate from source code so I might be minority.
@stanrock8015
Жыл бұрын
IDP vs IdP that’s the distinguishing. When spoken it’s about context. It is what it ia
@user-dw3vk6ji1i
Жыл бұрын
@DevOpsToolkit is there a video that you did about deploying Crossplane in production which covers the recommendations, ex: HA, breakglass protocolos if the controlplane cluster goes down...
@DevOpsToolkit
Жыл бұрын
Not yet... Adding it to my to-do list...
@andrewnhien9714
Жыл бұрын
In your example, if I want to generate some template file if using like you, the file always overrides if the dev or someone pushes their code, because the crossplane keep reconciling, any idea of 1 time to generate those file and be done? But still, using helm for the template? or any idea for a template file but still want use crossplane because just make a simple yaml and I have a whole repo(file, permission...). Sorry if I didn't explain clearly.
@DevOpsToolkit
Жыл бұрын
Crossplane compositions are all about creating CRDs and controllers so the arguments in favor of using Crossplane Compositions are similar to those in favor of creating CRDs and controllers. It would take me a while to explain why we should move stuff into clusters and create CRDs and controllers and I got that question quite a few times so I decided to make a video on that topic. If everything goes as planned, it should go live on August 28. Until then, the Gist of it is that a) we should be creating CRDs to define what is something and b) that CRDs does not replace tools like Helm but might reduce the dependency on it and, maybe, move people towards simpler solutions like Kustomize. It's coming...
@DevOpsToolkit
Жыл бұрын
Now that I went through your comment one more time i realized that i might have missubderstood it. If you're using crossplane compositions, it's similar to using Deployments. You cannot modify replica sets created by deployments since the changes will be overwritten by reconciliation loops of the deployment. Similarly, if you create crossplane claims, which create composite resource, all child resources are controlled by that composite resource. If you'd like to change those child resources, you would need to either modify the claim or, if you'd like to change the behaviour of the compisite resource you'd need to change the composition itself. All that is following the logic of kubernetes itself. You never modify child resources directly. They are owned by parents.
@nebroTtfeoH
Жыл бұрын
I thought that DeveloperExperiencePlatform (DevEx) and IDP are the same thing!? Tell me if I’m wrong!
@DevOpsToolkit
Жыл бұрын
It's probably the same or completely different depending on who you ask.
@TweakMDS
Жыл бұрын
We were struggling with the same terminology mix-up between IdP and IDP, and I started calling it IDevP (eye-dev-pee).
@DevOpsToolkit
Жыл бұрын
I like that.
@Milanbb1
Жыл бұрын
Why not create a Kubernetes operator for this? As I researched, there is no operator for GitHub.
@DevOpsToolkit
Жыл бұрын
Crossplane providers act as operators 🙂
@seanogorman6940
Жыл бұрын
You could just call it a devx platform, but its is really more than that... overloaded terms and ambiguity are the normal diet of engineers 😅
@sebiuo5817
Жыл бұрын
gosu
@julianomoraisbarbosa
Жыл бұрын
#til
@AndreaGhensi
Жыл бұрын
I'm currently using cookiecutter (we mainly develop python tools) and I'm considering a switch to copier, mainly to gain the ability to update the templates in already created repos. I'm really interested in your approach to move as much I can to gitops! Does an update of the argocd application overwrite the RepositoryFiles?
@DevOpsToolkit
Жыл бұрын
A change in a k8s GitHub file definition will result in a change to the file in GitHub.
Пікірлер: 38