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
When stopping/starting the nomad job with an expose stanza and a sidecar proxy the expose stanza get removed from the job spec in nomad and no longer exposes the /metrics. The only way to "fix" the issue is to redeploy the job.
Reproduction steps
Deploying the job. Stopping and then restarting the service
Expected Result
The /metrics endpoint to be exposed and accessible, still in the nomad jobspec
Thanks for the report. It seems like we may be dropping this field as the allocation data routes around the client and server. I will see if I can find where this is happening.
Nomad version
Output from
nomad version
Nomad v1.4.3 (f464aca)
Operating system and Environment details
Nomad config :
Consul config
Issue
When stopping/starting the nomad job with an expose stanza and a sidecar proxy the expose stanza get removed from the job spec in nomad and no longer exposes the /metrics. The only way to "fix" the issue is to redeploy the job.
Reproduction steps
Deploying the job. Stopping and then restarting the service
Expected Result
The /metrics endpoint to be exposed and accessible, still in the nomad jobspec
Actual Result
The expose block gets removed from the job spec
Job file (if appropriate)
Nomad Server logs (if appropriate)
Nomad Client logs (if appropriate)
No relevant logs discovered
The text was updated successfully, but these errors were encountered: