K8s move puppeteer service to fake-traffic namespace

[spottsdd]

Description

Previously Puppeteer ran in the same namespace as Storedog (usually storedog). This moved the puppeteer definition to a new folder and sets the namespace as fake-traffic.

How to test

K8s testing steps are outline in the k8s-manifests/readme. It's important to note that unlike Docker compose, K8s won't build container images. Images must be pre-built and hosted in a registry. For development, you can run a local registry. Then build and push images. The images must be built and pushed on the worker node as that is where the services will run and look for localhost.

The development K8s Sandbox is currently set to test. The services files from main branch are used to build and push to the local registry. You can also set the registry url to the live public version. Follow the steps in the readme to setup the Datadog operator and start Storedog.

Use the Storedog tab to the right of the worker tabs to load the site. Again, the pods are running on the worker node.

Once storedog is running, check pods in fake-traffic to confirm the pod is running:

kubectl get pods -n fake-traffic

View traffic in the trial account and confirm data is recieved.