Fixed yaml file links and other broken links (#1188)

* Fixed yaml file links and other broken links

* Made fixes for new v0.5.5 branch

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

@@ -168,10 +168,10 @@ helm repo update
 
 kubectl create namespace monitoring
 
-curl -fsSL https://karpenter.sh/docs/getting-started/prometheus-values.yaml | tee prometheus-values.yaml
+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/docs/getting-started/grafana-values.yaml | tee grafana-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
 ```
 

website/content/en/preview/reinvent.md

@@ -51,4 +51,4 @@ helm upgrade --install karpenter karpenter/karpenter --namespace karpenter \
 ## Next Steps
 If you're a Kubernetes expert, feel free to start exploring how Karpenter works on your own and if you have any questions, one of the AWS speakers will be happy to answer them.
 ​
-If you'd like a guided walkthrough of Karpenter's features and capabilities, you can follow the Karpenter Getting Started guide starting at the ["Provisioner" step](https://karpenter.sh/docs/getting-started/#provisioner). Please don't hesitate to ask your AWS speaker any questions you might have!
+If you'd like a guided walkthrough of Karpenter's features and capabilities, you can follow the Karpenter Getting Started guide starting at the ["Provisioner" step]({{< ref "./getting-started/#provisioner" >}}). Please don't hesitate to ask your AWS speaker any questions you might have!

website/content/en/v0.4.3/concepts/_index.md

@@ -42,7 +42,7 @@ Here are some things to know about the Karpenter provisioner:
 * **Provisioner CR**: Karpenter defines a Custom Resource called a Provisioner to specify provisioning configuration.
 Each provisioner manages a distinct set of nodes, but pods can be scheduled to any provisioner that supports its scheduling constraints.
 A provisioner contains constraints that impact the nodes that can be provisioned and attributes of those nodes (such timers for removing nodes).
-See [Provisioner](../provisioner-crd/) for a description of settings and the [Provisioning](../tasks/provisioning-task/) task for of provisioner examples. 
+See [Provisioner](../provisioner-crd/) for a description of settings.
 
 * **Well-known labels**: The provisioner can use well-known Kubernetes labels to allow pods to request only certain instance types, architectures, operating systems, or other attributes when creating nodes.
 See [Well-Known Labels, Annotations and Taints](https://kubernetes.io/docs/reference/labels-annotations-taints/) for details.
@@ -67,16 +67,11 @@ Karpenter handles all clean-up work needed to properly delete the node.
 * **Empty nodes**: When the last workload pod running on a Karpenter-managed node is gone, the node is annotated with an emptiness timestamp.
 Once that "node empty" time-to-live (`ttlSecondsAfterEmpty`) is reached, finalization is triggered.
 
-For more details on how Karpenter deletes nodes, see [Deleting nodes with Karpenter](../tasks/deprov-nodes/) for details.
-
 ### Upgrading nodes
 
 A straight-forward way to upgrade nodes is to set `ttlSecondsUntilExpired`.
 Nodes will be terminated after a set period of time and will be replaced with newer nodes.
 
-For details on upgrading nodes with Karpenter, see [Upgrading nodes with Karpenter](../deprov-nodes/#expiry) for details.
-
-
 Understanding the following concepts will help you in carrying out the tasks just described.
 
 ### Constraints
@@ -164,4 +159,3 @@ Kubernetes SIG scalability recommends against these features and Karpenter doesn
 Instead, the Karpenter project recommends `topologySpreadConstraints` to reduce blast radius and `nodeSelectors` and `taints` to implement colocation.
 {{% /alert %}}
 
-For more on how, as a developer, you can add constraints to your pod deployment, see [Running pods](../tasks/running-pods/) for details.

website/content/en/v0.4.3/getting-started/_index.md

@@ -102,7 +102,7 @@ First, create the IAM resources using AWS CloudFormation.
 
 ```bash
 TEMPOUT=$(mktemp)
-curl -fsSL https://karpenter.sh/docs/getting-started/cloudformation.yaml > $TEMPOUT \
+curl -fsSL https://karpenter.sh{{< relref "." >}}cloudformation.yaml > $TEMPOUT \
 && aws cloudformation deploy \
   --stack-name Karpenter-${CLUSTER_NAME} \
   --template-file ${TEMPOUT} \
@@ -181,10 +181,10 @@ helm repo update
 
 kubectl create namespace monitoring
 
-curl -fsSL https://karpenter.sh/docs/getting-started/prometheus-values.yaml
+curl -fsSL https://karpenter.sh{{< relref "." >}}prometheus-values.yaml
 helm install --namespace monitoring prometheus prometheus-community/prometheus --values prometheus-values.yaml
 
-curl -fsSL https://karpenter.sh/docs/getting-started/grafana-values.yaml
+curl -fsSL https://karpenter.sh{{< relref "." >}}grafana-values.yaml
 helm install --namespace monitoring grafana grafana-charts/grafana --values grafana-values.yaml
 ```
 

website/content/en/v0.5.0/getting-started/_index.md

@@ -102,7 +102,7 @@ First, create the IAM resources using AWS CloudFormation.
 
 ```bash
 TEMPOUT=$(mktemp)
-curl -fsSL https://karpenter.sh/docs/getting-started/cloudformation.yaml > $TEMPOUT \
+curl -fsSL https://karpenter.sh{{< relref "." >}}cloudformation.yaml > $TEMPOUT \
 && aws cloudformation deploy \
   --stack-name Karpenter-${CLUSTER_NAME} \
   --template-file ${TEMPOUT} \

website/content/en/v0.5.2/getting-started/_index.md

@@ -102,7 +102,7 @@ First, create the IAM resources using AWS CloudFormation.
 
 ```bash
 TEMPOUT=$(mktemp)
-curl -fsSL https://karpenter.sh/docs/getting-started/cloudformation.yaml > $TEMPOUT \
+curl -fsSL https://karpenter.sh{{< relref "." >}}cloudformation.yaml > $TEMPOUT \
 && aws cloudformation deploy \
   --stack-name Karpenter-${CLUSTER_NAME} \
   --template-file ${TEMPOUT} \

website/content/en/v0.5.3/getting-started/_index.md

@@ -180,10 +180,10 @@ helm repo update
 
 kubectl create namespace monitoring
 
-curl -fsSL https://karpenter.sh/docs/getting-started/prometheus-values.yaml | tee prometheus-values.yaml
+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/docs/getting-started/grafana-values.yaml | tee grafana-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
 ```
 

website/content/en/v0.5.5/getting-started/_index.md

@@ -168,10 +168,10 @@ helm repo update
 
 kubectl create namespace monitoring
 
-curl -fsSL https://karpenter.sh/docs/getting-started/prometheus-values.yaml | tee prometheus-values.yaml
+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/docs/getting-started/grafana-values.yaml | tee grafana-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
 ```
 

website/content/en/v0.5.5/reinvent.md

@@ -51,4 +51,4 @@ helm upgrade --install karpenter karpenter/karpenter --namespace karpenter \
 ## Next Steps
 If you're a Kubernetes expert, feel free to start exploring how Karpenter works on your own and if you have any questions, one of the AWS speakers will be happy to answer them.
 ​
-If you'd like a guided walkthrough of Karpenter's features and capabilities, you can follow the Karpenter Getting Started guide starting at the ["Provisioner" step](https://karpenter.sh/docs/getting-started/#provisioner). Please don't hesitate to ask your AWS speaker any questions you might have!
+If you'd like a guided walkthrough of Karpenter's features and capabilities, you can follow the Karpenter Getting Started guide starting at the ["Provisioner" step]({{< ref "./getting-started/#provisioner" >}}). Please don't hesitate to ask your AWS speaker any questions you might have!