You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Mar 22, 2024. It is now read-only.
Currently the only solution for tiering requires the spire-agent to be codeployed with the server, but within a different Pod, which then uses the spire CSI driver to expose the agent to the server instance.
We should have a second, much simpler deployment available too, where the upstream agent is simply co-deployed within the server Pod as a side-car. This would avoid the need for a spire CSI driver between the two, as they would both share a filesystem and could read the UNIX domain socket without any extra intermediates.
The text was updated successfully, but these errors were encountered:
Currently the only solution for tiering requires the spire-agent to be codeployed with the server, but within a different Pod, which then uses the spire CSI driver to expose the agent to the server instance.
We should have a second, much simpler deployment available too, where the upstream agent is simply co-deployed within the server Pod as a side-car. This would avoid the need for a spire CSI driver between the two, as they would both share a filesystem and could read the UNIX domain socket without any extra intermediates.
The text was updated successfully, but these errors were encountered: