From bba1980c6129b8667006f370d2112c94402b6159 Mon Sep 17 00:00:00 2001 From: surajsbharadwaj Date: Fri, 24 Oct 2025 15:23:16 +0200 Subject: [PATCH] docs: remove monitoring host vsi --- solutions/standard-openshift/README.md | 1 - solutions/standard-plus-vsi/README.md | 1 - solutions/standard/README.md | 1 - 3 files changed, 3 deletions(-) diff --git a/solutions/standard-openshift/README.md b/solutions/standard-openshift/README.md index cc2c2a9d..04f58c30 100644 --- a/solutions/standard-openshift/README.md +++ b/solutions/standard-openshift/README.md @@ -4,7 +4,6 @@ This example sets up an OpenShift Cluster on PowerVS following infrastructure: - A **VPC Infrastructure** with the following components: - One VSI for management (jump/bastion) - One VSI for network-services configured as squid proxy (using Ansible Galaxy collection roles [ibm.power_linux_sap collection](https://galaxy.ansible.com/ui/repo/published/ibm/power_linux_sap/). This VSI also acts as central ansible execution node. - - Optional VSI for Monitoring host - Optional [Client to site VPN server](https://cloud.ibm.com/docs/vpc?topic=vpc-vpn-client-to-site-overview) - Optional [IBM Cloud Security and Compliance Center Workload Protection](https://cloud.ibm.com/docs/workload-protection) and SCC Workload Protection agent configuration on the VSIs in the deployment - IBM Cloud Object storage(COS) Virtual Private endpoint gateway(VPE) diff --git a/solutions/standard-plus-vsi/README.md b/solutions/standard-plus-vsi/README.md index e052ba34..f3d76b47 100644 --- a/solutions/standard-plus-vsi/README.md +++ b/solutions/standard-plus-vsi/README.md @@ -4,7 +4,6 @@ This example sets up the following infrastructure: - A **VPC Infrastructure** with the following components: - One VSI for management (jump/bastion) - One VSI for network-services configured as squid proxy, NTP and DNS servers(using Ansible Galaxy collection roles [ibm.power_linux_sap collection](https://galaxy.ansible.com/ui/repo/published/ibm/power_linux_sap/). This VSI also acts as central ansible execution node. - - Optional VSI for Monitoring host - Optional [Client to site VPN server](https://cloud.ibm.com/docs/vpc?topic=vpc-vpn-client-to-site-overview) - Optional [File storage share](https://cloud.ibm.com/docs/vpc?topic=vpc-file-storage-create&interface=ui) - Optional [Network load balancer](https://cloud.ibm.com/docs/vpc?group=network-load-balancer) diff --git a/solutions/standard/README.md b/solutions/standard/README.md index f6a4fde2..a51178b6 100644 --- a/solutions/standard/README.md +++ b/solutions/standard/README.md @@ -4,7 +4,6 @@ This example sets up the following infrastructure: - A **VPC Infrastructure** with the following components: - One VSI for management (jump/bastion) - One VSI for network-services configured as squid proxy, NTP and DNS servers(using Ansible Galaxy collection roles [ibm.power_linux_sap collection](https://galaxy.ansible.com/ui/repo/published/ibm/power_linux_sap/). This VSI also acts as central ansible execution node. - - Optional VSI for Monitoring host - Optional [Client to site VPN server](https://cloud.ibm.com/docs/vpc?topic=vpc-vpn-client-to-site-overview) - Optional [File storage share](https://cloud.ibm.com/docs/vpc?topic=vpc-file-storage-create&interface=ui) - Optional [Network load balancer](https://cloud.ibm.com/docs/vpc?group=network-load-balancer)