You're reading from End-to-End Automation with Kubernetes and Crossplane Develop a control plane-based platform for unified infrastructure, services, and application automation

Product type Paperback

Published in Aug 2022

Publisher Packt

ISBN-13 9781801811545

Length 250 pages

Edition 1st Edition

Tools

Crossplane

Concepts

DevOps

Author (1):

Arun Ramakani

View More author details

Table of Contents (16) Chapters

Preface

1. Part 1: The Kubernetes Disruption

2. Chapter 1: Introducing the New Operating Model FREE CHAPTER

3. Chapter 2: Examining the State of Infrastructure Automation

4. Part 2: Building a Modern Infrastructure Platform

5. Chapter 3: Automating Infrastructure with Crossplane

6. Chapter 4: Composing Infrastructure with Crossplane

7. Chapter 5: Exploring Infrastructure Platform Patterns

8. Chapter 6: More Crossplane Patterns

9. Chapter 7: Extending and Scaling Crossplane

10. Part 3:Configuration Management Tools and Recipes

11. Chapter 8: Knowing the Trade-offs

12. Chapter 9: Using Helm, Kustomize, and KubeVela

13. Chapter 10: Onboarding Applications with Crossplane

14. Chapter 11: Driving the Platform Adoption

15. Other Books You May Enjoy

The repository and CI setup

At this stage, an XR/claim is developed to clone the template repository to create the new micro-frontend repository and CI pipeline. We can do this in two steps. First, we will configure GitLab, and then we’ll develop an XR/claim API.

GitLab configuration

We need to make the following one-time configurations in GitLab before we start the XR/claim API development:

Create the template project: We need to have a template repository from which we will make a new micro-frontend repository. You can access the template repository I have created at https://gitlab.com/unified.devops/react-template. The repository has a GitLab pipeline set up to build and push the Docker image into the Docker Hub registry. You can also set up a private registry here. We will automatically get the template project structure and CI set up while we clone the template repository for a micro-frontend. The Docker image name will be chosen based on the micro-frontend...