Building a Kubernetes CI/CD Pipeline With GitLab and Helm

Everyone loves GitLab CI and Kubernetes. GitLab CI (Continuous Integration) is a popular tool for building and testing software developers write for applications. GitLab CI helps developers build code faster, more confidently, and detect errors quickly.

Kubernetes, popularly shortened to K8s, is a portable, extensible, open-source platform for managing containerization workloads and services. K8s is used by companies of all sizes every day to automate deployment, scaling, and managing applications in containers.

The purpose of this article is to show how you can bolt on the Continuous Delivery (CD) piece of the puzzle to build a CI/CD pipeline so you can deploy your applications to Kubernetes. But before we get too far, we’re going to need to talk about Helm, which is an important part of the puzzle.

What the Helm?

Helm calls itself the package manager for Kubernetes. That’s a pretty accurate description. Helm is a versatile, sturdy tool DevOps consulting services engineers can use to define configuration files in, and perform a variable substitution to create consistent deployments to our clusters, and have different variables for different environments.

It’s certainly the right solution to the problem we’re covering here.

#kubernetes

What is GEEK

Buddha Community

50+ Useful Kubernetes Tools for 2020 - Part 2

Introduction

Last year, we provided a list of Kubernetes tools that proved so popular we have decided to curate another list of some useful additions for working with the platform—among which are many tools that we personally use here at Caylent. Check out the original tools list here in case you missed it.

According to a recent survey done by Stackrox, the dominance Kubernetes enjoys in the market continues to be reinforced, with 86% of respondents using it for container orchestration.

(State of Kubernetes and Container Security, 2020)

And as you can see below, more and more companies are jumping into containerization for their apps. If you’re among them, here are some tools to aid you going forward as Kubernetes continues its rapid growth.

(State of Kubernetes and Container Security, 2020)

#blog #tools #amazon elastic kubernetes service #application security #aws kms #botkube #caylent #cli #container monitoring #container orchestration tools #container security #containers #continuous delivery #continuous deployment #continuous integration #contour #developers #development #developments #draft #eksctl #firewall #gcp #github #harbor #helm #helm charts #helm-2to3 #helm-aws-secret-plugin #helm-docs #helm-operator-get-started #helm-secrets #iam #json #k-rail #k3s #k3sup #k8s #keel.sh #keycloak #kiali #kiam #klum #knative #krew #ksniff #kube #kube-prod-runtime #kube-ps1 #kube-scan #kube-state-metrics #kube2iam #kubeapps #kubebuilder #kubeconfig #kubectl #kubectl-aws-secrets #kubefwd #kubernetes #kubernetes command line tool #kubernetes configuration #kubernetes deployment #kubernetes in development #kubernetes in production #kubernetes ingress #kubernetes interfaces #kubernetes monitoring #kubernetes networking #kubernetes observability #kubernetes plugins #kubernetes secrets #kubernetes security #kubernetes security best practices #kubernetes security vendors #kubernetes service discovery #kubernetic #kubesec #kubeterminal #kubeval #kudo #kuma #microsoft azure key vault #mozilla sops #octant #octarine #open source #palo alto kubernetes security #permission-manager #pgp #rafay #rakess #rancher #rook #secrets operations #serverless function #service mesh #shell-operator #snyk #snyk container #sonobuoy #strongdm #tcpdump #tenkai #testing #tigera #tilt #vert.x #wireshark #yaml

Creating CI/CD Pipeline With Gitlab and DigitalOcean Managed Kubernetes

Peeyush Gupta, Sr. Developer Advocate from DigitalOcean, and Medhamsh Vuthpala, Tech Evangelist from Axelerant, discuss DigitalOcean Managed Kubernetes (DOKS) and Gitlab CI/CD pipelines, and demo how to integrate Gitlab with DOKS.

#kubernetes #gitlab #pipeline #ci #cd #doks

Serverless CI/CD on the AWS Cloud

CI/CD pipelines have long played a major role in speeding up the development and deployment of cloud-native apps. Cloud services like AWS lend themselves to more agile deployment through the services they offer as well as approaches such as Infrastructure as Code. There is no shortage of tools to help you manage your CI/CD pipeline as well.

