Known issues

As Google Distributed Cloud Sandbox is available in public preview, the following limitations apply:

  • GPUs: Not available in GDC Sandbox public preview release.
  • Persistence: GDC Sandbox is a test development environment that is automatically re-deployed with each incremental release. Configurations and data are not retained.
  • Instances: Instances are limited to 15.
  • Resources: This release limits the amount of the following resources:
    • One organization.
    • One tenant.
    • Two user cluster limit.
  • Users: To ensure adequate usage of shared resources, users are limited to a maximum of 25.
  • Sensitive Data: Users must consent to EULA prior to accessing GDC Sandbox. We recommend you not use GDC Sandbox for sensitive data or production workloads as it's intended for test, development, and training purposes.
  • IO experience: GDC Sandbox only supports the Application Operator (AO) or end-user experience of GDC.
  • Vertex AI: Pre-trained APIs are the only supported Vertex AI APIs on GDC Sandbox.
  • Vertex AI - Translation API GDC Sandbox only supports af-en and es-en language pairs for translation.

Known issues:

  1. GDC Sandbox is non-persistent and is refreshed incrementally on a monthly basis. When environments are refreshed, they're returned to a default state meaning you'll need to redeploy your configurations. It's recommended to save your configs, code, and containers in a code repository which also enables your low-high development into production environments.

  2. While uploading a file to a bucket (object storage), if you see an error Check network speed to ensure your file size is within limits and certificates are properly set., then follow this workaround.

    • On the browser in your GDC Sandbox, open the web page "https://objectstorage.org-1.zone1.google.gdch.test" and accept the certificate.
    • Try the file upload again.
    • If you still encounter issues like ErrPresignSignatureNotRecognized, try disabling using gdcloud config set storage/s3_insecure_skip_tls_verify true.

  3. The Vertex AI services status continuously shows "Enabling" even when the services APIs work. In this case, you might not be able to view the endpoints for each of the services. The endpoints are as listed here:

    • OCR: vision.org-1.zone1.google.gdch.test
    • Speech: speech.org-1.zone1.google.gdch.test
    • Translation: translation.org-1.zone1.google.gdch.test Use these endpoints, and contact GDC Sandbox support if the Vertex AI APIs don't work.

  4. Everytime you try to login to the console URL, it takes you back to the same login page. Contact GDC Sandbox support in this case.

  5. A Harbor instance creation fails and the status shows "Error". Contact GDC Sandbox support in this case.

  6. Login timeout: The authentication might time out on both UI and CLI if the environment is not accessed for a few minutes.

    • For UI timeout: Clear browser cache and refresh the browser.
    • For gdcloud timeout: Sign in again. See Sign in.

  7. Sometimes, the Console UI might show overlapping text, incorrect fonts, or unexpected elements. This issue usually resolves on its own, but if the problem persists, try clearing your browser's cache and restarting.

  8. When creating a backup repository, the Bucket name field expects the value to be a Fully Qualified Domain Name.

  9. standard-rwo: ReadWriteOnce is the only supported storage class for creating PVCs. The standard-rwx: ReadWriteMany storage class is not supported.

  10. After you set auth/login_config_cert_path using gdcloud config set, the value is unset after running a gdcloud auth login. The workaround for this issue is to always add --login-config-cert=/tmp/org-1-web-tls-ca.cert while running gdcloud auth login.

  11. Unable to launch Chrome after login into RDP. Try the following workaround:

    • Remove ~/.local/share/keyrings
    • Launch Chrome with command: /opt/google/chrome/google-chrome --password-store=basic

  12. If the Organization IAM Admin role is removed from the fop-platform-admin@example.com user, the role cannot be re-assigned and the user will lose access to most CUJs. Contact GDC Sandbox support in this case.

  13. "Failure to Open Web Browser" on the bootstrapper instance. The bootstrapper runs out of disk space and causes issues like the browser not opening. In most cases, the space is overloaded with dangling containers, volumes and images. Try the following fix to clean up some space:

    • docker images prune -a
    • docker volumes prune
    • docker containers prune

  14. ConfigMap creation failure. Contact GDC Sandbox support if you see a permissions issue in creating configmaps in the project namespaces.