Webinar: Automating Kubernetes Deployments

    Join us for Kubernetes Forums Seoul, Sydney, Bengaluru and Delhi – learn more at kubecon.io

    Don’t miss KubeCon + CloudNativeCon 2020 events in Amsterdam March 30 – April 2, Shanghai July 28-30 and Boston November 17-20! Learn more at kubecon.io. The conference features presentations from developers and end users of Kubernetes, Prometheus, Envoy, and all of the other CNCF-hosted projects

    Kubernetes abstracts and simplifies many aspects configuring and scaling infrastructure, but still requires DevOps. Building CI/CD pipelines to correctly deploy to Kuberentes clusters is a time-consuming process. In this webinar, we’ll look at how GitLab is thinking about “CI/CD as code” with versionable and template-able pipelines. With re-usable code snippets, we’ll show how building pipelines can be simplified to just a few clicks while remaining fully customizable.


    Previous articleAzure Devops Tutorial for Beginners
    Next articleCreate Multibranch Pipeline with Git – Jenkins Pipeline Tutorial for Beginners 2/4


    1. He asked: "How long you need to setup a simple CI/CD pipeline?". The same questions that those non-technical IT managers will ask you like "What's the problem? It is so straight forward. I have seen GitLab demo on youtube, don't think you can lie to me that it takes hours to set it up." But the fact is, you will face all sorts of connection issues like what even a GitLab expert will faced in his presentation even though he probably have done this many times already. Yea, every non-technical folks think it is easy. And I don't blame them. I blame the product vendors who painted such a rosy picture that everything can be done in one click so in order to sell their products. The reality is not what it appears to be. And DevOps is not a solve-all-issues tooling that you can purchase out-of-the-box and then suddenly your org are instantly transformed into super-efficient org that rules the world, or so those CIO/COO/CEO would wishfully think throwing a million bucks at it will solve all problems. Garbage-in-garbage-out. Still need to clear your garbage first.

    2. Gitlab runner in kubernetes does not support fech strategy. On big size repos and often many jobs builds it make a lot of traffic to gitlab server by cloning repos on each jobs. Also kubernetes integration do not support runner configuration. If you need some specific options like volumes for dind or something else you need to run gitlab runner in k8s cluster manualy. Documentation about k8s runner do not cover a lot of things.