While the majority of development teams have streamlined their pipelines to take full advantage of cloud-native features, there is still so much that can be done to refine CI/CD even further. The entire pipeline can now be built as code and managed either via Git as a single source of truth or by using visual tools to help guide the process.

The entire process can be fully automated. Even better, it can be made serverless, which allows the CI/CD pipeline to operate with immense efficiency. Git branches can even be utilized as a base for multiple pipelines. Thanks to the three tools from Amazon; AWS CodeCommit, AWS CodeBuild, and AWS CodeDeploy, serverless CI/CD on the AWS cloud is now easy to set up.

#aws #aws codebuild #aws codecommit #aws codedeploy #cd #cd pipeline #ci #ci/cd processes #ci/cd workflow #serverless

GitLab Runner Setup — CI/CD on AKS (Azure Kubernetes Service)

Runners are processes that pick up and execute jobs for GitLab. You can install the runner manually on your local machine, using docker on your local machine, a VM or automatically on a Kubernetes cluster.

The following steps should help you register an AKS cluster with GitLab and then install the agent on the cluster, and then register the agent with GitLab. I’m using GitLab Enterprise Edition 13.2.4–ee.

Firstly create an AKS cluster on Azure, once complete you’ll see something similar to below:

In Gitlab, first, enable CI/CD for the project under settings -> general -> pipelines.

You should now see a CI/CD option in the settings menu, again in the project you wish to enable CI/CD for, go to Settings -> CI/CD -> Install runner on Kubernetes:

Add Kubernetes Cluster:

Add existing cluster tab and fill in the details as follows:

1. Kubernetes cluster name (required) — The name you wish to give the cluster.
2. Environment scope (required) — The associated environment to this cluster.
3. API URL (required) — Get this from the Azure portal and add https:// in front of the URL, e.g. kubegitlabrunner-dns-322ea5bc.hcp.uksouth.azmk8s.io
4. CA certificate (required) — A valid Kubernetes certificate is needed to authenticate to the cluster. We will use the certificate created by default.

• Connect to the Kubernetes Cluster, hit connect in the portal to get the commands to run in azure cloud shell.

#gitlab #azure #ci-cd-pipeline #kubernetes #gitlab runner

GitLab CI/CD Tutorial | Build Production-ready CI/CD Pipelines

GitLab CI/CD Full Course released - CI/CD with Docker | K8s | Microservices!

Learn how to build production-ready CI/CD pipelines in one comprehensive and practical course!

GitLab CI/CD is one of the most popular CI/CD platforms! More and more companies are adopting it. So, the need for Developers or DevOps engineers, who know how to build complete CI/CD pipelines on GitLab is increasing.

While many GitLab courses teach you only the basics, we will dive into more advanced demos, like implementing dynamic versioning, using cache to speed up the pipeline execution or deploying to a K8s cluster. So, you'll have built several CI/CD pipelines with real life examples & best practices!
​
As usual you can expect complex topics explained in a simple way, animations to help you understand the concepts better and lots of hands-on demos!

▬▬▬▬▬▬  🚀 By the end of this course, you'll be able to... 🚀  ▬▬▬▬▬▬ 
✅  Confidently use GitLab CI/CD at your work
✅  Set up self-managed GitLab Runners
✅  Build and deploy containers with Docker Compose
✅  Build a Multi-Stage Pipeline
✅  Configure a CI/CD Pipeline for a Monorepo Microservices
✅  Configure a CI/CD Pipeline for a Polyrepo Microservices
✅  Deploy to a managed Kubernetes cluster
✅  Setup a CI/CD pipeline with best practices

▬▬▬▬▬▬  📚 What you'll learn 📚 ▬▬▬▬▬▬ 
✅  Pipelines, Jobs, Stages
✅  Regular & Secret Variables
✅  Workflow Rules
✅  Speed up Pipeline using Cache
✅  Configure Job Artifacts (test report, passing files and env vars)
✅  Conditionals
✅  GitLab Runners & Executors
✅  GitLab's built-in Docker registry
✅  GitLab Environments
✅  GitLab's Job Templates
✅  Reuse pipeline configuration by writing own job ci-templates library
✅  needs, dependencies, extends etc.

►  More Infos here: https://www.techworld-with-nana.com/gitlab-cicd-course

#gitlab #gitlabcicd #docker #k8s #microservices #ci #cd