mirror of
https://github.com/clearml/clearml-docs
synced 2025-06-26 18:17:44 +00:00
Modify design (#471)
This commit is contained in:
@@ -19,7 +19,7 @@ and delete all cookies under the ClearML Server URL.
|
||||
|
||||
## Launching
|
||||
|
||||
:::warning
|
||||
:::caution
|
||||
By default, ClearML Server deploys as an open network. To restrict ClearML Server access, follow the instructions
|
||||
in the [Security](clearml_server_security.md) page.
|
||||
:::
|
||||
|
||||
@@ -208,7 +208,7 @@ For improved security, the ports for ClearML Server Elasticsearch, MongoDB, and
|
||||
they are only open internally in the docker network. If external access is needed, open these ports (but make sure to
|
||||
understand the security risks involved with doing so).
|
||||
|
||||
:::warning
|
||||
:::caution
|
||||
Opening the ports for Elasticsearch, MongoDB, and Redis for external access may pose a security concern and is not recommended
|
||||
unless you know what you're doing. Network security measures, such as firewall configuration, should be considered when
|
||||
opening ports for external access.
|
||||
|
||||
@@ -22,7 +22,7 @@ The migration process makes use of a script that automatically performs the foll
|
||||
* Renames the original data directory to avoid accidental reuse.
|
||||
|
||||
|
||||
:::warning
|
||||
:::caution
|
||||
Once the migration process completes successfully, the data is no longer accessible to the older version of Trains Server,
|
||||
and ClearML Server needs to be installed.
|
||||
:::
|
||||
|
||||
@@ -59,7 +59,7 @@ For more information see [Import the image to your custom images list](https://c
|
||||
## Launching
|
||||
|
||||
|
||||
:::warning
|
||||
:::caution
|
||||
By default, ClearML Server launches with unrestricted access. To restrict ClearML Server access, follow the
|
||||
instructions in the [Security](clearml_server_security.md) page.
|
||||
:::
|
||||
|
||||
@@ -23,7 +23,7 @@ Ensure that the `helm` binary is in the PATH of your shell.
|
||||
You will create a multi-node Kubernetes cluster using Helm, and then install ClearML in your cluster. For deployment
|
||||
instructions with up-to-date Helms charts, see the [clearml-helm-charts repository](https://github.com/allegroai/clearml-helm-charts/tree/main/charts/clearml#local-environment).
|
||||
|
||||
:::warning Server Access
|
||||
:::caution Server Access
|
||||
By default, ClearML Server launches with unrestricted access. To restrict ClearML Server access, follow the
|
||||
instructions in the [Security](clearml_server_security.md) page.
|
||||
:::
|
||||
|
||||
@@ -30,7 +30,7 @@ For Linux users only:
|
||||
## Deploying
|
||||
|
||||
|
||||
:::warning
|
||||
:::caution
|
||||
By default, ClearML Server launches with unrestricted access. To restrict ClearML Server access, follow the
|
||||
instructions in the [Security](clearml_server_security.md) page.
|
||||
:::
|
||||
|
||||
@@ -15,7 +15,7 @@ and delete all cookies under the ClearML Server URL.
|
||||
|
||||
## Deploying
|
||||
|
||||
:::warning
|
||||
:::caution
|
||||
By default, ClearML Server launches with unrestricted access. To restrict ClearML Server access, follow the instructions in the [Security](clearml_server_security.md) page.
|
||||
:::
|
||||
|
||||
|
||||
@@ -13,7 +13,7 @@ to upgrade and migrate to a [new AWS instance](#upgrading-and-migrating-to-a-new
|
||||
|
||||
This section contains the steps to upgrade ClearML Server on the same AWS instance.
|
||||
|
||||
:::warning
|
||||
:::caution
|
||||
Some legacy **Trains Server** AMIs provided an auto-upgrade on restart capability. This functionality is now deprecated.
|
||||
:::
|
||||
|
||||
|
||||
Reference in New Issue
Block a user