GitLab End to End Pipelines on Kubernetes with Maven, Nexus, SonarQube, Kaniko & Helm

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

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

  • @Newtrojan
    @Newtrojan Месяц назад +1

    Great content. Subscribed. How do we manage a gitops based approach with multiple teams, owning different products with different IAC configs and multiple environments like qa dev prod.

    • @DevOpsMadeEasy
      @DevOpsMadeEasy  Месяц назад

      You may check IaC wrappers like atmos.tools, terragrunt or terramate

  • @yashwanthreddy3946
    @yashwanthreddy3946 10 месяцев назад +1

    Great video

  • @janez_fem2664
    @janez_fem2664 10 месяцев назад +1

    Thank you so much for this project. Say we have multiple applications to run (microservices), what will change with this approach? Do you have any video on this, please

    • @DevOpsMadeEasy
      @DevOpsMadeEasy  9 месяцев назад +1

      You can build each application in the build stage and deploy the whole app with a helm chart in the deploy stage. Usually a single helm will deploy all your microservices by having them included as subcharts.

  • @AK-lx3yg
    @AK-lx3yg 10 месяцев назад +1

    Thanks!

  • @sahild6584
    @sahild6584 Год назад +1

    Thnx

  • @djwasky
    @djwasky Месяц назад

    Great job.
    When I do Deploy the Nexus only accept my .jar if version is ended up with "-SNAPSHOT". Why? How to deploy without this sufix?

    • @DevOpsMadeEasy
      @DevOpsMadeEasy  Месяц назад

      If snapshot repository is used then snapshot will be appended

  • @amitverma7545
    @amitverma7545 10 месяцев назад

    Git lab runners setup didn’t include in previous tutorial

  • @user-lh7pk2sh4t
    @user-lh7pk2sh4t 4 месяца назад

    thanks