diff --git a/docs/conf.py b/docs/conf.py index 5a49827d411..e64d1cae733 100644 --- a/docs/conf.py +++ b/docs/conf.py @@ -168,6 +168,7 @@ def setup(app): r"^http://127.0.0.1", r"^\.\./", "https://www.hpe.com/us/en/hpe-machine-learning-development-environment.html", + r"https://mldes\.ext\.hpe\.com.*", ] linkcheck_timeout = 20 diff --git a/docs/reference/deploy/helm-config-reference.rst b/docs/reference/deploy/helm-config-reference.rst index 5548c9ce93f..29cc4ffc2c4 100644 --- a/docs/reference/deploy/helm-config-reference.rst +++ b/docs/reference/deploy/helm-config-reference.rst @@ -122,11 +122,11 @@ - ``type: gcs``: Checkpoints are stored on Google Cloud Storage (GCS). Authentication is done using GCP's "`Application Default Credentials `__" approach. When using - Determined inside Google Kubernetes Engine (GCE), the simplest approach is to ensure that the + Determined inside Google Kubernetes Engine (GKE), the simplest approach is to ensure that the nodes used by Determined are running in a service account that has the "Storage Object Admin" role on the GCS bucket being used for checkpoints. As an alternative (or when running outside of GKE), you can add the appropriate `service account credentials - `__ to your + `__ to your container (e.g., via a bind-mount), and then set the ``GOOGLE_APPLICATION_CREDENTIALS`` environment variable to the container path where the credentials are located. See :ref:`environment-variables` for more information on how to set environment variables in trial diff --git a/docs/reference/deploy/master-config-reference.rst b/docs/reference/deploy/master-config-reference.rst index 7175f8cea69..27aa129d45d 100644 --- a/docs/reference/deploy/master-config-reference.rst +++ b/docs/reference/deploy/master-config-reference.rst @@ -1311,7 +1311,7 @@ inside Google Compute Engine (GCE), the simplest approach is to ensure that the Determined are running in a service account that has the "Storage Object Admin" role on the GCS bucket being used for checkpoints. As an alternative (or when running outside of GCE), you can add the appropriate `service account credentials -`__ to your +`__ to your container (e.g., via a bind-mount), and then set the ``GOOGLE_APPLICATION_CREDENTIALS`` environment variable to the container path where the credentials are located. See :ref:`environment-variables` for more information on how to set environment variables in trial environments. diff --git a/docs/reference/experiment-config-reference.rst b/docs/reference/experiment-config-reference.rst index 6b3222b2581..bd70226af17 100644 --- a/docs/reference/experiment-config-reference.rst +++ b/docs/reference/experiment-config-reference.rst @@ -522,7 +522,7 @@ inside Google Compute Engine (GCE), the simplest approach is to ensure that the Determined are running in a service account that has the "Storage Object Admin" role on the GCS bucket being used for checkpoints. As an alternative (or when running outside of GCE), you can add the appropriate `service account credentials -`__ to your +`__ to your container (e.g., via a bind-mount), and then set the ``GOOGLE_APPLICATION_CREDENTIALS`` environment variable to the container path where the credentials are located. See :ref:`environment-variables` for more details on how to set environment variables in containers. diff --git a/docs/setup-cluster/mldes/_index.rst b/docs/setup-cluster/mldes/_index.rst index ddf6da934fc..437463ab4d0 100644 --- a/docs/setup-cluster/mldes/_index.rst +++ b/docs/setup-cluster/mldes/_index.rst @@ -6,7 +6,8 @@ .. attention:: - MLDES only supports Determined Enterprise Edition. + MLDE Managed Service has been discontinued. This page is now obsolete but is left here for + historical reasons. ********** Overview