# OpenShift Network Playground Overview

## Overview

The OpenShift Network Playground is both web-based and cli-based interface built for advanced OpenShift users that makes it easy to quickly build and test different OpenShift network scenarios.

OpenShift Network Playground enables you to do the following:

* Zero touch installation
* Deploy an OpenShift Baremetal IPI cluster using an single command.
* Deploy Single-stack or Dual-stack cluster Single Node OpenShift cluster.
* Reproduce all the network related scenarios.
* Store and restore multiple OpenShift releases - Saves deployment time.
* Plug in additional network interface
* Fast reproducer using pre-added manifests
* OpenShift node console access and authentication

## Glossary of common terms for OpenShift Container Platform <a href="#getting-started-openshift-common-terms_openshift-overview" id="getting-started-openshift-common-terms_openshift-overview"></a>

This glossary defines common Kubernetes and OpenShift Container Platform terms.

### Kind

kind is a tool for running local Kubernetes clusters using Docker container "nodes". kind was primarily designed for testing Kubernetes itself, but may be used for local development or CI.

### DNS64

DNS64 is a DNS service that returns AAAA records with these synthetic IPv6 addresses for IPv4-only destinations (with A but not AAAA records in the DNS). This lets IPv6-only clients use NAT64 gateways without any other configuration.

### NAT64

NAT64 is an IPv6 transition mechanism that facilitates communication between IPv6 and IPv4 hosts by using a form of network address translation (NAT).


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://kevy.gitbook.io/onp/getting-started/openshift-network-playground-overview.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.