Skip to content

Commit

Permalink
Update README.md
Browse files Browse the repository at this point in the history
Fix comments from Viktor
Add Note for external_fdqn
  • Loading branch information
kristianiliev1 authored Oct 29, 2024
1 parent 396a1c8 commit 19334ec
Showing 1 changed file with 7 additions and 8 deletions.
15 changes: 7 additions & 8 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -389,27 +389,26 @@ graphdb_external_address_fqdn = "your-fqdn-or-ip"
```

_Notes_:
- Setting disable_agw to true allows you to use your existing Application Gateway.
- The context_path variable sets the custom context path for your application.
- The context_path variable only works when disable_agw is true!
- Setting `disable_agw` to true allows you to use your existing Application Gateway.
- When using `disable_agw` you need to set `graphdb_external_adress_fqdn` as well.
- The `context_path` variable sets the custom context path for your application.

**_Post-Deployment Actions_**:
After applying the Terraform code, you must perform the following steps:

**1.** Configure the Application Gateway:
- Path-Based Routing Rule: Set up a path-based routing rule on your Application Gateway to listen to the same context path. For example, if ```hcl context_path = "/graphdb"```, the path-based rule should be ```hcl/graphdb/*```.
- Path-Based Routing Rule: Set up a path-based routing rule on your Application Gateway to listen to the same context path. For example, if `context_path = "/graphdb"`, the path-based rule should be `/graphdb/*`.

_Note_:
- You can use your External Application Gateway without the context path.

**2.** Add VMs or VMSS to Backend Pool:
- Manually add your Virtual Machines (VMs) or Virtual Machine Scale Sets (VMSS) to the Application Gateway’s backend pool as targets.
- Manually add your Virtual Machine Scale Sets (VMSS) to the Application Gateway’s backend pool as targets.

**3.** Upgrade VM Instances:
- After adding the VMSS to the backend pool and ensuring the Application Gateway has access to the VMSS, upgrade your VM instances to the latest model/version. This step is crucial for the Application Gateway to recognize them as valid targets in the backend pool.

- After assigning the VMSS to the backend pool and verifying that the Application Gateway can access the VMSS, upgrade your VM instances to the latest model or version. This is essential for the Application Gateway to identify them as valid targets within the backend pool.
**4.** Network Security Group (NSG) Configuration:
- Ensure that the Application Gateway has the necesery access to the VMSS by configuring NSG rules to allow traffic between them.
- Configure NSG rules to allow traffic between the Application Gateway and the VMSS, ensuring the necessary access is in place.

## Local Development

Expand Down

0 comments on commit 19334ec

Please sign in to comment.