Demo Environment

This guide is tailored to provide a straightforward, step-by-step approach to deploying Qpoint within a Kubernetes environment. It details the use of a Github repository with some pre-baked utilities that can help you test Qpoint right away. If you have your own Kubernetes resources you'd like to test with Qpoint, this guide may be irrelevant.

Prerequisites

• git

• make

• Docker

Clone the Demo Repository

You'll need to clone the demo repository to your local machine and then enter that directory:

git clone https://github.com/qpoint-io/demos.git
cd demos

Bring up a Demo Environment

Get to know the Makefile by running the following command in the cloned demos folder:

make help

You can launch a demo environment using the following command:

make up

Install Qpoint

• Create an Account

• Install the Operator

• Enable Workloads

If you’d like to use the pre-baked utilities, you can enable workloads automatically by executing the following command to label all example namespaces

make label-namespaces-egress-inject

Install Applications

At this point, Qpoint is waiting and ready to go. We’ve prepared a number of tools to help you test the proxy which are available in the Demo repository. You can view them by running:

make list-apps

Simple (Ubuntu)

A basic Ubuntu container. Gain a shell into the container and use CURL to hit different endpoints.

make simple-app

Simple (Alpine)

A basic Alpine container. Gain a shell into the container and use CURL to hit different endpoints.

make simple-alpine-app

Simple (Fedora)

A basic Fedora container. Gain a shell into the container and use CURL to hit different endpoints.

make simple-fedora-app

Artillery

An API load testing utility built into a Docker container. Container's config file is available here.

make artillery-app

Datadog

Datadog is an infrastructure monitoring & security platform. You'll need an API key in order to use this service effectively which can be inserted here.

make datadog-app