Separate the command line commands in the getting started guide last …

…part (#1429)

Seperates all the remaining command line instructions into .sh files for the getting started with EKS doc.

website/content/en/preview/getting-started/getting-started-with-eksctl/_index.md

@@ -87,53 +87,33 @@ Karpenter requires permissions like launching instances. This will create an AWS
 
 This step is only necessary if this is the first time you're using EC2 Spot in this account. More details are available [here](https://docs.aws.amazon.com/batch/latest/userguide/spot_fleet_IAM_role.html).
 
-```bash
-aws iam create-service-linked-role --aws-service-name spot.amazonaws.com
-# If the role has already been successfully created, you will see:
-# An error occurred (InvalidInput) when calling the CreateServiceLinkedRole operation: Service role name AWSServiceRoleForEC2Spot has been taken in this account, please try a different suffix.
-```
+{{% script file="./content/en/preview/getting-started/getting-started-with-eksctl/scripts/step06-add-spot-role.sh" language="bash"%}}
 
 ### Install Karpenter Helm Chart
 
 Use Helm to deploy Karpenter to the cluster.
 
 Before the chart can be installed the repo needs to be added to Helm, run the following commands to add the repo.
 
-{{% script file="./content/en/preview/getting-started/getting-started-with-eksctl/scripts/step06-install-helm-chart.sh" language="bash"%}}
+{{% script file="./content/en/preview/getting-started/getting-started-with-eksctl/scripts/step07-install-helm-chart.sh" language="bash"%}}
 
 Install the chart passing in the cluster details and the Karpenter role ARN.
 
-{{% script file="./content/en/preview/getting-started/getting-started-with-eksctl/scripts/step07-apply-helm-chart.sh" language="bash"%}}
+{{% script file="./content/en/preview/getting-started/getting-started-with-eksctl/scripts/step08-apply-helm-chart.sh" language="bash"%}}
 
 #### Deploy a temporary Prometheus and Grafana stack (optional)
 
 The following commands will deploy a Prometheus and Grafana stack that is suitable for this guide but does not include persistent storage or other configurations that would be necessary for monitoring a production deployment of Karpenter. This deployment includes two Karpenter dashboards that are automatically onboaraded to Grafana. They provide a variety of visualization examples on Karpenter metrices.
 
-```bash
-helm repo add grafana-charts https://grafana.github.io/helm-charts
-helm repo add prometheus-community https://prometheus-community.github.io/helm-charts
-helm repo update
-
-kubectl create namespace monitoring
-
-curl -fsSL https://karpenter.sh{{< relref "." >}}prometheus-values.yaml | tee prometheus-values.yaml
-helm install --namespace monitoring prometheus prometheus-community/prometheus --values prometheus-values.yaml
-
-curl -fsSL https://karpenter.sh{{< relref "." >}}grafana-values.yaml | tee grafana-values.yaml
-helm install --namespace monitoring grafana grafana-charts/grafana --values grafana-values.yaml
-```
+{{% script file="./content/en/preview/getting-started/getting-started-with-eksctl/scripts/step09-add-prometheus-grafana.sh" language="bash"%}}
 
 The Grafana instance may be accessed using port forwarding.
 
-```bash
-kubectl port-forward --namespace monitoring svc/grafana 3000:80
-```
+{{% script file="./content/en/preview/getting-started/getting-started-with-eksctl/scripts/step10-add-grafana-port-forward.sh" language="bash"%}}
 
 The new stack has only one user, `admin`, and the password is stored in a secret. The following command will retrieve the password.
 
-```bash
-kubectl get secret --namespace monitoring grafana -o jsonpath="{.data.admin-password}" | base64 --decode
-```
+{{% script file="./content/en/preview/getting-started/getting-started-with-eksctl/scripts/step11-grafana-get-password.sh" language="bash"%}}
 
 ### Provisioner
 
@@ -155,28 +135,7 @@ Review the [provisioner CRD]({{<ref "../../provisioner.md" >}}) for more informa
 
 Note: This provisioner will create capacity as long as the sum of all created capacity is less than the specified limit.
 
-```bash
-cat <<EOF | kubectl apply -f -
-apiVersion: karpenter.sh/v1alpha5
-kind: Provisioner
-metadata:
-  name: default
-spec:
-  requirements:
-    - key: karpenter.sh/capacity-type
-      operator: In
-      values: ["spot"]
-  limits:
-    resources:
-      cpu: 1000
-  provider:
-    subnetSelector:
-      karpenter.sh/discovery: ${CLUSTER_NAME}
-    securityGroupSelector:
-      karpenter.sh/discovery: ${CLUSTER_NAME}
-  ttlSecondsAfterEmpty: 30
-EOF
-```
+{{% script file="./content/en/preview/getting-started/getting-started-with-eksctl/scripts/step12-add-provisioner.sh" language="bash"%}}
 
 ## First Use
 
@@ -187,43 +146,14 @@ Create some pods using a deployment, and watch Karpenter provision nodes in resp
 
 This deployment uses the [pause image](https://www.ianlewis.org/en/almighty-pause-container) and starts with zero replicas.
 
-```bash
-cat <<EOF | kubectl apply -f -
-apiVersion: apps/v1
-kind: Deployment
-metadata:
-  name: inflate
-spec:
-  replicas: 0
-  selector:
-    matchLabels:
-      app: inflate
-  template:
-    metadata:
-      labels:
-        app: inflate
-    spec:
-      terminationGracePeriodSeconds: 0
-      containers:
-        - name: inflate
-          image: public.ecr.aws/eks-distro/kubernetes/pause:3.2
-          resources:
-            requests:
-              cpu: 1
-EOF
-kubectl scale deployment inflate --replicas 5
-kubectl logs -f -n karpenter -l app.kubernetes.io/name=karpenter -c controller
-```
+{{% script file="./content/en/preview/getting-started/getting-started-with-eksctl/scripts/step13-automatic-node-provisioning.sh" language="bash"%}}
 
 ### Automatic Node Termination
 
 Now, delete the deployment. After 30 seconds (`ttlSecondsAfterEmpty`),
 Karpenter should terminate the now empty nodes.
 
-```bash
-kubectl delete deployment inflate
-kubectl logs -f -n karpenter -l app.kubernetes.io/name=karpenter -c controller
-```
+{{% script file="./content/en/preview/getting-started/getting-started-with-eksctl/scripts/step14-deprovisioning.sh" language="bash"%}}
 
 ### Manual Node Termination
 
@@ -233,21 +163,10 @@ finalizer to the node object, which blocks deletion until all pods are
 drained and the instance is terminated. Keep in mind, this only works for
 nodes provisioned by Karpenter.
 
-```bash
-kubectl delete node $NODE_NAME
-```
+{{% script file="./content/en/preview/getting-started/getting-started-with-eksctl/scripts/step15-delete-node.sh" language="bash"%}}
 
 ## Cleanup
 
 To avoid additional charges, remove the demo infrastructure from your AWS account.
 
-```bash
-helm uninstall karpenter --namespace karpenter
-aws iam delete-role --role-name "${CLUSTER_NAME}-karpenter"
-aws cloudformation delete-stack --stack-name "Karpenter-${CLUSTER_NAME}"
-aws ec2 describe-launch-templates \
-    | jq -r ".LaunchTemplates[].LaunchTemplateName" \
-    | grep -i "Karpenter-${CLUSTER_NAME}" \
-    | xargs -I{} aws ec2 delete-launch-template --launch-template-name {}
-eksctl delete cluster --name "${CLUSTER_NAME}"
-```
+{{% script file="./content/en/preview/getting-started/getting-started-with-eksctl/scripts/step16-cleanup.sh" language="bash"%}}

website/content/en/preview/getting-started/getting-started-with-eksctl/scripts/add-monitoring.sh

@@ -0,0 +1,22 @@
+#!/bin/bash
+set -euo pipefail #fail if one step fails
+
+if [ "$#" -ne 1 ]
+then
+  echo "Missing required Karpenter version. Usage: add-monitoring.sh v0.0.1"
+  exit 1
+fi
+
+export KARPENTER_VERSION=$1
+
+declare -a steps=(
+  step01-config.sh
+  step09-add-prometheus-grafana.sh
+  step10-add-grafana-port-forward.sh
+  step11-grafana-get-password.sh
+)
+
+for step in "${steps[@]}"; do
+  echo "$step"
+  source $step
+done

website/content/en/preview/getting-started/getting-started-with-eksctl/scripts/add-provisioner.sh

@@ -0,0 +1,14 @@
+#!/bin/bash
+set -euo pipefail #fail if one step fails
+
+declare -a steps=(
+  step01-config.sh
+  step12-add-provisioner.sh
+  step13-automatic-node-provisioning.sh
+  step14-automatic-node-termination.sh
+)
+
+for step in "${steps[@]}"; do
+  echo "$step"
+  source $step
+done

website/content/en/preview/getting-started/getting-started-with-eksctl/scripts/cleanup.sh

@@ -0,0 +1,12 @@
+#!/bin/bash
+
+declare -a steps=(
+  step01-config.sh
+  step14-deprovisioning.sh
+  step16-cleanup.sh
+)
+
+for step in "${steps[@]}"; do
+  echo "$step"
+  source $step
+done

website/content/en/preview/getting-started/getting-started-with-eksctl/scripts/run-all-steps.sh → website/content/en/preview/getting-started/getting-started-with-eksctl/scripts/install.sh

@@ -3,7 +3,7 @@ set -euo pipefail #fail if one step fails
 
 if [ "$#" -ne 1 ]
 then
-  echo "Missing required Karpenter version. Usage: run-all-steps.sh v0.0.1"
+  echo "Missing required Karpenter version. Usage: install.sh v0.0.1"
   exit 1
 fi
 
@@ -15,13 +15,12 @@ declare -a steps=(
   step03-iam-cloud-formation.sh
   step04-grant-access.sh
   step05-controller-iam.sh
-  step06-install-helm-chart.sh
-  step07-apply-helm-chart.sh
+  step06-add-spot-role.sh
+  step07-install-helm-chart.sh
+  step08-apply-helm-chart.sh
 )
 
-i=0
 for step in "${steps[@]}"; do
-  ((i += 1))
-  echo "Step $i"
+  echo "$step"
   source $step
 done

website/content/en/preview/getting-started/getting-started-with-eksctl/scripts/step06-add-spot-role.sh

@@ -0,0 +1,3 @@
+aws iam create-service-linked-role --aws-service-name spot.amazonaws.com
+# If the role has already been successfully created, you will see:
+# An error occurred (InvalidInput) when calling the CreateServiceLinkedRole operation: Service role name AWSServiceRoleForEC2Spot has been taken in this account, please try a different suffix.

website/content/en/preview/getting-started/getting-started-with-eksctl/scripts/step09-add-prometheus-grafana.sh

@@ -0,0 +1,11 @@
+helm repo add grafana-charts https://grafana.github.io/helm-charts
+helm repo add prometheus-community https://prometheus-community.github.io/helm-charts
+helm repo update
+
+kubectl create namespace monitoring
+
+curl -fsSL https://karpenter.sh/"${KARPENTER_VERSION}"/getting-started/getting-started-with-eksctl/prometheus-values.yaml | tee prometheus-values.yaml
+helm install --namespace monitoring prometheus prometheus-community/prometheus --values prometheus-values.yaml
+
+curl -fsSL https://karpenter.sh/"${KARPENTER_VERSION}"/getting-started/getting-started-with-eksctl/grafana-values.yaml | tee grafana-values.yaml
+helm install --namespace monitoring grafana grafana-charts/grafana --values grafana-values.yaml

website/content/en/preview/getting-started/getting-started-with-eksctl/scripts/step10-add-grafana-port-forward.sh

@@ -0,0 +1 @@
+kubectl port-forward --namespace monitoring svc/grafana 3000:80

website/content/en/preview/getting-started/getting-started-with-eksctl/scripts/step11-grafana-get-password.sh

@@ -0,0 +1 @@
+kubectl get secret --namespace monitoring grafana -o jsonpath="{.data.admin-password}" | base64 --decode

website/content/en/preview/getting-started/getting-started-with-eksctl/scripts/step12-add-provisioner.sh

@@ -0,0 +1,20 @@
+cat <<EOF | kubectl apply -f -
+apiVersion: karpenter.sh/v1alpha5
+kind: Provisioner
+metadata:
+  name: default
+spec:
+  requirements:
+    - key: karpenter.sh/capacity-type
+      operator: In
+      values: ["spot"]
+  limits:
+    resources:
+      cpu: 1000
+  provider:
+    subnetSelector:
+      karpenter.sh/discovery: ${CLUSTER_NAME}
+    securityGroupSelector:
+      karpenter.sh/discovery: ${CLUSTER_NAME}
+  ttlSecondsAfterEmpty: 30
+EOF

website/content/en/preview/getting-started/getting-started-with-eksctl/scripts/step13-automatic-node-provisioning.sh

@@ -0,0 +1,25 @@
+cat <<EOF | kubectl apply -f -
+apiVersion: apps/v1
+kind: Deployment
+metadata:
+  name: inflate
+spec:
+  replicas: 0
+  selector:
+    matchLabels:
+      app: inflate
+  template:
+    metadata:
+      labels:
+        app: inflate
+    spec:
+      terminationGracePeriodSeconds: 0
+      containers:
+        - name: inflate
+          image: public.ecr.aws/eks-distro/kubernetes/pause:3.2
+          resources:
+            requests:
+              cpu: 1
+EOF
+kubectl scale deployment inflate --replicas 5
+kubectl logs -f -n karpenter -l app.kubernetes.io/name=karpenter -c controller

website/content/en/preview/getting-started/getting-started-with-eksctl/scripts/step14-deprovisioning.sh

@@ -0,0 +1,2 @@
+kubectl delete deployment inflate
+kubectl logs -f -n karpenter -l app.kubernetes.io/name=karpenter -c controller

website/content/en/preview/getting-started/getting-started-with-eksctl/scripts/step15-delete-node.sh

@@ -0,0 +1 @@
+kubectl delete node $NODE_NAME

website/content/en/preview/getting-started/getting-started-with-eksctl/scripts/step16-cleanup.sh

@@ -0,0 +1,8 @@
+helm uninstall karpenter --namespace karpenter
+aws iam delete-role --role-name "${CLUSTER_NAME}-karpenter"
+aws cloudformation delete-stack --stack-name "Karpenter-${CLUSTER_NAME}"
+aws ec2 describe-launch-templates \
+    | jq -r ".LaunchTemplates[].LaunchTemplateName" \
+    | grep -i "Karpenter-${CLUSTER_NAME}" \
+    | xargs -I{} aws ec2 delete-launch-template --launch-template-name {}
+eksctl delete cluster --name "${CLUSTER_NAME}"