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/virt-aws-bm.adoc
+16-30Lines changed: 16 additions & 30 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -6,11 +6,18 @@
6
6
[id="virt-aws-bm_{context}"]
7
7
= {VirtProductName} on AWS bare metal
8
8
9
-
You can run {VirtProductName} on an Amazon Web Services (AWS) bare-metal {product-title} cluster. Before you set up your cluster, review the following summary of supported features and limitations:
9
+
You can run {VirtProductName} on an Amazon Web Services (AWS) bare-metal {product-title} cluster.
10
+
11
+
[NOTE]
12
+
====
13
+
{VirtProductName} is also supported on {product-rosa} (ROSA) Classic clusters, which have the same configuration requirements as AWS bare-metal clusters.
14
+
====
15
+
16
+
Before you set up your cluster, review the following summary of supported features and limitations:
10
17
11
18
Installing::
12
19
--
13
-
* You can install the cluster by using installer-provisioned infrastructure, ensuring that you specify bare-metal node instance types in the `install-config.yaml` file. For example, you can use the `c5n.metal` type value for a machine based on x86_64 architecture.
20
+
* You can install the cluster by using installer-provisioned infrastructure, ensuring that you specify bare-metal instance types for the worker nodes by editing the `install-config.yaml` file. For example, you can use the `c5n.metal` type value for a machine based on x86_64 architecture.
14
21
+
15
22
For more information, see the {product-title} documentation about installing on AWS.
16
23
--
@@ -29,32 +36,11 @@ Networking::
29
36
30
37
Storage::
31
38
--
32
-
* link:https://docs.portworx.com/portworx-enterprise/install-portworx/openshift[Portworx] is supported as a storage provider for {VirtProductName} on AWS bare metal.
33
-
** To use Portworx with {VirtProductName}, you must configure the `StorageClass` manifest to support live migration. For example:
39
+
* You can use any storage solution that is certified by the storage vendor to work with the underlying platform.
34
40
+
35
-
.Example `StorageClass` manifest
36
-
[source,yaml]
37
-
----
38
-
allowVolumeExpansion: true
39
-
apiVersion: storage.k8s.io/v1
40
-
kind: StorageClass
41
-
metadata:
42
-
annotations:
43
-
params/aggregation_level: Specifies the number of replication sets the volume
44
-
can be aggregated from
45
-
#...
46
-
name: px-csi-db-shared
47
-
parameters:
48
-
io_profile: db_remote
49
-
repl: "2" <1>
50
-
sharedv4: "true"
51
-
sharedv4_mount_options: vers=3.0,nolock <2>
52
-
sharedv4_svc_type: ClusterIP
53
-
provisioner: pxd.portworx.com
54
-
reclaimPolicy: Delete
55
-
volumeBindingMode: Immediate
56
-
----
57
-
<1> Use `repl: "2"` for a cluster with 3 worker nodes.
58
-
<2> You must use NFS version 3 with the `nolock` mount option.
59
-
--
60
-
* Amazon Elastic File System (EFS) and Amazon Elastic Block Store (EBS) are not supported for use with {VirtProductName} due to performance and functionality limitations.
41
+
[IMPORTANT]
42
+
====
43
+
AWS bare-metal and ROSA clusters might have different supported storage solutions. Ensure that you confirm support with your storage vendor.
44
+
====
45
+
* Amazon Elastic File System (EFS) and Amazon Elastic Block Store (EBS) are not supported for use with {VirtProductName} due to performance and functionality limitations.
0 commit comments