Running GitHub Self-Hosted Runners on AKS Virtual Nodes (backed by Azure Container Instances)

Поділитися
Вставка
  • Опубліковано 24 січ 2025

КОМЕНТАРІ • 5

  • @mohammadramezani7065
    @mohammadramezani7065 21 день тому

    Thanks alot. it was super helpful for me.keep up good work .

  • @stansidorov
    @stansidorov 2 роки тому +1

    This is awesome, thank you. I have a few questions. In your manifest you specified a particular repo. Is there way to set it up in a such way that it picks up an action job from any repo in the GitHub organization? And how much time it takes to provision a virtual node for a job? Thank you.

    • @Atmosera-
      @Atmosera-  2 роки тому

      You can create another manifest for the new job and repo. And the runner only runs for that job then scales back down. You can't do it for just any repo.

  • @anilnair5978
    @anilnair5978 5 місяців тому

    this is beautifully explained can you let me know how i can use my windows agent inside windows node

  • @flemminglund7361
    @flemminglund7361 7 місяців тому

    Hi, what if my AKS cluster is private, with my own vnet / subnet. In my workflow i need to run kubelogin which means I've to run in a user context in order to pickup kubelogin from environment variables. Is there any way to handle that on the fly, with github runners, or self-hosted runners , on-demand?