|
23 | 23 | - Action: Includes the `jump-server` role. |
24 | 24 | - Condition: Runs only if all of these are defined: `JUMP_SVR_HOST`, `JUMP_SVR_USER`, `JUMP_SVR_PRIVATE_KEY`, `V4_CFG_MANAGE_STORAGE` and if `V4_CFG_MANAGE_STORAGE` is `true`. |
25 | 25 | - Tags: `viya` |
26 | | - - **Networking Considerations:** May require SSH access to the jump server and NFS server. See [networking-considerations.md](../docs/networking-considerations.md) |
| 26 | + - **Networking Considerations:** May require SSH access to the jump server and NFS server. See [NetworkingConsiderations.md](../docs/user/NetworkingConsiderations.md) |
27 | 27 | 5. **Optionally Include Baseline Role for Install** |
28 | 28 |
|
29 | 29 | - Task: `baseline role install` |
30 | 30 | - Action: Includes the `baseline` role for install actions. |
31 | 31 | - Condition: Runs only if both `'baseline'` and `'install'` are in `ansible_run_tags`. |
32 | 32 | - Tags: `baseline` |
33 | | - - **Networking Considerations:** Deploys core components (ingress-nginx, cert-manager, metrics-server, csi-driver-nfs, ebs-csi-driver, etc.) that impact cluster networking, ingress, and storage. See [networking-considerations.md](../docs/networking-considerations.md) |
| 33 | + - **Networking Considerations:** Deploys core components (ingress-nginx, cert-manager, metrics-server, csi-driver-nfs, ebs-csi-driver, etc.) that impact cluster networking, ingress, and storage. See [NetworkingConsiderations.md](../docs/user/NetworkingConsiderations.md) |
34 | 34 | 6. **Optionally Include Multi-Tenancy Role** |
35 | 35 |
|
36 | 36 | - Task: `Multi-tenancy role` |
37 | 37 | - Action: Includes the `multi-tenancy` role. |
38 | 38 | - Condition: Runs only if `V4MT_ENABLE` is defined. |
39 | 39 | - Tags: `multi-tenancy` |
40 | | - - **Networking Considerations:** May create namespaces and network policies. See [networking-considerations.md](../docs/networking-considerations.md) |
| 40 | + - **Networking Considerations:** May create namespaces and network policies. See [NetworkingConsiderations.md](../docs/user/NetworkingConsiderations.md) |
41 | 41 | 7. **Include VDM Role** |
42 | 42 |
|
43 | 43 | - Task: `vdm role` |
|
50 | 50 | - Action: Includes the `baseline` role for uninstall actions. |
51 | 51 | - Condition: Runs only if both `'baseline'` and `'uninstall'` are in `ansible_run_tags`. |
52 | 52 | - Tags: `baseline` |
53 | | - - **Networking Considerations:** Removes core components and may affect networking and storage resources. See [networking-considerations.md](../docs/networking-considerations.md) |
| 53 | + - **Networking Considerations:** Removes core components and may affect networking and storage resources. See [NetworkingConsiderations.md](../docs/user/NetworkingConsiderations.md) |
54 | 54 | 9. **Delete Temporary Directory** |
55 | 55 |
|
56 | 56 | - Task: `Delete tmpdir` |
|
61 | 61 | - Tasks are executed in the order listed above. |
62 | 62 | - Some tasks/roles are conditionally included based on variables or tags. |
63 | 63 | - The playbook is designed to be flexible for different deployment scenarios by using tags and conditions. |
64 | | -- For a detailed summary of networking considerations, see [networking-considerations.md](../docs/networking-impact.md) |
| 64 | +- For a detailed summary of networking considerations, see [NetworkingConsiderations.md](../docs/user/NetworkingConsiderations.md) |
0 commit comments