google / google/osdfir-infrastructure
GRR installers on Windows setup not properly working
- Dominant language
- Go Template
- Stars
- 213
- Forks
- 30
- Avg merge
- 14h 33m
- Merged PRs (30d)
- 5
Description
### Name and Version
charts/osdfir-infrastructure/grr
### What environment are you using?
Running in minikube (confirmed connection is possible via curl to IP/Port from another host)
### What steps will reproduce the bug?
When doing a fresh install with a specified GRR IP address and port
```
helm install my-release ../osdfir-infrastructure/ --set grr.clientBuilder.address="" --set-string grr.clientBuilder.port=30443
```
Then downloading the GRR Windows MSI installer and installing it on a Windows host.
The Windows host does not check in to the GRR console.
### Are you using any custom parameters or values?
_No response_
### What is the expected behavior?
You can visibly see that the GRR windows client checked into the GRR Admin Console. Also some instructions on basic troubleshooting on the client side would be very helpful to have.
### What do you see instead?
I don't see the GRR windows client in the GRR admin UI.
### Additional information
_No response_
Contributor guide
Research direction
Reproduce the fresh install using the charts/osdfir-infrastructure/grr setup and the shown helm command, then install the downloaded GRR Windows MSI. Check the GRR Admin Console and the Windows client for evidence of the failed check-in. Done means the Windows client appears in the console and basic client-side troubleshooting instructions are documented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- helm, kubernetes
- Domain
- devops, infrastructure, operating-systems, security
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100