Skip to main content

Other - CICD

  • CI - Continuous Integration
  • CD - Continuous Delivery (building deployable artifacts / images)
  • CD - Continuous Deployment (deploying those artifacts / images)
  • CV - Continuous Verification

https://github.com/theonedev/onedev

Spinnaker​

https://www.spinnaker.io/concepts

image

Jenkins Operator​

https://jenkinsci.github.io/kubernetes-operator

Weave Flux​

Weaveworks are originally known for creating Weave Net, a container SDN now available as both a Docker plugin and Kubernetes CNI option. Today, the company offers an extensive and eye-candy dashboard and a cloud offering, Weave Cloud.The Flux Operator ⭐ 6.9k for Kubernetes allows GitOps style CD & release management where operator fetches the changes from git push events and handles the deployments gracefully. It continuously tries to match the declaritive configuration to the actualy deployment in Kubernetes. The cloud offering also has nice UI and Prometheus integration which aims to help your Continuous Delivery pipelines.

image

Flux​

The GitOps Kubernetes operator

We believe in GitOps

  • You declaratively describe the entire desired state of your system in git.This includes the apps, config, dashboards, monitoring and everything else.
  • What can be described can be automated.Use YAMLs to enforce conformance of the system. You don't need to runkubectl, all changes go through git. Use diff tools to detect divergence between observed and desired state and get notifications.
  • You push code not containers.Everything is controlled through pull requests. There is no learning curve for new devs, they just use your standard git PR process. The history in git allows you to recover from any snapshot as you have a sequence of transactions. It is much more transparent to make operational changes by pull request, e.g. fix a production issue via a pull request instead of making changes to the running system.

Flux is a tool that automatically ensures that the state of a cluster matches the config in git. It uses an operator in the cluster to trigger deployments inside Kubernetes, which means you don't need a separate CD tool. It monitors all relevant image repositories, detects new images, triggers deployments and updates the desired running configuration based on that (and a configurable policy).

The benefits are: you don't need to grant your CI access to the cluster, every change is atomic and transactional, git has your audit log. Each transaction either fails or succeeds cleanly. You're entirely code centric and don't need new infrastructure.

image

https://github.com/fluxcd/flux

Tekton (+1)​

Kubernetes-native CI/CD

Tekton is a powerful and flexibleopen-source framework for creating CI/CD systems, allowing developers tobuild, test, and deployacross cloud providers and on-premise systems.

CRDs​

  • Task
  • PipelineResource
  • Pipeline
  • TaskRun
  • PipelineRun

https://cloud.google.com/tekton

https://github.com/tektoncd/pipeline

https://tekton.dev

https://github.com/tektoncd/dashboard

How to Build Cloud-Native CI/CD Pipelines With Tekton on Kubernetes- Speakers: Nikhil Thomas

Keel​

Kubernetes Operator to automate Helm, DaemonSet, StatefulSet & Deployment updates

https://keel.sh

https://github.com/keel-hq/keel

DroneCI​

Drone is a self-service Continuous Delivery platform for busy development teams.

Drone is a Container-Native, Continuous Delivery Platform

Drone is a Continuous Delivery system built on container technology. Drone uses a simple YAML configuration file, a superset of docker-compose, to define and execute Pipelines inside Docker containers.

https://drone.io

https://github.com/drone/drone

https://www.youtube.com/watch?v=myCcJJ_Fk10

Concourse​

https://github.com/concourse/concourse

https://concourse-ci.org

CicleCI​

https://www.youtube.com/watch?v=kDWHPlrEgEY

Semaphore​

CI/CD​

https://medium.com/axons/ci-cd-with-argo-on-kubernetes-28c1a99616a9

https://medium.com/@andrew.kaczynski/gitops-in-kubernetes-argo-cd-and-gitlab-ci-cd-5828c8eb34d6

GitlabCI​

Example​

image: docker:latest

services:
    - docker:dind

stages:
    - build
    - deploy

variables:
    # Common
    AWS_ACCESS_KEY_ID: $AWS_ACCESS_KEY_ID
    AWS_SECRET_ACCESS_KEY: $AWS_SECRET_ACCESS_KEY
    AWS_REGION: $AWS_REGION
    S3_BUCKET_NAME: $S3_BUCKET_NAME
    CDN_DISTRIBUTION_ID: $CDN_DISTRIBUTION_ID

cache:
    key: $CI_COMMIT_REF_SLUG
    paths:
    - node_modules/

######################
##   BUILD STAGE    ##
######################
Build:
    stage: build
    image: node:latest
    script:
    - yarn install
    - yarn build
    artifacts:
    paths:
    - build/
    expire_in: 1 day

######################
##   DEPLOY STAGE   ##
######################
Deploy:
    stage: deploy
    when: manual
    before_script:
    - apk add --no-cache curl jq py-pip
    - pip install awscli
    - eval $(aws ecr get-login --no-include-email --region $AWS_REGION | sed 's|https://||')

    script:
        - aws s3 cp build/ s3://$S3_BUCKET_NAME/test/ --recursive --include "*"
        - aws cloudfront create-invalidation --distribution-id $CDN_DISTRIBUTION_ID --paths "/*"

Deploy:
    stage: deploy
    image: registry.gitlab.com/gitlab-org/cloud-deploy/aws-base:latest
    script:
        - aws s3 sync build/ s3://$S3_BUCKET_NAME/metta-web/$S3_BUCKET_PATH/ --delete
        - aws cloudfront create-invalidation --distribution-id $CDN_DISTRIBUTION_ID --paths "/*"

Others​