Skip to content

Conversation

@spottsdd
Copy link
Contributor

Description

Previous version of k8s manifest files for the frontend were missing variables needed for RUM. This adds the variables needed and steps in the readme files.

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, view rum data in the trial account to confirm data is received.

@spottsdd spottsdd requested review from a team as code owners July 11, 2025 11:47
Co-authored-by: tammergalal <80272161+tammergalal@users.noreply.github.com>
@spottsdd spottsdd merged commit 1daa224 into main Jul 11, 2025
1 check passed
@spottsdd spottsdd deleted the add-k8s-rum branch July 11, 2025 14:00
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants