Merge branch 'main' into mda-pw-test

Author: MariadeAnton

site/content/docs/alerting-and-retries/retries.md

@@ -69,7 +69,7 @@ There are some tradeoffs to consider:
 
 ### Network retries
 
-For API checks, you can enable network retries to automatically retry a check run only if it fails due to a network error—such as a timeout, DNS resolution issue, or connection reset.
+For API checks & URL monitors, you can enable network retries to automatically retry a check run only if it fails due to a network error—such as a timeout, DNS resolution issue, or connection reset.
 
 When network retries are enabled:
 * The check will retry on: ECONNRESET, ENOTFOUND, ETIMEDOUT, EAI_AGAIN, ECONNREFUSED, and similar network errors.

site/content/docs/cli/constructs-reference.md

@@ -1041,6 +1041,7 @@ For all of the methods above, the `options` argument can be used to customize th
 - `maxRetries`: The maximum number of times to retry the check. This value should be between 1 and 10. Defaults to 2.
 - `maxDurationSeconds`: The maximum amount of time to continue retrying the check. Maximum 600 seconds. Defaults to 600 seconds.
 - `sameRegion`: Whether retries should be run in the same region as the initial failed check run. Defaults to `true`.
+- `onlyOn`: Limits retries to specific failure types. Currently supports 'NETWORK_ERROR' only, and is only applicable to API checks and URL monitors. See [Network retries](/docs/alerting-and-retries/retries/#network-retries) for more information.
 
 ## `AlertEscalationPolicy`
 

site/content/docs/monitoring/global-locations.md

@@ -9,8 +9,6 @@ menu:
 ---
 You can configure your run checks to run from an ever growing amount of global locations. Leveraging global infrastructure allows us to measure what the user experience is in different parts of the world.
 
-We use [Amazon Web Services](https://aws.amazon.com) to host our check runner infrastructure and follow the opening of new datacenter locations as close a possible, i.e. if  a new location opens up, Checkly will be there very soon.
-
 Current locations in Checkly are
 
 | Americas                     | Europe/Middle East/Africa | Asia Pacific               |

site/content/docs/private-locations/running-on-kubernetes.md

@@ -9,58 +9,16 @@ menu:
 
 ---
 
-We advise running any production-grade Checkly Agent deployments on a container orchestrator like Kubernetes. To help you get started, we created the [checkly-k8s repo](https://github.com/checkly/checkly-k8s) which contains a Helm chart and a few example Kubernetes manifests.
+We advise running any production-grade Checkly Agent deployments on a container orchestrator like Kubernetes. To help you get started, we provide a [public Helm chart](https://github.com/checkly/helm-charts) for deploying the agent.
 
 ## Prerequisites
 
-- You've [created a Private Location](/docs/private-locations/) and have an API key.
-- A running Kubernetes cluster
-- [Helm](https://helm.sh/) if you are using Helm charts.
+- You've [created a Private Location](/docs/private-locations/) and have an API key
+- You have a running Kubernetes cluster
+- [Helm](https://helm.sh/) is installed
 
-Now, clone the repo with the examples:
+## Deploying the Checkly Agent with Helm
 
-```bash
-git clone https://github.com/checkly/checkly-k8s.git
-cd checkly-k8
-```
+See the [Checkly Helm Charts README](https://github.com/checkly/helm-charts/tree/main/charts/agent#readme) for installation instructions and configuration options.
 
-## Helm chart
-
-Find the Helm chart in the `/helm-chart` directory. The Helm chart does two basic things:
-- Creates a secret for the API key.
-- Spins up two pods running the Checkly Agent
-
-Assuming you have Helm set up to point at your K8S cluster, run it with the following command, making sure you
-**replace the `apiKeySecret.apikey="pl_..."` with your Checkly Private Location API key**.
-
-```bash
-helm install checkly-agent --set apiKeySecret.apiKey="pl_..."  ./helm-chart
-```
-
-## Kubernetes manifests
-
-If you are not using Helm, you can also use K8S manifest files to create your preferred cluster setup for the Checkly
-Agent. Here is a rundown of the manifest files you can find in the repo:
-
-### [agentSecret.yaml](https://github.com/checkly/checkly-k8s/blob/main/k8s-manifests/agent-secret.yaml)
-
-Creates a secret containing the API key your agents use to connect to the private location. The pod and deployment manifests are configured
-to use this secret.
-
-### [agentPod.yaml](https://github.com/checkly/checkly-k8s/blob/main/k8s-manifests/agent-pod.yaml)
-
-Creates a single pod running the Checkly agent. Connects to the Private Location using the API key specified in
-[agentSecret.yaml](https://github.com/checkly/checkly-k8s/blob/main/k8s-manifests/agent-secret.yaml). Uses the
-[latest image](https://hub.docker.com/r/checkly/agent/tags).
-
-This is a quick way to test the Checkly Agent on your cluster. Be aware, if the container exits, it will not automatically restarted.
-
-### [agentDeployment.yaml](https://github.com/checkly/checkly-k8s/blob/main/k8s-manifests/agent-deployment.yaml)
-
-Create a deployment of Checkly agent pods (default: 2). Connects to the private location using the API key specified in
-[agentSecret.yaml](https://github.com/checkly/checkly-k8s/blob/main/k8s-manifests/agent-secret.yaml)). Uses the
-[latest image](https://hub.docker.com/r/checkly/agent/tags). Rolling updates are enabled.
-
-### [checklyNamespace.yaml](https://github.com/checkly/checkly-k8s/blob/main/k8s-manifests/checkly-namespace.yaml)
-
-Optional but recommended - Creates a namespace for the Checkly agent resources. Make sure to have NetworkPolicies in place to your other namespaces.
+If you run into any issues, feel free to open an issue on the repository or reach out via the [Community Slack](https://join.slack.com/t/checklycommunity/shared_invite/zt-2qc51mpyr-5idwVD4R4izkf5FC4CFk1A).

site/content/docs/url-monitors/_index.md

@@ -58,7 +58,6 @@ new UrlMonitor('hello-url-1', {
   name: 'Hello URL',
   activated: true,
   request: {
-    method: 'GET',
     url: 'https://api.checklyhq.com/v1/echo/get',
     assertions: [
       UrlAssertionBuilder.statusCode().equals(200),
@@ -77,7 +76,6 @@ new UrlMonitor('hello-url-1', {
   name: 'Hello URL',
   activated: true,
   request: {
-    method: 'GET',
     url: 'https://api.checklyhq.com/v1/echo/get',
     assertions: [
       UrlAssertionBuilder.statusCode().equals(200),