Skip to content

Commit 5f98cf6

Browse files
authored
Update runtime-classes.mdx
1 parent 9bb678d commit 5f98cf6

File tree

1 file changed

+4
-4
lines changed

1 file changed

+4
-4
lines changed

vcluster/configure/vcluster-yaml/sync/from-host/runtime-classes.mdx

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -99,7 +99,7 @@ When vCluster removes a synced RuntimeClass from the virtual cluster due to sele
9999

100100
To sync only RuntimeClass resources labeled `environment: development`:
101101

102-
```yaml
102+
```yaml title="Filter example runtimeClass"
103103
sync:
104104
toHost:
105105
pods:
@@ -116,7 +116,7 @@ sync:
116116

117117
To sync RuntimeClass resources where the label `kubernetes.io/runtime.class` is either `gvisor` or `youki`:
118118

119-
```yaml
119+
```yaml title="Flexible filter example runtimeClass"
120120
sync:
121121
toHost:
122122
pods:
@@ -137,7 +137,7 @@ sync:
137137

138138
The following configuration syncs RuntimeClass resources that match both label and expression criteria:
139139

140-
```yaml
140+
```yaml title="Combined filter example runtimeClass"
141141
sync:
142142
toHost:
143143
pods:
@@ -160,7 +160,7 @@ sync:
160160

161161
When a Pod resource references a RuntimeClass that doesn't match the selector criteria, the error output looks like this:
162162

163-
```bash
163+
```bash title="Error handling example runtimeClass"
164164
vcluster-virtual-cluster-1:~$ kubectl describe pod my-pod
165165
Name: my-pod
166166
Namespace: default

0 commit comments

Comments
 (0)