Welcome to the Developer Sandbox for Red Hat OpenShift

Access Red Hat’s products and technologies without setup or configuration, and start developing quicker than ever before with our new sandbox environments for Red Hat OpenShift and CodeReady Workspaces. Try your hand at the technologies with our library of activities as well.

Understand the Sandbox

What is the Sandbox?

The sandbox provides you with a private OpenShift environment in a shared, multi-tenant OpenShift cluster that is pre-configured with a set of developer tools. You can easily create containers from your source code or Dockerfile, build new applications using the samples and stacks provided, add services such as databases from our templates catalog, deploy Helm charts, and much more. Discover the rich capabilities of the full developer experience on OpenShift with the sandbox.

What can I do in the Sandbox?

The sandbox is perfect for immediate access into OpenShift, but how can you start practicing your skills in this context if you don’t have a starting point yet? Well, we’ve taken care of that for you with a curated series of activities that you can complete in the sandbox.

DevNation Summer Camps

Let's chat

Share your ideas, connect with the Dev Sandbox community, and engage with Red Hat in the #dev-sandbox channel on DevNation Slack workspace.

Click here to join the DevNation workspace.

Frequently asked questions

Your Developer Sandbox for Red Hat OpenShift is active for 30 days and has specific built-in functionality. However, in some scenarios, we may be able to modify this time allotment and other default settings. Please communicate all of your modifications through the Red Hat team.

Contact the team creating the Developer Sandbox for Red Hat OpenShift.

Most settings and management needs can be taken care of from within your cluster interface itself.

Learn about developer-focused features in the OpenShift Developer Console.

 

Q: What is the Developer Sandbox for Red Hat OpenShift?

A: The sandbox provides you with a private OpenShift environment in a shared, multi-tenant OpenShift cluster that is pre-configured with a set of developer tools.

Q: What is my cost for the sandbox?

A: It is free. There is no credit card required. You just need a Red Hat account and to complete the phone verification process.

Q: Can I deploy my software on the sandbox?

A: That’s the idea! You’ll find that some software will deploy as-is, while other code might require some minor changes. You’ll quickly see how easy it is to create a container running your software on your cluster. Java, Node.js, Python, Go, C#, and more are supported.
 

Q: We’re not a Red Hat Enterprise Linux or a Red Hat shop. Can we still use the sandbox?

A: Absolutely. You don’t need to install anything to get started. You may want to install a command-line tool for your environment (Linux, macOS, or Windows -- all are welcome), but it’s not necessary.

Q: Which developer tools are available in my sandbox?

A: The default developer experience on OpenShift, including a catalog of Helm charts and Red Hat builder images, s2i build tool, and CodeReady Workspaces.

Q: How can I install additional developer tools in my sandbox?

A: Developer Sandbox for Red Hat OpenShift will provide a pre-configured set of tools and services. We would love to learn from you about other tools and services that we should consider adding to the sandbox. Please send us your request here.

Q: What kind of resources do I get with my sandbox?

A: Your private OpenShift environment includes two projects (namespaces) and a resource quota of 7 GB RAM, 15GB storage. The two namespaces can be used to emulate "development" and "stage" phases for your application.

Q: How long can my pods run in the sandbox?

A: All user pods can run for 12 (twelve) consecutive hours before they are automatically deleted.

Q: Why do I have to validate my phone number to access the sandbox?

A: We require a valid phone number to reduce the creation of fraudulent accounts on the Developer Sandbox for Red Hat OpenShift. Red Hat will not use this information for any other reason, and you will never receive a phone call from Red Hat or any third-party as a result of trying the sandbox.

Q: Why am I occasionally encountering Docker pull rate limit errors?

A: Docker Hub has a pull rate limit for downloading images as an anonymous user. Your private sandbox environment runs on a shared, multi-tenant OpenShift cluster so this limit can be reached during periods of increased activity. You can use a secret to pull your images as an authenticated Docker Hub user instead. See this article for instructions.

 

Don't see what you need? Ask a question here.

Calling all developers

Learn how to move your existing Java app to Kubernetes—without changing a single line of code

Watch demos on how you can take your existing source code or create a new application, easily deploy and manage them as containers, edit the code from our integrated developer experience, and much more.