CL Node release 2.8.0

src/config/sidebar.ts

@@ -1032,10 +1032,6 @@ export const SIDEBAR: Partial<Record<Sections, SectionEntry[]>> = {
               title: "Secrets Config (TOML)",
               url: "chainlink-nodes/v1/secrets-config",
             },
-            {
-              title: "Legacy Config (.env)",
-              url: "chainlink-nodes/v1/configuration",
-            },
           ],
         },
         {
@@ -1083,10 +1079,6 @@ export const SIDEBAR: Partial<Record<Sections, SectionEntry[]>> = {
           title: "Security and Operation Best Practices",
           url: "chainlink-nodes/resources/best-security-practices",
         },
-        {
-          title: "Best Practices for Nodes on AWS",
-          url: "chainlink-nodes/resources/best-practices-aws",
-        },
         { title: "Miscellaneous", url: "chainlink-nodes/resources/miscellaneous" },
       ],
     },

src/content/chainlink-nodes/external-initiators/external-initiators-in-nodes.mdx

@@ -8,7 +8,7 @@ import { Aside } from "@components"
 
 <Aside type="note">
   External initiators are disabled on nodes by default. Set the `FEATURE_EXTERNAL_INITIATORS=true` [configuration
-  variable](/chainlink-nodes/v1/configuration/#feature_external_initiators) to enable this feature.
+  variable](/chainlink-nodes/v1/configuration) to enable this feature.
 </Aside>
 
 ## Creating an external initiator

src/content/chainlink-nodes/external-initiators/external-initiators-introduction.mdx

@@ -20,7 +20,7 @@ External initiators allow jobs in a node to be initiated depending on some exter
 
 <Aside type="note">
   External initiators are disabled on nodes by default. Set the `FEATURE_EXTERNAL_INITIATORS=true` [configuration
-  variable](/chainlink-nodes/v1/configuration/#feature_external_initiators) to enable this feature.
+  variable](/chainlink-nodes/v1/configuration) to enable this feature.
 </Aside>
 
 Initiator Bridges handle the authentication to and from the External Initiator and where to send the messages. When creating a Bridge two parameters are required:

src/content/chainlink-nodes/resources/best-security-practices.mdx

@@ -58,7 +58,7 @@ To be proactive in detecting any issues before or when they occur, active monito
 - Ethereum client disk, RAM and CPU usage.
 
 Monitoring can be set up from the Docker container's output and fed into most major logging providers. For example, you can use Docker's docs to set up the logging driver for [Amazon CloudWatch](https://docs.docker.com/config/containers/logging/awslogs/) and [Google Cloud Logging](https://docs.docker.com/config/containers/logging/gcplogs/). You will want to set the [
-JSON_CONSOLE](/chainlink-nodes/v1/configuration/#json_console) configuration variable to `true` so that the output of the container is JSON-formatted for logging.
+JSON_CONSOLE](/chainlink-nodes/v1/configuration) configuration variable to `true` so that the output of the container is JSON-formatted for logging.
 
 ## Frequent Updates
 
@@ -77,10 +77,10 @@ The following are suggestions for job specifications and configuration settings
 
 [Configuring Chainlink Nodes](/chainlink-nodes/v1/configuration):
 
-- [MINIMUM_CONTRACT_PAYMENT_LINK_JUELS](/chainlink-nodes/v1/configuration/#minimum_contract_payment_link_juels): ensure your required payment amount is high enough to meet the costs of responding onchain.
-- [MIN_INCOMING_CONFIRMATIONS](/chainlink-nodes/v1/configuration/#min_incoming_confirmations): this can be set to 0 for common data request jobs. See the bullet above on setting individual `confirmations` for specific jobs.
-- [LOG_FILE_MAX_SIZE](/chainlink-nodes/v1/configuration/#log_file_max_size): Set this to `0` if you're using external log drivers which parse the output from Docker containers. This will save you disk space.
-- [JSON_CONSOLE](/chainlink-nodes/v1/configuration/#json_console): Set to `true` if you're using external log drivers to parse the output of Docker containers. This will make it easier to parse individual fields of the log and set up alerts.
+- [MINIMUM_CONTRACT_PAYMENT_LINK_JUELS](/chainlink-nodes/v1/configuration): ensure your required payment amount is high enough to meet the costs of responding onchain.
+- [MIN_INCOMING_CONFIRMATIONS](/chainlink-nodes/v1/configuration): this can be set to 0 for common data request jobs. See the bullet above on setting individual `confirmations` for specific jobs.
+- [LOG_FILE_MAX_SIZE](/chainlink-nodes/v1/configuration): Set this to `0` if you're using external log drivers which parse the output from Docker containers. This will save you disk space.
+- [JSON_CONSOLE](/chainlink-nodes/v1/configuration): Set to `true` if you're using external log drivers to parse the output of Docker containers. This will make it easier to parse individual fields of the log and set up alerts.
 
 ## Addresses
 

src/content/chainlink-nodes/resources/evm-performance-configuration.mdx

@@ -40,7 +40,7 @@ You can configure as many send-only nodes as you want. Send-only nodes only broa
   URL for a send-only node as an existing primary node, and it has no effect.
 </Aside>
 
-Here is an example for how to specify the [`EVM_NODES` environment variable](/chainlink-nodes/v1/configuration/#evm_nodes):
+Here is an example for how to specify the [`EVM_NODES` environment variable](/chainlink-nodes/v1/configuration):
 
 ```shell
 export EVM_NODES='
@@ -98,9 +98,9 @@ NODE_POLL_FAILURE_THRESHOLD=0
 NODE_POLL_INTERVAL=0
 ```
 
-- [NODE_NO_NEW_HEADS_THRESHOLD](/chainlink-nodes/v1/configuration/#node_no_new_heads_threshold): Controls how long to wait receiving no new heads before marking a node dead
-- [NODE_POLL_FAILURE_THRESHOLD](/chainlink-nodes/v1/configuration/#node_poll_failure_threshold): Controls how many consecutive poll failures will disable a node
-- [NODE_POLL_INTERVAL](/chainlink-nodes/v1/configuration/#node_poll_interval): Controls how often the node will be polled
+- [NODE_NO_NEW_HEADS_THRESHOLD](/chainlink-nodes/v1/configuration): Controls how long to wait receiving no new heads before marking a node dead
+- [NODE_POLL_FAILURE_THRESHOLD](/chainlink-nodes/v1/configuration): Controls how many consecutive poll failures will disable a node
+- [NODE_POLL_INTERVAL](/chainlink-nodes/v1/configuration): Controls how often the node will be polled
 
 By default, these environment variables use the following values:
 
@@ -120,9 +120,9 @@ It is not recommended to configure primary nodes with _only_ a websocket URL. Ro
 
 If you enabled HTTP URLs on all your primary nodes, you can increase the values for the following environment variables:
 
-- [ETH_RPC_DEFAULT_BATCH_SIZE](/chainlink-nodes/v1/configuration/#eth_rpc_default_batch_size)
-- [BLOCK_HISTORY_ESTIMATOR_BATCH_SIZE](/chainlink-nodes/v1/configuration/#block_history_estimator_batch_size)
-- [ETH_LOG_BACKFILL_BATCH_SIZE](/chainlink-nodes/v1/configuration/#eth_log_backfill_batch_size)
+- [ETH_RPC_DEFAULT_BATCH_SIZE](/chainlink-nodes/v1/configuration)
+- [BLOCK_HISTORY_ESTIMATOR_BATCH_SIZE](/chainlink-nodes/v1/configuration)
+- [ETH_LOG_BACKFILL_BATCH_SIZE](/chainlink-nodes/v1/configuration)
 
 By default, these config variables are set conservatively to avoid overflowing websocket frames. In HTTP mode, there are no such limitations. You might be able to improve performance with increased values similar to the following example: