Skip to content

Commit aa7a26b

Browse files
committed
Added lightbox
1 parent ee84276 commit aa7a26b

File tree

1 file changed

+5
-5
lines changed

1 file changed

+5
-5
lines changed

articles/operator-nexus/concepts-nexus-kubernetes-placement.md

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -67,7 +67,7 @@ when creating NKS Clusters against an Operator Nexus environment.
6767
> KubernetesCluster resource or viewing the "Host" column in Azure Portal's
6868
> display of Kubernetes Cluster Nodes.
6969
70-
:::image type="content" source="media/nexus-kubernetes/show-baremetal-host.png" alt-text="A screenshot showing bare metal server for NKS VMs.":::
70+
:::image type="content" source="media/nexus-kubernetes/show-baremetal-host.png" lightbox="media/nexus-kubernetes/show-baremetal-host.png" alt-text="A screenshot showing bare metal server for NKS VMs.":::
7171

7272
The example Operator Nexus environment has these specifications:
7373

@@ -77,7 +77,7 @@ The example Operator Nexus environment has these specifications:
7777

7878
[numa]: https://en.wikipedia.org/wiki/Non-uniform_memory_access
7979

80-
### Empty Environment
80+
### Empty Environment
8181

8282
Given an empty Operator Nexus environment with the given capacity, we create
8383
three differently sized Nexus Kubernetes Clusters.
@@ -130,7 +130,7 @@ on the same bare metal servers (see rule #3 in
130130
Here's a visualization of a layout the user might see after deploying Clusters
131131
A, B, and C into an empty environment.
132132

133-
:::image type="content" source="media/nexus-kubernetes/after-first-deployment.png" alt-text="Diagram showing possible layout of VMs after first deployment.":::
133+
:::image type="content" source="media/nexus-kubernetes/after-first-deployment.png" lightbox="media/nexus-kubernetes/after-first-deployment.png" alt-text="Diagram showing possible layout of VMs after first deployment.":::
134134

135135
### Half-full Environment
136136

@@ -176,7 +176,7 @@ and Agent Pool #2 are collocated on the same bare metal servers in racks 7 and
176176
Here's a visualization of a layout the user might see after deploying Cluster
177177
D into the target environment.
178178

179-
:::image type="content" source="media/nexus-kubernetes/after-second-deployment.png" alt-text="Diagram showing possible layout of VMs after second deployment.":::
179+
:::image type="content" source="media/nexus-kubernetes/after-second-deployment.png" lightbox="media/nexus-kubernetes/after-second-deployment.png" alt-text="Diagram showing possible layout of VMs after second deployment.":::
180180

181181
### Nearly full Environment
182182

@@ -207,7 +207,7 @@ racks were racks 3 and 6.
207207
Here's a visualization of a layout the user might see after deploying Cluster
208208
E into the target environment.
209209

210-
:::image type="content" source="media/nexus-kubernetes/after-third-deployment.png" alt-text="Diagram showing possible layout of VMs after third deployment.":::
210+
:::image type="content" source="media/nexus-kubernetes/after-third-deployment.png" lightbox="media/nexus-kubernetes/after-third-deployment.png" alt-text="Diagram showing possible layout of VMs after third deployment.":::
211211

212212
## Placement during a Runtime Upgrade
213213

0 commit comments

Comments
 (0)