-
Notifications
You must be signed in to change notification settings - Fork 492
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
SPIFFE_ENDPOINT_SOCKET env support for spire-agent #5776
base: main
Are you sure you want to change the base?
Conversation
Signed-off-by: Kevin Fox <Kevin.Fox@pnnl.gov>
// DefaultSocketPath is the SPIRE agent's default socket path | ||
var DefaultSocketPath string |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This will be used for API
calls and health checks
, except for the run
command, where we will continue using DefaultRunSocketPath
.
Is it expected to affect health checks?
If not, should we update the code to modify the default within AddOSFlags
instead?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We chatted about this. I believe the current plan is to do everything but run in one pr, and run in a future pr.
SPIFFE_ENDPOINT_SOCKET needs to support unix:// on the front according to: https://github.com/spiffe/spiffe/blob/main/standards/SPIFFE_Workload_Endpoint.md#4-locating-the-endpoint But this patch doesn't work with that currently. |
Signed-off-by: Kevin Fox <Kevin.Fox@pnnl.gov>
Signed-off-by: kfox1111 <Kevin.Fox@pnnl.gov>
Enables specifying SPIFFE_ENDPOINT_SOCKET to the non run subcommands to the spire-agent
partially-fixes: #5770