mirror of
https://github.com/clearml/clearml-docs
synced 2025-05-20 20:25:33 +00:00
Small edits
This commit is contained in:
parent
9420513df8
commit
60be54d54b
@ -125,7 +125,7 @@ If the data and the configuration need to be restored:
|
|||||||
|
|
||||||
The following section contains a list of Custom Image URLs (exported in different formats) for each released ClearML Server version.
|
The following section contains a list of Custom Image URLs (exported in different formats) for each released ClearML Server version.
|
||||||
|
|
||||||
### Latest Version - v1.13.1
|
### Latest Version - v1.13.0
|
||||||
|
|
||||||
- [https://storage.googleapis.com/allegro-files/clearml-server/clearml-server.tar.gz](https://storage.googleapis.com/allegro-files/clearml-server/clearml-server.tar.gz)
|
- [https://storage.googleapis.com/allegro-files/clearml-server/clearml-server.tar.gz](https://storage.googleapis.com/allegro-files/clearml-server/clearml-server.tar.gz)
|
||||||
|
|
||||||
|
@ -8,7 +8,7 @@ The Application Gateway is available under the ClearML Enterprise plan.
|
|||||||
|
|
||||||
The AI Application Gateway enables external HTTP(S) or direct TCP access to ClearML tasks and applications running on
|
The AI Application Gateway enables external HTTP(S) or direct TCP access to ClearML tasks and applications running on
|
||||||
nodes. The gateway is configured with an endpoint or external address, making these services accessible from the user's
|
nodes. The gateway is configured with an endpoint or external address, making these services accessible from the user's
|
||||||
machine, outside the workload’ network.
|
machine, outside the workload's network.
|
||||||
|
|
||||||
This guide describes how to install and run the ClearML AI Application Gateway using docker-compose for environments
|
This guide describes how to install and run the ClearML AI Application Gateway using docker-compose for environments
|
||||||
where you manage both the ClearML Server and the workload nodes.
|
where you manage both the ClearML Server and the workload nodes.
|
||||||
|
@ -84,6 +84,8 @@ agentk8sglue:
|
|||||||
# -- Custom Bash script for the Task Pods ran by Glue Agent
|
# -- Custom Bash script for the Task Pods ran by Glue Agent
|
||||||
containerCustomBashScript: ""
|
containerCustomBashScript: ""
|
||||||
```
|
```
|
||||||
|
:::
|
||||||
|
|
||||||
|
|
||||||
## Examples
|
## Examples
|
||||||
|
|
||||||
@ -246,6 +248,7 @@ agentk8sglue:
|
|||||||
- mountPath: "/tmp/task/"
|
- mountPath: "/tmp/task/"
|
||||||
name: task-pvc
|
name: task-pvc
|
||||||
```
|
```
|
||||||
|
:::
|
||||||
|
|
||||||
### Example: Required Role
|
### Example: Required Role
|
||||||
|
|
||||||
|
@ -29,7 +29,7 @@ You have two configuration options:
|
|||||||
- [**Append**](#append-extra-certificates-to-the-existing-ca-certificatescrt) extra certificates to the existing `ca-certificates.crt`
|
- [**Append**](#append-extra-certificates-to-the-existing-ca-certificatescrt) extra certificates to the existing `ca-certificates.crt`
|
||||||
|
|
||||||
|
|
||||||
### Replace Entire `ca-certificates.crt` File
|
### Replace Entire ca-certificates.crt File
|
||||||
|
|
||||||
To replace the whole ca-bundle, provide a concatenated list of all trusted CA certificates in `pem` format as
|
To replace the whole ca-bundle, provide a concatenated list of all trusted CA certificates in `pem` format as
|
||||||
they are stored in a standard `ca-certificates.crt`.
|
they are stored in a standard `ca-certificates.crt`.
|
||||||
@ -51,7 +51,7 @@ customCertificates:
|
|||||||
...
|
...
|
||||||
```
|
```
|
||||||
|
|
||||||
### Append Extra Certificates to the Existing `ca-certificates.crt`
|
### Append Extra Certificates to the Existing ca-certificates.crt
|
||||||
|
|
||||||
You can add certificates to the existing CA bundle. Each certificate must have a unique `alias`.
|
You can add certificates to the existing CA bundle. Each certificate must have a unique `alias`.
|
||||||
|
|
||||||
@ -104,7 +104,7 @@ You have two configuration options:
|
|||||||
- [**Append**](#append-extra-certificates-to-the-existing-ca-certificatescrt-1) extra certificates to the existing `ca-certificates.crt`
|
- [**Append**](#append-extra-certificates-to-the-existing-ca-certificatescrt-1) extra certificates to the existing `ca-certificates.crt`
|
||||||
|
|
||||||
|
|
||||||
### Replace Entire `ca-certificates.crt` File
|
### Replace Entire ca-certificates.crt File
|
||||||
|
|
||||||
To replace the whole ca-bundle, provide a concatenated list of all trusted CA certificates in `pem` format as
|
To replace the whole ca-bundle, provide a concatenated list of all trusted CA certificates in `pem` format as
|
||||||
they are stored in a standard `ca-certificates.crt`.
|
they are stored in a standard `ca-certificates.crt`.
|
||||||
@ -127,7 +127,7 @@ customCertificates:
|
|||||||
...
|
...
|
||||||
```
|
```
|
||||||
|
|
||||||
### Append Extra Certificates to the Existing `ca-certificates.crt`
|
### Append Extra Certificates to the Existing ca-certificates.crt
|
||||||
|
|
||||||
You can add certificates to the existing CA bundle. Each certificate must have a unique `alias`.
|
You can add certificates to the existing CA bundle. Each certificate must have a unique `alias`.
|
||||||
|
|
||||||
|
@ -46,17 +46,17 @@ helm repo update
|
|||||||
* Configure `devicePlugin.config.data.renamed-resources.sharing.timeSlicing.resources` for each GPU index on the host
|
* Configure `devicePlugin.config.data.renamed-resources.sharing.timeSlicing.resources` for each GPU index on the host
|
||||||
* Use `nvidia.com/gpu-<INDEX>` format for the `rename` field, and set `replicas` to `8`.
|
* Use `nvidia.com/gpu-<INDEX>` format for the `rename` field, and set `replicas` to `8`.
|
||||||
|
|
||||||
```yaml
|
```yaml
|
||||||
gfd:
|
gfd:
|
||||||
imagePullSecrets:
|
imagePullSecrets:
|
||||||
- "clearml-dockerhub-access"
|
- "clearml-dockerhub-access"
|
||||||
toolkit:
|
toolkit:
|
||||||
env:
|
env:
|
||||||
- name: ACCEPT_NVIDIA_VISIBLE_DEVICES_ENVVAR_WHEN_UNPRIVILEGED
|
- name: ACCEPT_NVIDIA_VISIBLE_DEVICES_ENVVAR_WHEN_UNPRIVILEGED
|
||||||
value: "false"
|
value: "false"
|
||||||
- name: ACCEPT_NVIDIA_VISIBLE_DEVICES_AS_VOLUME_MOUNTS
|
- name: ACCEPT_NVIDIA_VISIBLE_DEVICES_AS_VOLUME_MOUNTS
|
||||||
value: "true"
|
value: "true"
|
||||||
devicePlugin:
|
devicePlugin:
|
||||||
repository: docker.io/clearml
|
repository: docker.io/clearml
|
||||||
image: k8s-device-plugin
|
image: k8s-device-plugin
|
||||||
version: v0.17.1-gpu-card-selection
|
version: v0.17.1-gpu-card-selection
|
||||||
@ -101,7 +101,7 @@ devicePlugin:
|
|||||||
devices:
|
devices:
|
||||||
- "1"
|
- "1"
|
||||||
replicas: 8
|
replicas: 8
|
||||||
```
|
```
|
||||||
|
|
||||||
#### For CFGI version < 1.3.0 (Legacy)
|
#### For CFGI version < 1.3.0 (Legacy)
|
||||||
|
|
||||||
|
Loading…
Reference in New Issue
Block a user