Troubleshooting Launcher and Kubernetes#
RStudio is now Posit!
Our professional products have been renamed to Posit Connect, Posit Workbench, Posit Package Manager, Posit Cloud, and Posit Academy so it’s easier for folks to understand that we support more than just R. Please review our Blog post/FAQ to answer commonly asked questions about the rebrand.
If you are having issues when integrating Workbench with Kubernetes, then you can use the following troubleshooting steps to perform diagnostic tests, ensure that your configuration settings are valid, and verify that your Kubernetes cluster and environment is properly configured for Posit Workbench, formerly RStudio Workbench, and Launcher.
When to use these steps#
Use these troubleshooting steps if:
- The Workbench or Launcher services will not start
- If you are unable to access the Workbench home page in your browser
- If you are unable to start new remote sessions in Kubernetes
- If new remote sessions are stuck in a Pending or Suspended status
Log files and diagnostic tools#
Step 1. Check the log files related to the services and sessions
Step 2. Run the verify installation command to test your configuration
Launcher configuration issues#
Step 3. Check the status of the rstudio-server and rstudio-launcher
services
Step 4. Verify that your license is authorized to use Launcher
Step 5. Verify that the rserver node and Kubernetes cluster's clocks are synced
Step 6. Verify that your configuration files are correct
Kubernetes plugin configuration issues#
Step 7. Skip the Kubernetes SSL certificate verification for testing purposes
Step 8. Verify that your Kubernetes certificate authority is configured correctly
Step 9. Verify that your Kubernetes API URL is configured correctly
Step 10. Verify that your Kubernetes service account token is configured correctly
Kubernetes configuration and environment issues#
Step 11. Verify that your service account has access to the Kubernetes API
Step 12. Verify that the Docker images are accessible and configured correctly
Step 13. Ensure that you have added worker nodes to your Kubernetes cluster
Step 14. Ensure that you have adequate CPU/RAM resources for the Kubernetes worker nodes
Step 15. Verify that you have configured your NFS server correctly
Step 16. Verify network connectivity to your NFS server