ACCESS_TOKEN

This course introduces you to serverless computing using Knative, teaches CI/CD using Tekton, and shows you how to build pipelines triggered by GitHub events.

How to Build a Serverless App Platform on Kubernetes-01.png

knative.tar.gz

DigitalOcean Account

Install Knative

​​Businesses are modernizing and adopting multi-cloud approaches to deliver services. This shift in application deployment has given rise to containerization and Kubernetes for the deployment, management, and scaling of containerized applications. 

This course introduces you to serverless computing and shows you how to build serverless applications using Knative. It teaches CI/CD using Tekton and shows you how to build pipelines triggered by GitHub events. You will create a pipeline that builds container images using Build and, later, Cloud Native Buildpacks. 

In the last part of the course, you will build a web application that integrates with GitHub using a GitHub App, and triggers application build and deployment in response to GitHub events.

Building a Serverless App Platform on Kubernetes

## What is CI/CD?
Developers continually commit code in small increments (usually several times a day), which is then built and tested before it’s merged. 

**Continuous integration (CI)** refers to our application’s automated building and testing on every new commit. Continuous integration works well with Agile methodologies so that developers work on incremental stories, and the code for those stories is merged incrementally into a shared folder/git repo. Continuous integration deals with packaging the code into an executable artifact, leaving out a key part of the software delivery process.

**Continuous deployment (CD)** is the final phase of the software delivery process. It automates the deployment of our software after the test and builds phases that are successful. Where and how the software is deployed depends on what type of infrastructure we’re deploying to.

A **CI/CD pipeline** is a set of processes that run when we change our code. It takes the code, builds it, runs the necessary test, and then deploys it to the desired environment or infrastructure.



# What is CI/CD?
Developers continually commit code in small increments (usually several times a day), which is then built and tested before it’s merged. 

**Continuous integration (CI)** refers to our application’s automated building and testing on every new commit. Continuous integration works well with Agile methodologies so that developers work on incremental stories, and the code for those stories is merged incrementally into a shared folder/git repo. Continuous integration deals with packaging the code into an executable artifact, leaving out a key part of the software delivery process.

**Continuous deployment (CD)** is the final phase of the software delivery process. It automates the deployment of our software after the test and builds phases that are successful. Where and how the software is deployed depends on what type of infrastructure we’re deploying to.

A **CI/CD pipeline** is a set of processes that run when we change our code. It takes the code, builds it, runs the necessary test, and then deploys it to the desired environment or infrastructure.



Learn about Tekton and its core components.

Before We Begin

Introduction

Using Knative to Run Serverless Applications

CI/CD Using Tekton

Automate Tekton Pipeline Execution

Build Container Images without Dockerfile

Build the UI For the Platform

Introduction to CI/CD and Tekton

What is CI/CD?