You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: modules/installation-azure-stack-hub-config-yaml.adoc
+70-50Lines changed: 70 additions & 50 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -30,13 +30,22 @@ apiVersion: v1
30
30
baseDomain: example.com
31
31
controlPlane: <1>
32
32
name: master
33
+
platform:
34
+
azure:
35
+
osDisk:
36
+
diskSizeGB: 1024 <2>
37
+
diskType: premium_LRS
33
38
replicas: 3
34
39
compute: <1>
35
40
- name: worker
36
-
platform: {}
41
+
platform:
42
+
azure:
43
+
osDisk:
44
+
diskSizeGB: 512 <2>
45
+
diskType: premium_LRS
37
46
replicas: 0
38
47
metadata:
39
-
name: test-cluster <2>
48
+
name: test-cluster <3>
40
49
networking:
41
50
clusterNetwork:
42
51
- cidr: 10.128.0.0/14
@@ -53,50 +62,51 @@ endif::openshift-origin[]
53
62
- 172.30.0.0/16
54
63
platform:
55
64
azure:
56
-
armEndpoint: azurestack_arm_endpoint <3>
57
-
baseDomainResourceGroupName: resource_group <4>
58
-
region: azure_stack_local_region <5>
59
-
resourceGroupName: existing_resource_group <6>
65
+
armEndpoint: azurestack_arm_endpoint <4>
66
+
baseDomainResourceGroupName: resource_group <5>
67
+
region: azure_stack_local_region <6>
68
+
resourceGroupName: existing_resource_group <7>
60
69
outboundType: Loadbalancer
61
-
cloudName: AzureStackCloud <7>
62
-
pullSecret: '{"auths": ...}' <8>
70
+
cloudName: AzureStackCloud <8>
71
+
pullSecret: '{"auths": ...}' <9>
63
72
ifndef::openshift-origin[]
64
-
fips: false <9>
65
-
additionalTrustBundle: | <10>
73
+
fips: false <10>
74
+
additionalTrustBundle: | <11>
66
75
-----BEGIN CERTIFICATE-----
67
76
<MY_TRUSTED_CA_CERT>
68
77
-----END CERTIFICATE-----
69
-
sshKey: ssh-ed25519 AAAA... <11>
78
+
sshKey: ssh-ed25519 AAAA... <12>
70
79
endif::openshift-origin[]
71
80
ifdef::openshift-origin[]
72
-
additionalTrustBundle: | <9>
81
+
additionalTrustBundle: | <10>
73
82
-----BEGIN CERTIFICATE-----
74
83
<MY_TRUSTED_CA_CERT>
75
84
-----END CERTIFICATE-----
76
-
sshKey: ssh-ed25519 AAAA... <10>
85
+
sshKey: ssh-ed25519 AAAA... <11>
77
86
endif::openshift-origin[]
78
87
----
79
88
<1> The `controlPlane` section is a single mapping, but the compute section is a sequence of mappings. To meet the requirements of the different data structures, the first line of the `compute` section must begin with a hyphen, `-`, and the first line of the `controlPlane` section must not. Although both sections currently define a single machine pool, it is possible that future versions of {product-title} will support defining multiple compute pools during installation. Only one control plane pool is used.
80
-
<2> Specify the name of the cluster.
81
-
<3> Specify the Azure Resource Manager endpoint that your Azure Stack Hub operator provides.
82
-
<4> Specify the name of the resource group that contains the DNS zone for your base domain.
83
-
<5> Specify the name of your Azure Stack Hub local region.
84
-
<6> Specify the name of an already existing resource group to install your cluster to. If undefined, a new resource group is created for the cluster.
85
-
<7> Specify the Azure Stack Hub environment as your target platform.
86
-
<8> Specify the pull secret required to authenticate your cluster.
89
+
<2> You can specify the size of the disk to use in GB. Minimum recommendation for control plane nodes is 1024 GB.
90
+
<3> Specify the name of the cluster.
91
+
<4> Specify the Azure Resource Manager endpoint that your Azure Stack Hub operator provides.
92
+
<5> Specify the name of the resource group that contains the DNS zone for your base domain.
93
+
<6> Specify the name of your Azure Stack Hub local region.
94
+
<7> Specify the name of an already existing resource group to install your cluster to. If undefined, a new resource group is created for the cluster.
95
+
<8> Specify the Azure Stack Hub environment as your target platform.
96
+
<9> Specify the pull secret required to authenticate your cluster.
87
97
ifndef::openshift-origin[]
88
-
<9> Whether to enable or disable FIPS mode. By default, FIPS mode is not enabled. If FIPS mode is enabled, the {op-system-first} machines that {product-title} runs on bypass the default Kubernetes cryptography suite and use the cryptography modules that are provided with {op-system} instead.
98
+
<10> Whether to enable or disable FIPS mode. By default, FIPS mode is not enabled. If FIPS mode is enabled, the {op-system-first} machines that {product-title} runs on bypass the default Kubernetes cryptography suite and use the cryptography modules that are provided with {op-system} instead.
89
99
+
90
100
[IMPORTANT]
91
101
====
92
102
The use of FIPS Validated / Modules in Process cryptographic libraries is only supported on {product-title} deployments on the `x86_64` architecture.
93
103
====
94
-
<10> If your Azure Stack Hub environment uses an internal certificate authority (CA), add the necessary certificate bundle in `.pem` format.
95
-
<11> You can optionally provide the `sshKey` value that you use to access the machines in your cluster.
104
+
<11> If your Azure Stack Hub environment uses an internal certificate authority (CA), add the necessary certificate bundle in `.pem` format.
105
+
<12> You can optionally provide the `sshKey` value that you use to access the machines in your cluster.
96
106
endif::openshift-origin[]
97
107
ifdef::openshift-origin[]
98
-
<9> If your Azure Stack Hub environment uses an internal certificate authority (CA), add the necessary certificate bundle in `.pem` format.
99
-
<10> You can optionally provide the `sshKey` value that you use to access the machines in your cluster.
108
+
<10> If your Azure Stack Hub environment uses an internal certificate authority (CA), add the necessary certificate bundle in `.pem` format.
109
+
<11> You can optionally provide the `sshKey` value that you use to access the machines in your cluster.
<2> If you do not provide these parameters and values, the installation program provides the default value.
166
185
<3> The `controlPlane` section is a single mapping, but the `compute` section is a sequence of mappings. To meet the requirements of the different data structures, the first line of the `compute` section must begin with a hyphen, `-`, and the first line of the `controlPlane` section must not. Although both sections currently define a single machine pool, it is possible that future versions of {product-title} will support defining multiple compute pools during installation. Only one control plane pool is used.
167
-
<4> The name of the cluster.
168
-
<5> The Azure Resource Manager endpoint that your Azure Stack Hub operator provides.
169
-
<6> The name of the resource group that contains the DNS zone for your base domain.
170
-
<7> The name of your Azure Stack Hub local region.
171
-
<8> The name of an existing resource group to install your cluster to. If undefined, a new resource group is created for the cluster.
172
-
<9> The URL of a storage blob in the Azure Stack environment that contains an {op-system} VHD.
173
-
<10> The pull secret required to authenticate your cluster.
186
+
<4> You can specify the size of the disk to use in GB. Minimum recommendation for control plane nodes is 1024 GB.
187
+
<5> The name of the cluster.
188
+
<6> The Azure Resource Manager endpoint that your Azure Stack Hub operator provides.
189
+
<7> The name of the resource group that contains the DNS zone for your base domain.
190
+
<8> The name of your Azure Stack Hub local region.
191
+
<9> The name of an existing resource group to install your cluster to. If undefined, a new resource group is created for the cluster.
192
+
<10> The URL of a storage blob in the Azure Stack environment that contains an {op-system} VHD.
193
+
<11> The pull secret required to authenticate your cluster.
174
194
ifndef::openshift-origin[]
175
-
<11> Whether to enable or disable FIPS mode. By default, FIPS mode is not enabled. If FIPS mode is enabled, the {op-system-first} machines that {product-title} runs on bypass the default Kubernetes cryptography suite and use the cryptography modules that are provided with {op-system} instead.
195
+
<12> Whether to enable or disable FIPS mode. By default, FIPS mode is not enabled. If FIPS mode is enabled, the {op-system-first} machines that {product-title} runs on bypass the default Kubernetes cryptography suite and use the cryptography modules that are provided with {op-system} instead.
176
196
+
177
197
[IMPORTANT]
178
198
====
179
199
The use of FIPS Validated / Modules in Process cryptographic libraries is only supported on {product-title} deployments on the `x86_64` architecture.
180
200
====
181
-
<12> You can optionally provide the `sshKey` value that you use to access the machines in your cluster.
201
+
<13> You can optionally provide the `sshKey` value that you use to access the machines in your cluster.
182
202
endif::openshift-origin[]
183
203
ifdef::openshift-origin[]
184
-
<11> You can optionally provide the `sshKey` value that you use to access the machines in your cluster.
204
+
<12> You can optionally provide the `sshKey` value that you use to access the machines in your cluster.
185
205
endif::openshift-origin[]
186
206
+
187
207
[NOTE]
188
208
====
189
209
For production {product-title} clusters on which you want to perform installation debugging or disaster recovery, specify an SSH key that your `ssh-agent` process uses.
190
210
====
191
211
ifndef::openshift-origin[]
192
-
<13> If the Azure Stack Hub environment is using an internal Certificate Authority (CA), adding the CA certificate is required.
212
+
<14> If the Azure Stack Hub environment is using an internal Certificate Authority (CA), adding the CA certificate is required.
193
213
endif::openshift-origin[]
194
214
ifdef::openshift-origin[]
195
-
<12> If the Azure Stack Hub environment is using an internal Certificate Authority (CA), adding the CA certificate is required.
215
+
<13> If the Azure Stack Hub environment is using an internal Certificate Authority (CA), adding the CA certificate is required.
0 commit comments