|
2 | 2 |
|
3 | 3 | [HIVE-1367](https://issues.redhat.com/browse/HIVE-1367)
|
4 | 4 |
|
5 |
| -- [Clusterpool for on-prem cloud providers](#clusterpool-for-on-prem-cloud-providers) |
6 |
| - - [Summary](#summary) |
7 |
| - - [Problem Statement](#problem-statement) |
8 |
| - - [Proposal](#proposal) |
9 |
| - - [Summary](#summary-1) |
10 |
| - - [`ClusterPool.Spec.Inventory`](#clusterpoolspecinventory) |
11 |
| - - [How To Use](#how-to-use) |
12 |
| - - [Validation](#validation) |
13 |
| - - [`Size` and `MaxSize`](#size-and-maxsize) |
14 |
| - - [Pool Version](#pool-version) |
15 |
| - - [Handling Inventory Updates](#handling-inventory-updates) |
16 |
| - - [Adding An Inventory](#adding-an-inventory) |
17 |
| - - [Adding An Entry to the Inventory](#adding-an-entry-to-the-inventory) |
18 |
| - - [Removing An Entry from the Inventory](#removing-an-entry-from-the-inventory) |
19 |
| - - [Deleting The Inventory](#deleting-the-inventory) |
20 |
| - - [Maintaining the lease of the ClusterDeploymentCustomization](#maintaining-the-lease-of-the-clusterdeploymentcustomization) |
21 |
| - - [Fairness](#fairness) |
22 |
| - - [Future](#future) |
23 |
| - - [Alternatives](#alternatives) |
24 |
| - - [Bespoke Inventory Definition](#bespoke-inventory-definition) |
25 |
| - - [Full Spec](#full-spec) |
26 |
| - - [Hooks](#hooks) |
| 5 | +- [Summary](#summary) |
| 6 | +- [Problem Statement](#problem-statement) |
| 7 | +- [Proposal](#proposal) |
| 8 | + - [Summary](#summary-1) |
| 9 | + - [`ClusterPool.Spec.Inventory`](#clusterpoolspecinventory) |
| 10 | + - [How To Use](#how-to-use) |
| 11 | + - [Validation](#validation) |
| 12 | + - [`Size` and `MaxSize`](#size-and-maxsize) |
| 13 | + - [Pool Version](#pool-version) |
| 14 | + - [Handling Inventory Updates](#handling-inventory-updates) |
| 15 | + - [Adding An Inventory](#adding-an-inventory) |
| 16 | + - [Adding An Entry to the Inventory](#adding-an-entry-to-the-inventory) |
| 17 | + - [Removing An Entry from the Inventory](#removing-an-entry-from-the-inventory) |
| 18 | + - [Deleting The Inventory](#deleting-the-inventory) |
| 19 | + - [Maintaining the lease of the ClusterDeploymentCustomization](#maintaining-the-lease-of-the-clusterdeploymentcustomization) |
| 20 | + - [Fairness](#fairness) |
| 21 | +- [Future](#future) |
| 22 | +- [Alternatives](#alternatives) |
| 23 | + - [Bespoke Inventory Definition](#bespoke-inventory-definition) |
| 24 | + - [Full Spec](#full-spec) |
| 25 | + - [Hooks](#hooks) |
27 | 26 |
|
28 | 27 | ## Summary
|
29 | 28 |
|
|
59 | 58 |
|
60 | 59 | and ClusterDeploymentCustomization CR will look like
|
61 | 60 | ```yaml
|
62 |
| -apiVersion: v1 |
| 61 | +apiVersion: hive.openshift.io/v1 |
63 | 62 | kind: ClusterDeploymentCustomization
|
64 | 63 | metadata:
|
65 | 64 | name: foo-cluster-deployment-customization
|
@@ -115,10 +114,10 @@ For the VSphere case, this allows the administrator to:
|
115 | 114 | - Create a ClusterDeploymentCustomization CR to patch `spec.metadata.name` field of the default install config generated by clusterpool controller. Please refer the section above of a sample CR. The content in `spec.installConfigPatches` field should be as follows
|
116 | 115 | ```yaml
|
117 | 116 | spec:
|
118 |
| - installConfigPatches: |
119 |
| - - op: replace |
120 |
| - path: metadata/name |
121 |
| - value: foo |
| 117 | + installConfigPatches: |
| 118 | + - op: replace |
| 119 | + path: metadata/name |
| 120 | + value: foo |
122 | 121 | ```
|
123 | 122 | - Add the name of ClusterDeploymentCustomization CR to `clusterPool.spec.inventory.ClusterDeploymentCustomizations` list. For ClusterDeploymentCustomization with a name `foo-cluster-deployment-customization` the clusterpool should be configured as follows
|
124 | 123 | ```yaml
|
|
0 commit comments