liveBook · Manning

Multi-cloud deployment

As explained in Platform Engineering on Kubernetes

A multi-cloud strategy is an approach for using or operating across services and infrastructure from multiple cloud providers.

Multi-cloud deployment operates application infrastructure across multiple cloud providers. It addresses provider-specific provisioning, configuration drift, upgrades, monitoring, and the coordination required to keep application dependencies available and reproducible. section 1.4.3 section 5.1

The central implementation move is to define infrastructure through Kubernetes APIs rather than directly through cloud-specific tools. Crossplane supplies a Kubernetes-native control plane, supports multiple providers, and enables higher-level abstractions for application dependencies. section 5.1 section 5.2

A practical multi-cloud setup typically involves:

  • Identifying application infrastructure such as databases, message brokers, and identity services. section 1.4.3
  • Versioning and monitoring infrastructure configuration so environments can be reproduced for testing and troubleshooting. section 5.1
  • Installing Crossplane in a Kubernetes cluster and configuring providers for the required cloud services. section 5.2
  • Exposing composite resources as standardized self-service interfaces for application teams. section 5.5

Crossplane-provisioned application infrastructure

A platform team can define a composite resource for an application's database or message broker. Application teams request that resource through Kubernetes APIs, while Crossplane maps the request to the configured cloud provider without exposing provider-specific provisioning tools. section 1.4.3 section 5.5

How Platform Engineering on Kubernetes covers it

How deep it goes
Defines the operational problem and gives a declarative Crossplane path, stopping short of detailed provider configuration or composition syntax.
Examples
Uses databases, message brokers, identity services, and Crossplane-provisioned composite resources as infrastructure examples.
What it assumes
Requires a Kubernetes cluster, Crossplane control plane, and provider configurations before provisioning infrastructure.
What you can do after
Apply it via Crossplane to provision application infrastructure through Kubernetes APIs and request resources using self-service interfaces.
How it connects
Connects Kubernetes APIs, Crossplane, declarative infrastructure, application infrastructure, and cloud-provider abstraction.

Also explained in

Compare how 3 books explain multi-cloud deployment →

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Platform Engineering on Kubernetes. The section links point to the parts of the book it draws on.