mirror of
https://github.com/kemko/nomad.git
synced 2026-01-01 16:05:42 +03:00
a6f6384b71
* Permit Consul Connect Gateways to be used with podman Enable use of Consul Connect Gateways (ingresss/terminating/mesh) with podman task driver. task driver for Connect-enabled tasks for sidecar services which used podman if any other task in the same task group was using podman or fell back to docker otherwise. That PR did not consider consul connect gateways, which remained hardcoded to using docker task driver always. This change applies the same heuristic also to gateway tasks, enabling use of podman. Limitations: The heuristic only works where the task group containing the gateway also contains a podman task. Therefore it does not work for the ingress example in the docs (https://developer.hashicorp.com/nomad/docs/job-specification/gateway#ingress-gateway) which uses connect native and requires the gateway be in a separate task. * cl: add cl for connect gateway podman autodetect * connect: add test ensuring we guess podman for gateway when possible --------- Co-authored-by: Seth Hoenig <shoenig@duck.com>
4 lines
113 B
Plaintext
4 lines
113 B
Plaintext
```release-note:improvement
|
|
consul/connect: Attempt autodetection of podman task driver for Connect gateways
|
|
```
|