Internal Developer Platform (IDP) For Infrastructure

Sdílet
Vložit
  • čas přidán 25. 08. 2024

Komentáře • 33

  • @DevOpsToolkit
    @DevOpsToolkit  Před rokem +18

    Should I continue adding "stuff" to the IDP based on this and the previous video? What would you like to see next?

    • @kaokakelvin6202
      @kaokakelvin6202 Před rokem +2

      Beautiful staff here, I'm pretty new to this, but i would like to implement it in my work place. Could you do one for lower and higher environments, and maybe speak alittle about integrating existing resources like dbs, and also support for PRs.

    • @DevOpsToolkit
      @DevOpsToolkit  Před rokem +1

      @kaokakelvin6202 integration with DBs was explored in the previous IDP video (you'll find the link in the description of this one). PRs will probably be the subject of the next IDP video 🙂

    • @kaokakelvin6202
      @kaokakelvin6202 Před rokem +2

      @@DevOpsToolkit cant wait, thank you.

    • @chrisre2751
      @chrisre2751 Před rokem +1

      Thank you for the video. I like the stuff about IDP.
      I would like to see more about different environments and stages.
      Höre can I create infrastrukture for development stage an prod stage. And how can I stage the golden images with ArgoCD to the stages. @DevOpsToolkit

    • @chrisre2751
      @chrisre2751 Před rokem +1

      Hey Viktor, I asked myself the question if it is posible and a good idea to also use crossplane to execute sql scripts. Usualy me app interact with the database and modify data, but I also have base data which is needed. Is there a way to use crossplane to insert some base data SQL scripts in my data base? This would be fire and forget scripts. ArgoCD and Crossplane would help my to know which data inserted/modified.

  • @pavelpikat8950
    @pavelpikat8950 Před rokem +10

    That's exactly what my team and I are doing - Port, ArgoCD, Crossplan, except our provider is Azure, and we even formed dedicated, product-oriented Platform Engineering team for that. The future looks bright and we've build a lot of hype within the company, now we just need to.. implement it! :D

    • @nootajay
      @nootajay Před rokem +2

      I wrote this for my upcoming sprint planning, apart from civo have tried before. But I will go with vcluster approach rather than creating a cloud cluster. with vcluster I can provide prometheus+grafana+otel observability and that can be common in all of the virtual clusters. Cool right!

    • @DevOpsToolkit
      @DevOpsToolkit  Před rokem

      vCluster is a great option, especially if not resources are cluster-scoped and/or when using "expensive" managed Kubernetes (e.g., EKS, AKS, GKE). DigitalOcean, on the other hand, is very cheap and very fast to create so the need for vCluster is slightly smaller (still useful though).
      In any case, vCluster is awesome.

  • @andrewnhien9714
    @andrewnhien9714 Před rokem +2

    Very excited for what you have to say at the upcoming video. Thank you for your continuous work and sharing. Viktor

  • @socrateshlapolosa2020
    @socrateshlapolosa2020 Před 12 dny +1

    There is so much to be appreciated from this. Would be interested to see version that uses terraform for the control cluster (instead of scripts), would be interesting to explore a self hosted version of port (e.g. enterprise), to be automatically configured as part of the cluster creation vs copy and paste of json. So many ways this could go, but please DO CARRY ON, this is still very topical, just check out the google trends

  • @jpconstantineau
    @jpconstantineau Před rokem +13

    To Celebrate what we created - let's destroy it! 🎉 🤣

  • @user-dw3vk6ji1i
    @user-dw3vk6ji1i Před rokem +1

    Awesome content, keep them coming! Excited about the next one!
    I would like to see scenarios that tie things together, ex: crossplane compositions that create a full segment of a project, frontend tier, backend tier, data tier, and ties them together. We were able to do something similar using EKS Blueprints, yet this still requires the user to do a lot of Terraform wizardry.
    BTW whats it with Civo?

    • @DevOpsToolkit
      @DevOpsToolkit  Před rokem +1

      That's the ultimate goal; to add all components and the whole lifecycle.
      I used Civo in this video mostly because it'll become important in the next IDP episode. It'll become clearer when I release it. Until then, you should be able to replace Civo with whichever provider you might prefer. The Crossplane composition I used already supports AWS, GCP, and Azure aside from Civo.

    • @user-dw3vk6ji1i
      @user-dw3vk6ji1i Před rokem +1

      🙌

  • @claytoncastro2734
    @claytoncastro2734 Před rokem +1

    I love crossplane for these kinds of things, but haven't done a deep enough dive with it to see its full capabilities. Could it be used to create/manage self managed clusters? I'm not sure how it would handle resource dependencies in such a situation, how it would inject the necessary generated ip addresses into cloud-init commands, etc. Would another IAC tool be required to help it do such?

    • @DevOpsToolkit
      @DevOpsToolkit  Před rokem

      all the info you need gets stored into kubernetes secrets. Also, any resource can reference data from any other resources.

  • @TheGriffender
    @TheGriffender Před rokem +1

    Hi Viktor, since the goal is to create potentially many k8s clusters, have you consider using the cluster-api rather than a lot non-gitops stuff in github action ?

    • @DevOpsToolkit
      @DevOpsToolkit  Před rokem +2

      I'm using crossplane which is based on kubernetes resources hence it's gitops friendly. The main difference is that crossplane covers all types of resources and not only those related to kubernetes cluster and that it allows you to create your own abstractions (CRDs).

  • @rafasn03312
    @rafasn03312 Před rokem +1

    every service and vendor lock stuff will be ready for anyone interested to deploy something. Those services might help people and cut functions in the company until operation and average software will become easy to deploy, copy & paste. It turns out average joe will replace more expensive workers and companies will have more competitors than ever, with few monopolies taking over the whole market.

  • @dandogamer
    @dandogamer Před rokem +1

    Been looking at civo for a while to develop a platform ontop of and honestly looks great. Would love to see an in depth view and your thoughts on it. The cluster creation speed is amazimg

    • @DevOpsToolkit
      @DevOpsToolkit  Před rokem

      Something like
      czcams.com/video/SwOIlzXLIw4/video.html

    • @nootajay
      @nootajay Před rokem +1

      what is civo, is it like helm?

    • @DevOpsToolkit
      @DevOpsToolkit  Před rokem

      @@nootajay Civo is a service (Cloud) provider similar to AWS, AZure, GCP, Digital Ocean, Linode, etc.

    • @dandogamer
      @dandogamer Před rokem +1

      @@DevOpsToolkit ahh brilliant, must of missed this one thanks :)

  • @anthonymc6140
    @anthonymc6140 Před rokem +2

    Hi Viktor, any opinion on Otomi? have you tried it?

    • @DevOpsToolkit
      @DevOpsToolkit  Před rokem

      I tried it a long time ago. It probably changed a lot since then so I don't feel comfortable commenting on it without getting up to date.

    • @anthonymc6140
      @anthonymc6140 Před rokem +1

      @@DevOpsToolkit makes sense! Maybe a topic for a futur video...thanks again for the very informative content!

    • @DevOpsToolkit
      @DevOpsToolkit  Před rokem +1

      @@anthonymc6140 Good suggestion... Adding it to my TODO list...

  • @sebiuo5817
    @sebiuo5817 Před rokem +1

    crack

  •  Před rokem +1

    Never seen anyone call these set of functions IDP, IDP = en.wikipedia.org/wiki/Identity_provider

    • @DevOpsToolkit
      @DevOpsToolkit  Před rokem

      These days, IDP is commonly used as a short version of Internal Developer Platform. Identity Provider would be IdP (lower d). That being said, it is indeed confusing to use IDP when there is IdP. Yet, I haven't heard anyone using a different acronym for Internal Developer Platform.