-
Notifications
You must be signed in to change notification settings - Fork 2k
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
connect block blank in job inspect output #7397
Comments
Created a job with all the settings filled in under the Input: service {
name = "count-api"
port = "9001"
connect {
sidecar_service {
proxy {
expose {
path {
path = "/health"
protocol = "http"
local_path_port = 9001
listener_port = "example"
}
}
local_service_address = "10.0.0.1"
local_service_port = 8081
upstreams {
destination_name = "my-upstream"
local_bind_port = 8090
}
config {
foo = "bar"
}
}
port = "example"
tags = ["a", "b"]
}
sidecar_task {
# name = "my-sidecar"
driver = "docker"
user = "bob"
config {
a = "b"
}
env {
MY_SIDECAR = "v1"
}
resources {
cpu = 400
memory = 256
}
meta {
foo = "bar"
}
logs {
max_files = 4
}
kill_timeout = "10s"
shutdown_delay = "5s"
kill_signal = "SIGTERM"
}
}
} Inspect: $ nomad job inspect foo | jq '.Job.TaskGroups[0].Services[0].Connect' | cat
{
"Native": false,
"SidecarService": {
"Port": "example",
"Proxy": {
"Config": {
"foo": "bar"
},
"ExposeConfig": null,
"LocalServiceAddress": "",
"LocalServicePort": 0,
"Upstreams": [
{
"DestinationName": "my-upstream",
"LocalBindPort": 8090
}
]
},
"Tags": [
"a",
"b"
]
},
"SidecarTask": {
"Config": {
"a": "b"
},
"Driver": "docker",
"Env": {
"MY_SIDECAR": "v1"
},
"KillSignal": "SIGTERM",
"KillTimeout": 10000000000,
"LogConfig": {
"MaxFileSizeMB": 0,
"MaxFiles": 4
},
"Meta": {
"foo": "bar"
},
"Name": "",
"Resources": {
"CPU": 400,
"Devices": null,
"DiskMB": 0,
"IOPS": 0,
"MemoryMB": 256,
"Networks": null
},
"ShutdownDelay": 5000000000,
"User": "bob"
}
} Looks like we are missing all of the It seems |
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. |
Possibly related to #7275, I noticed the output of
inspect
does not provideconnect
information.From the original job:
The text was updated successfully, but these errors were encountered: