move updated nodeclasses doc to preview

aws · Dec 13, 2023 · bb62cc9 · bb62cc9
1 parent 3098ccd
commit bb62cc9
Show file tree

Hide file tree

Showing 2 changed files with 33 additions and 33 deletions.
diff --git a/website/content/en/docs/concepts/nodeclasses.md b/website/content/en/docs/concepts/nodeclasses.md
@@ -56,9 +56,6 @@ spec:
   amiSelectorTerms:             
     - tags:
         karpenter.sh/discovery: "${CLUSTER_NAME}"
-
-  # Optional, use instance-store volumes for node ephemeral-storage
-  instanceStorePolicy: RAID0
 
   # Optional, overrides autogenerated userdata with a merge semantic
   userData: |                   
@@ -554,36 +551,6 @@ spec:
 
 The `Custom` AMIFamily ships without any default `blockDeviceMappings`.
 
-## spec.instanceStorePolicy
-
-The `instanceStorePolicy` field controls how [instance-store](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/InstanceStorage.html) volumes are handled. By default, Karpenter and Kubernetes will simply ignore them.
-
-### RAID0
-
-If you intend to use these volumes for faster node ephemeral-storage, set `instanceStorePolicy` to `RAID0`:
-
-```yaml
-spec:
-  instanceStorePolicy: RAID0
-```
-
-This will set the allocatable ephemeral-storage of each node to the total size of the instance-store volume(s). 
-
-The disks must be formatted & mounted in a RAID0 and be the underlying filesystem for the Kubelet & Containerd. Instructions for each AMI family are listed below:
-
-#### AL2
-
-On AL2, Karpenter automatically configures the disks through an additional boostrap argument (`--local-disks raid0`). The device name is `/dev/md/0` and its mount point is `/mnt/k8s-disks/0`. You should ensure any additional disk setup does not interfere with these.
-
-#### Others
-
-For all other AMI families, you must configure the disks yourself. Check out the [`setup-local-disks`](https://github.com/awslabs/amazon-eks-ami/blob/master/files/bin/setup-local-disks) script in [amazon-eks-ami](https://github.com/awslabs/amazon-eks-ami) to see how this is done for AL2.
-
-{{% alert title="Tip" color="secondary" %}}
-Since the Kubelet & Containerd will be using the instance-store filesystem, you may consider using a more minimal root volume size.
-{{% /alert %}}
-
-
 ## spec.userData
 
 You can control the UserData that is applied to your worker nodes via this field. This allows you to run custom scripts or pass-through custom configuration to Karpenter instances on start-up.

diff --git a/website/content/en/preview/concepts/nodeclasses.md b/website/content/en/preview/concepts/nodeclasses.md
@@ -56,6 +56,9 @@ spec:
   amiSelectorTerms:             
     - tags:
         karpenter.sh/discovery: "${CLUSTER_NAME}"
+
+  # Optional, use instance-store volumes for node ephemeral-storage
+  instanceStorePolicy: RAID0
 
   # Optional, overrides autogenerated userdata with a merge semantic
   userData: |                   
@@ -551,6 +554,36 @@ spec:
 
 The `Custom` AMIFamily ships without any default `blockDeviceMappings`.
 
+## spec.instanceStorePolicy
+
+The `instanceStorePolicy` field controls how [instance-store](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/InstanceStorage.html) volumes are handled. By default, Karpenter and Kubernetes will simply ignore them.
+
+### RAID0
+
+If you intend to use these volumes for faster node ephemeral-storage, set `instanceStorePolicy` to `RAID0`:
+
+```yaml
+spec:
+  instanceStorePolicy: RAID0
+```
+
+This will set the allocatable ephemeral-storage of each node to the total size of the instance-store volume(s). 
+
+The disks must be formatted & mounted in a RAID0 and be the underlying filesystem for the Kubelet & Containerd. Instructions for each AMI family are listed below:
+
+#### AL2
+
+On AL2, Karpenter automatically configures the disks through an additional boostrap argument (`--local-disks raid0`). The device name is `/dev/md/0` and its mount point is `/mnt/k8s-disks/0`. You should ensure any additional disk setup does not interfere with these.
+
+#### Others
+
+For all other AMI families, you must configure the disks yourself. Check out the [`setup-local-disks`](https://github.com/awslabs/amazon-eks-ami/blob/master/files/bin/setup-local-disks) script in [amazon-eks-ami](https://github.com/awslabs/amazon-eks-ami) to see how this is done for AL2.
+
+{{% alert title="Tip" color="secondary" %}}
+Since the Kubelet & Containerd will be using the instance-store filesystem, you may consider using a more minimal root volume size.
+{{% /alert %}}
+
+
 ## spec.userData
 
 You can control the UserData that is applied to your worker nodes via this field. This allows you to run custom scripts or pass-through custom configuration to Karpenter instances on start-up.