ClearML/clearml-docs
1
0
Fork 0
mirror of https://github.com/clearml/clearml-docs synced 2025-04-05 13:45:46 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity

Small edits

Browse Source
This commit is contained in:
Noam Wasersprung 2025-03-27 12:38:24 +02:00 committed by GitHub
commit 62796b5a13
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
4 changed files with 18 additions and 17 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
docs/deploying_clearml/enterprise_deploy/appgw_install_compose_hosted.md
View File

@ -10,7 +10,7 @@ The AI Application Gateway enables external access to ClearML tasks, and applic
require HTTP or TCP access. The gateway is configured with an endpoint or external address, making these services
accessible from the user's machine, outside the workload nodes’ network.
This guide details the installation of the App Gateway Router for ClearML users who use ClearML's SaaS control
This guide details the installation of the App Gateway Router for ClearML users who use ClearML's hosted control
plane while hosting their own workload nodes.
## Requirements

19
docs/deploying_clearml/enterprise_deploy/change_artifact_links.md
View File

@ -29,18 +29,19 @@ script changes the values in the databases, and can't be undone.
## Fixing MongoDB links
1. Access the `apiserver` Docker container:
* In `docker-compose:`
```commandline
sudo docker exec -it allegro-apiserver /bin/bash
* In `docker-compose:`
```commandline
sudo docker exec -it allegro-apiserver /bin/bash
```
* In Kubernetes:
```commandline
kubectl exec -it -n clearml <clearml-apiserver-pod-name> -- bash
```
* In Kubernetes:
```commandline
kubectl exec -it -n clearml <clearml-apiserver-pod-name> -- bash
```
1. Navigate to the script location in the `upgrade` folder:
```commandline

14
docs/deploying_clearml/enterprise_deploy/k8s.md
View File

@ -66,13 +66,13 @@ imageCredentials:
clearml:
cookieDomain: "<BASE_DOMAIN>"
# Set values for improved security
apiserverKey: ""
apiserverSecret: ""
fileserverKey: ""
fileserverSecret: ""
secureAuthTokenSecret: ""
testUserKey: ""
testUserSecret: ""
apiserverKey: "<GENERATED_API_SERVER_KEY>"
apiserverSecret: "<GENERATED_API_SERVER_SECRET>"
fileserverKey: "<GENERATED_FILE_SERVER_KEY>"
fileserverSecret: "<GENERATED_FILE_SERVER_SECRET>"
secureAuthTokenSecret: "<GENERATED_AUTH_TOKEN_SECRET>"
testUserKey: "<GENERATED_TEST_USER_KEY>"
testUserSecret: "<GENERATED_TEST_USER_SECRET>"
apiserver:

2
docs/deploying_clearml/enterprise_deploy/multi_tenant_k8s.md
View File

@ -565,7 +565,7 @@ curl $APISERVER_URL/system.create_company \
### Limit Features for all Users
This Helm Chart value in the `overrides.yaml` will have priority over all tenants, and will limit the features
available to any user in the system. This means that even if the feature is enabled for the tenant, if it;s not in this
available to any user in the system. This means that even if the feature is enabled for the tenant, if it's not in this
list, the user will not see it.
Example: all users will only have the `applications` feature enabled.