You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
feat(liqoctl): specify non-standard resources with liqoctl
This patch introduces the `--resource` flag to the `peer` `create
virtualnode` and `create resourceslice` commands, to allow the user to
directly specify custom resources without the needs to manually edit the
manifests.
Copy file name to clipboardExpand all lines: docs/advanced/peering/offloading-in-depth.md
+1Lines changed: 1 addition & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -61,6 +61,7 @@ You can specify the resources you want to acquire by adding:
61
61
*`--cpu` to specify the amount of CPU.
62
62
*`--memory` to specify the amount of memory.
63
63
*`--pods` to specify the number of pods.
64
+
*`--resource` other resources can be specified with this flag, which can be even repeated multiple times. (e.g: `--resource=nvidia.com/gpu=2 --resource=my.custom/resource=2Gi`)
64
65
65
66
To add other resources like `ephemeral-storage`, `gpu`, or any other custom resources, you can use the `-o yaml` flag for the `liqoctl create resourceslice` command and edit the `ResourceSlice` spec manifest before applying it.
Copy file name to clipboardExpand all lines: docs/usage/peer.md
+14-2Lines changed: 14 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -36,8 +36,8 @@ To perform a peering without having access to both clusters, you need to manuall
36
36
The peering command enables all 3 liqo modules and performs the following steps:
37
37
38
38
1.**enables networking**.
39
-
Exchanges network configurations and creates the two **gateways** (one acting as _server_ and located in the provider cluster, another acting as _client_ in the consumer cluster) to let the two clusters communicate over a secure tunnel.
40
-
The location of the client/server gateway can be customized when creating the peering using the `--gw-server-service-location` flag in `liqoctl`.
39
+
Exchanges network configurations and creates the two **gateways** (one acting as _server_ and located in the provider cluster, another acting as _client_ in the consumer cluster) to let the two clusters communicate over a secure tunnel.
40
+
The location of the client/server gateway can be customized when creating the peering using the `--gw-server-service-location` flag in `liqoctl`.
41
41
2.**enables authentication**.
42
42
Authenticates the consumer with the provider.
43
43
In this step, the consumer obtains an `Identity` (*kubeconfig*) to replicate resources to the provider cluster.
@@ -237,6 +237,18 @@ liqoctl peer \
237
237
--memory=2Gi
238
238
```
239
239
240
+
Other non-standard resources can be defined via the `--resource` flag:
241
+
242
+
```bash
243
+
liqoctl peer \
244
+
--kubeconfig=$CONSUMER_KUBECONFIG_PATH \
245
+
--remote-kubeconfig=$PROVIDER_KUBECONFIG_PATH \
246
+
--cpu=2 \
247
+
--memory=2Gi \
248
+
--resource=nvidia.com/gpu=2 \
249
+
--resource=custom=2Gi
250
+
```
251
+
240
252
```{warning}
241
253
To make sure the consumer cluster does not exceed the quota of shared resources, the offloaded pods need to be created with the resources `limits` set.
0 commit comments