Postpone ClusterClass blog
This commit is contained in:
+3
-3
@@ -1,7 +1,7 @@
|
||||
---
|
||||
layout: blog
|
||||
title: "Introducing ClusterClass and Managed Topologies in Cluster API"
|
||||
date: 2021-10-04
|
||||
date: 2021-10-08
|
||||
slug: capi-clusterclass-and-managed-topologies
|
||||
---
|
||||
|
||||
@@ -29,7 +29,7 @@ As the name suggests, ClusterClass and managed topologies are built in two parts
|
||||
|
||||
The idea behind ClusterClass is simple: define the shape of your cluster once, and reuse it many times, abstracting the complexities and the internals of a Kubernetes cluster away.
|
||||
|
||||

|
||||

|
||||
|
||||
ClusterClass, at its heart, is a collection of Cluster and Machine templates. You can use it as a “stamp” that can be leveraged to create many clusters of a similar shape.
|
||||
|
||||
@@ -92,7 +92,7 @@ Managed Topologies let you put the power of ClusterClass into action.
|
||||
|
||||
Given a ClusterClass, you can create many Clusters of a similar shape by providing a single resource, the Cluster.
|
||||
|
||||

|
||||

|
||||
|
||||
Here is an example:
|
||||
|
||||
|
Before Width: | Height: | Size: 39 KiB After Width: | Height: | Size: 39 KiB |
|
Before Width: | Height: | Size: 36 KiB After Width: | Height: | Size: 36 KiB |
Reference in New Issue
Block a user