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
As part of #6701 Nomad Clients should be able to configure envoy with an SI token.
gh-6718 covers Nomad Clients being able to request SI tokens be derived on behalf of tasks. Those tokens are written into the secrets directory for each task. Since Nomad provides first class support for using envoy as a Consul Connect sidecar, we can also set this token for envoy when generating the envoy_bootstrap.json file, in the envoy TR hook.
Until Task Dependencies exist, we'll need to think about the existing retry logic here and how it fits in with the token derivation retries.
The text was updated successfully, but these errors were encountered:
I'm going to lock this issue because it has been closed for 120 days ⏳. This helps our maintainers find and focus on the active issues.
If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.
As part of #6701 Nomad Clients should be able to configure
envoy
with an SI token.gh-6718 covers Nomad Clients being able to request SI tokens be derived on behalf of tasks. Those tokens are written into the
secrets
directory for each task. Since Nomad provides first class support for usingenvoy
as a Consul Connect sidecar, we can also set this token forenvoy
when generating theenvoy_bootstrap.json
file, in the envoy TR hook.Until Task Dependencies exist, we'll need to think about the existing retry logic here and how it fits in with the token derivation retries.
The text was updated successfully, but these errors were encountered: