From 83ba6762cc43d9db581b979bb5e3445669e46cc2 Mon Sep 17 00:00:00 2001
From: Daniel Baumann <daniel.baumann@progress-linux.org>
Date: Mon, 25 Nov 2024 18:33:56 +0100
Subject: Merging upstream version 2.0.3+dfsg (Closes: #923993, #1042533,
 #1045145).

Signed-off-by: Daniel Baumann <daniel.baumann@progress-linux.org>
---
 packaging/installer/methods/gcp.md | 24 ++++++------------------
 1 file changed, 6 insertions(+), 18 deletions(-)

(limited to 'packaging/installer/methods/gcp.md')

diff --git a/packaging/installer/methods/gcp.md b/packaging/installer/methods/gcp.md
index 5003decb4..59e293690 100644
--- a/packaging/installer/methods/gcp.md
+++ b/packaging/installer/methods/gcp.md
@@ -1,13 +1,3 @@
-<!--
-title: "Install Netdata on GCP"
-description: "The Netdata Agent runs on all popular cloud providers, but often requires additional steps and configuration for full functionality."
-custom_edit_url: https://github.com/netdata/netdata/edit/master/packaging/installer/methods/gcp.md
-sidebar_label: "GCP"
-learn_status: "Published"
-learn_topic_type: "Tasks"
-learn_rel_path: "Installation/Install on specific environments"
--->
-
 # Install Netdata on GCP
 
 Netdata is fully compatible with the Google Cloud Platform (GCP).
@@ -42,12 +32,11 @@ command from a remote system, and it fails, it's likely that a firewall is block
 Another option is to put Netdata behind web server, which will proxy requests through standard HTTP/HTTPS ports
 (80/443), which are likely already open on your instance. We have a number of guides available:
 
--   [Apache](/docs/netdata-agent/configuration/running-the-netdata-agent-behind-a-reverse-proxy/Running-behind-apache.md)
--   [Nginx](/docs/netdata-agent/configuration/running-the-netdata-agent-behind-a-reverse-proxy/Running-behind-nginx.md)
--   [Caddy](/docs/netdata-agent/configuration/running-the-netdata-agent-behind-a-reverse-proxy/Running-behind-caddy.md)
--   [HAProxy](/docs/netdata-agent/configuration/running-the-netdata-agent-behind-a-reverse-proxy/Running-behind-haproxy.md)
--   [lighttpd](/docs/netdata-agent/configuration/running-the-netdata-agent-behind-a-reverse-proxy/Running-behind-lighttpd.md)
-
+- [Apache](/docs/netdata-agent/configuration/running-the-netdata-agent-behind-a-reverse-proxy/Running-behind-apache.md)
+- [Nginx](/docs/netdata-agent/configuration/running-the-netdata-agent-behind-a-reverse-proxy/Running-behind-nginx.md)
+- [Caddy](/docs/netdata-agent/configuration/running-the-netdata-agent-behind-a-reverse-proxy/Running-behind-caddy.md)
+- [HAProxy](/docs/netdata-agent/configuration/running-the-netdata-agent-behind-a-reverse-proxy/Running-behind-haproxy.md)
+- [lighttpd](/docs/netdata-agent/configuration/running-the-netdata-agent-behind-a-reverse-proxy/Running-behind-lighttpd.md)
 
 To add a firewall rule, go to the [Firewall rules page](https://console.cloud.google.com/networking/firewalls/list) and
 click **Create firewall rule**.
@@ -55,7 +44,7 @@ click **Create firewall rule**.
 The following configuration has previously worked for Netdata running on GCP instances
 ([see #7786](https://github.com/netdata/netdata/issues/7786)):
 
-```conf
+```text
 Name: <name>
 Type: Ingress
 Targets: <name-tag>
@@ -67,4 +56,3 @@ Priority: 1000
 
 Read GCP's [firewall documentation](https://cloud.google.com/vpc/docs/using-firewalls) for specific instructions on how
 to create a new firewall rule.
-
-- 
cgit v1.2.3