Test and create steps for manually building GRR clients for local setups

Name and Version

charts/grr

What is the problem this feature will solve?

Make GRR easier to configure in non GCP settings, such as running OSDFIR Infrastructure locally within a bare metal machine using Minikube or KIND and wanting to connect an external client back to the setup.

What is the feature you are proposing to solve the problem?

Test a process for building GRR clients manually with the OSDFIR Infrastructure setup. Essentially, this should do the following

• Documentation instructing them on how to build a GRR client adhoc
• Follows similar steps to the job-build-grr-client.yaml
• Ideally the user would specify an IP address/port and optionally a cert, then the job-build-grr-client.yaml can automatically rebuild with the new client installers (currently it does not do that).

Please ensure this has been tested, by installing OSDFIR Infrastructure on a test VM, configuring GRR fleetspeak with a new external IP/port, instructing the user to first test the connection works via curl or other similar tool, then lastly, builds the new client installer to be used.

See the various options and info for configuring GRR here:

• https://github.com/google/fleetspeak/tree/master/sandboxes
• https://osdfir.blogspot.com/2023/12/running-grr-everywhrr.html
• https://osdfir.blogspot.com/2024/01/life-of-grr-message_23.html

Bonus points if this new solution can utilize the envoy proxy:

• https://github.com/google/fleetspeak/tree/master/sandboxes/passthrough-mode

What alternatives have you considered?

No response