openshift/openshift-docs
1
0
Fork 0
mirror of https://github.com/openshift/openshift-docs.git synced 2026-02-07 09:46:53 +01:00
Code Issues Releases Activity

Adding IMDS information to ROSA/OSD

Browse Source
This commit is contained in:
Eric Ponvelle
2023-08-09 14:27:50 -04:00
committed by openshift-cherrypick-robot
parent 4cd57cd1fa
commit a06e4f3501
1 changed files with 17 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

17
modules/osd-create-cluster-ccs.adoc
View File

@@ -166,6 +166,23 @@ PVs created by using any other storage class are still encrypted, but the PVs ar
After your cluster is created, you can change the number of compute nodes in your cluster, but you cannot change the compute node instance type in a machine pool. The number and types of nodes available to you depend on your {product-title} subscription.
====
. Choose your preference for the Instance Metadata Service (IMDS) type, either using both IMDSv1 and IMDSv2 types or requiring your EC2 instances to use only IMDSv2. You can access instance metadata from a running instance in two ways:
+
* Instance Metadata Service Version 1 (IMDSv1) - a request/response method
* Instance Metadata Service Version 2 (IMDSv2) - a session-oriented method
+
[IMPORTANT]
====
The Instance Metadata Service settings cannot be changed after your cluster is created.
====
+
[NOTE]
====
IMDSv2 uses session-oriented requests. With session-oriented requests, you create a session token that defines the session duration, which can range from a minimum of one second to a maximum of six hours. During the specified duration, you can use the same session token for subsequent requests. After the specified duration expires, you must create a new session token to use for future requests.
====
+
For more information regarding IMDS, see link:https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ec2-instance-metadata.html[Instance metadata and user data] in the AWS documentation.
. Optional: Expand *Edit node labels* to add labels to your nodes. Click *Add label* to add more node labels and select *Next*.
. On the *Network configuration* page, select *Public* or *Private* to use either public or private API endpoints and application routes for your cluster.