Skip to content

Commit d68f9b9

Browse files
Add links to individual sections.
1 parent b17fcc0 commit d68f9b9

File tree

1 file changed

+10
-9
lines changed

1 file changed

+10
-9
lines changed

articles/operator-nexus/concepts-nexus-availability.md

Lines changed: 10 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -15,25 +15,26 @@ When it comes to availability, there are two areas to consider:
1515

1616
- Availability of the Nexus platform itself, including:
1717

18-
- Capacity and Redundancy Planning
18+
- [Capacity and Redundancy Planning](#capacity-and-redundancy-planning)
1919

20-
- Considering Workload Redundancy Requirements
20+
- [Considering Workload Redundancy Requirements](#considering-workload-redundancy-requirements)
2121

22-
- Site Deployment and Connection
22+
- [Site Deployment and Connection](#site-deployment-and-connection)
2323

24-
- Other Networking Considerations for Availability
24+
- [Other Networking Considerations for Availability](#other-networking-considerations-for-availability)
2525

26-
- Identity and Authentication
26+
- [Identity and Authentication](#identity-and-authentication)
2727

28-
- Managing Platform Upgrade
28+
- [Managing Platform Upgrade](#managing-platform-upgrade)
2929

3030
- Availability of the Network Functions (NFs) running on the platform, including:
3131

32-
- Configuration Updates
32+
- [Configuration Updates](#configuration-updates)
3333

34-
- Workload Upgrade
34+
- [Workload Placement](#workload-placement)
35+
36+
- [Workload Upgrade](#workload-upgrade)
3537

36-
- Workload Healing
3738

3839
## Deploy and Configure Nexus for High Availability
3940

0 commit comments

Comments
 (0)