Book Image

Effortless Cloud-Native App Development Using Skaffold

By : Ashish Choudhary
Book Image

Effortless Cloud-Native App Development Using Skaffold

By: Ashish Choudhary

Overview of this book

Kubernetes has become the de facto standard for container orchestration, drastically improving how we deploy and manage cloud-native apps. Although it has simplified the lives of support professionals, we cannot say the same for developers who need to be equipped with better tools to increase productivity. An automated workflow that solves a wide variety of problems that every developer faces can make all the difference! Enter Skaffold – a command-line tool that automates the build, push, and deploy steps for Kubernetes applications. This book is divided into three parts, starting with common challenges encountered by developers in building apps with Kubernetes. The second part covers Skaffold features, its architecture, supported container image builders, and more. In the last part, you'll focus on practical implementation, learning how to deploy Spring Boot apps to cloud platforms such as Google Cloud Platform (GCP) using Skaffold. You'll also create CI/CD pipelines for your cloud-native apps with Skaffold. Although the examples covered in this book are written in Java and Spring Boot, the techniques can be applied to apps built using other technologies too. By the end of this Skaffold book, you'll develop skills that will help accelerate your inner development loop and be able to build and deploy your apps to the Kubernetes cluster with Skaffold.
Table of Contents (15 chapters)
1
Section 1: The Kubernetes Nightmare – Skaffold to the Rescue
5
Section 2: Getting Started with Skaffold
9
Section 3: Building and Deploying Cloud-Native Spring Boot Applications with Skaffold

Getting started with GitHub Actions

GitHub Actions allows you to build, test, and deploy your workloads from your GitHub repository GitHub Actions is event-driven; for example, when someone creates a pull request, opens an issue, does a deployment, and so on. The specific actions are triggered based upon the events. You can even create your own GitHub Actions to customize the workflow based upon your use case. There is a great marketplace available too, at https://github.com/marketplace, from where you can integrate existing GitHub Actions into your workflow.

GitHub Actions uses a YAML syntax file to define events, jobs, actions, and commands. In the following diagram, you can see a complete list of GitHub Actions components:

Figure 9.1 – GitHub Actions components

Let's discuss the GitHub components in detail:

  • Workflow: This is used to build, test, package, release, or deploy the project on GitHub. A workflow consists of jobs and is triggered...