fmt code

03-master.tf

@@ -1,4 +1,3 @@
-# Create virtual Server
 resource "stackit_server" "example01" {
   project_id = var.stackit_project_id
   name       = "example01"

04-backup.tf

@@ -1,4 +1,3 @@
-# Create virtual Server
 resource "stackit_server" "example02" {
   project_id = var.stackit_project_id
   name       = "example02"

05-ha.tf

@@ -4,10 +4,6 @@ resource "stackit_network_interface" "vip01" {
   security   = false
 }
 
-locals {
-  x = stackit_network_interface.vip01.ipv4
-}
-
 resource "stackit_public_ip" "vip01-wan" {
   project_id           = var.stackit_project_id
   network_interface_id = stackit_network_interface.vip01.network_interface_id

README.md

@@ -1,20 +1,16 @@
 # Basic High Availability (HA) Setup Using VRRP
 
-This guide provides a comprehensive, step-by-step process for setting up a Basic High Availability (HA) cluster using the Virtual Router Redundancy Protocol (VRRP) with the STACKIT CLI. In this HA configuration, one virtual machine (VM) functions as the active primary node while the secondary remains on standby, ready to take over in the event of a failure.
+This guide provides a comprehensive, step-by-step process for setting up a Basic High Availability (HA) 
+cluster using the Virtual Router Redundancy Protocol (VRRP) with the STACKIT CLI. 
+In this HA configuration, one virtual machine (VM) functions as the active primary node while the secondary 
+remains on standby.
 
 > For setup instructions using the STACKIT CLI instead of Terraform, please refer to the [STACKIT CLI Guide](STACKIT-CLI-GUIDE.md).
 
-## Overview of Core Components
-
-- **Active/Passive VM Configuration**: Ensures redundancy, with one active node and a standby failover node.
-- **VRRP Synchronization**: Maintains state information between nodes, enabling seamless failover.
-- **Security Group Rules**: Configured to allow VRRP and ICMP traffic.
-- **Virtual IP (vIP)**: A dedicated internal IP address bound to a shared network interface card (NIC) port for seamless failover.
-- **Public IP Binding**: Enables external access to the HA endpoint.
-
 ## Testing the Setup
 
-After completing the setup, use the [test-setup.sh](test-setup.sh) script to verify that the Apache server is operational on each machine. Executing this script should yield the following results:
+After completing the setup, use the [test-setup.sh](test-setup.sh) script to verify that the Apache server is operational 
+on each machine. Executing this script should yield the following results:
 
 ```bash
 Performing curl on IP: 193.148.177.243
@@ -40,8 +36,7 @@ curl $vip01_wan_ip
 <center><h1>example02</h1>
 ```
 
-The response confirms that the failover from the master to the backup has occurred
-successfully, demonstrating the effectiveness of the HA setup.
+The response confirms that the fail-over from the master to the backup has occurred.
 
 ## Diagrams