Why EVERYONE should use Azure DevOps Environments for Kubernetes deployments

Поделиться
HTML-код
  • Опубликовано: 14 дек 2024

Комментарии • 17

  • @CoderDave
    @CoderDave  4 года назад +2

    ✨Question of the day✨: how do you deploy to your Kubernetes cluster?

  • @anjanakrishnana7098
    @anjanakrishnana7098 2 года назад +1

    Hi @CoderDave Thanks for this great info. Is it possible to use this environment feature with a private AKS cluster too?

    • @CoderDave
      @CoderDave  2 года назад

      Yes you definitely can use it also with private clusters :)

  • @OPCDE
    @OPCDE 4 года назад +1

    Super underrated video! When was that feature released?

    • @CoderDave
      @CoderDave  4 года назад +2

      Thanks! It actually a pretty “old” feature (it’s been initially released on May 10th, 2019 docs.microsoft.com/en-us/azure/devops/release-notes/2019/build-may#kubernetes-integration-for-azure-pipelines) but not many people knows it’s there 😊

    • @OPCDE
      @OPCDE 4 года назад

      @@CoderDave Excellent. I bumped into it and fell on your video after searching a good summary explanation.

    • @CoderDave
      @CoderDave  4 года назад

      Glad to have been helpful 😊 this is a very difficult niche to be on, but if I can help even just 1 person then I’m happy

  • @sukritkapil
    @sukritkapil 4 года назад +1

    Hi Dave,
    Hope everything is great on your end. How did you add the Kubernetes resource? Did you get the 12 month free Azure subscription?

    • @CoderDave
      @CoderDave  4 года назад +1

      Hi. I do have some Azure accounts, but you can actually add any Kubernetes cluster you have. If you have it on Azure with AKS, then the procedure is the one you see in the video (and you can do that even with the free Azure trial account). If you instead have your K8S cluster anywhere else, then you can just add it with the settings page

    • @sukritkapil
      @sukritkapil 4 года назад

      @@CoderDave Thanks!!

  • @ackrite8139
    @ackrite8139 2 года назад +1

    The Kubernetes dashboard is really cool. But problem is that I deploy a very complex on-prem cluster with a lot of components and I only build/test all the services individually in Pipelines and then bring everything together in Azure Release Pipelines where I put together the helm chart with token replacer, update image versions and also perform the linting, validation, deployment, rollback with different stages connected together. Is there a way to get the Environment to start tracking the status of the kubernetes namespace even if I never deployed to it from a normal pipeline?

    • @CoderDave
      @CoderDave  2 года назад +1

      Not that I know of, the easier workaround would be to have a dummy pipeline which “pretends” to deploy to that namespace

    • @ackrite8139
      @ackrite8139 2 года назад

      Ah so the environment doesn’t care about what/if you actually deploy to the cluster? Perfect then I’ll add a dummy CD stage to my Helm CI Pipeline. Thanks a lot!

  • @АртемАрте-г5х
    @АртемАрте-г5х 3 года назад +1

    It was cool if you'll explain how to use Envts with real machines (servers), not containers. Most of developers still use large eco-systems with real servers and virtual machines.

    • @CoderDave
      @CoderDave  3 года назад +1

      I actually have a video that talk just about that: Azure DevOps Environments for Virtual Machines EXPLAINED ruclips.net/video/zBr7cl6ASMQ/видео.html

    • @carlosgarcialalicata
      @carlosgarcialalicata 2 года назад

      I love how people keep saying "most developers" do this, or do that.... where do they get that info from? For example, as of today, I personally know many more developers using containers than plain VMs - but of course I would never say "most developers", since I know a handful of them