From 5f5ad985ade167f8b113b2df721ff8b2084fa02d Mon Sep 17 00:00:00 2001 From: Robert Parker Date: Thu, 23 Jan 2020 13:33:34 -0800 Subject: [PATCH] remove alias so the the response is 200 not 304 --- .../rke-clusters/custom-nodes/agent-options/_index.md | 1 - .../cluster-provisioning/rke-clusters/rancher-agents/_index.md | 2 -- 2 files changed, 3 deletions(-) diff --git a/content/rancher/v2.x/en/cluster-provisioning/rke-clusters/custom-nodes/agent-options/_index.md b/content/rancher/v2.x/en/cluster-provisioning/rke-clusters/custom-nodes/agent-options/_index.md index 58fc18c181d..241369bc24d 100644 --- a/content/rancher/v2.x/en/cluster-provisioning/rke-clusters/custom-nodes/agent-options/_index.md +++ b/content/rancher/v2.x/en/cluster-provisioning/rke-clusters/custom-nodes/agent-options/_index.md @@ -4,7 +4,6 @@ weight: 2500 aliases: - /rancher/v2.x/en/admin-settings/agent-options/ - /rancher/v2.x/en/cluster-provisioning/custom-clusters/agent-options - - /rancher/v2.x/en/cluster-provisioning/rke-clusters/agent-options --- Rancher deploys an agent on each node to communicate with the node. This pages describes the options that can be passed to the agent. To use these options, you will need to [create a cluster with custom nodes]({{}}/rancher/v2.x/en/cluster-provisioning/rke-clusters/custom-nodes/) and add the options to the generated `docker run` command when adding a node. diff --git a/content/rancher/v2.x/en/cluster-provisioning/rke-clusters/rancher-agents/_index.md b/content/rancher/v2.x/en/cluster-provisioning/rke-clusters/rancher-agents/_index.md index 2e3b1e0678a..de3e9ba5058 100644 --- a/content/rancher/v2.x/en/cluster-provisioning/rke-clusters/rancher-agents/_index.md +++ b/content/rancher/v2.x/en/cluster-provisioning/rke-clusters/rancher-agents/_index.md @@ -1,8 +1,6 @@ --- title: Rancher Agents weight: 2400 -aliases: - - /rancher/v2.x/en/cluster-provisioning/rancher-agents --- There are two different agent resources deployed on Rancher managed clusters: