fix: use host network for runner containers to access cluster DNS
Change runner container network from bridge to host to allow workflow containers to resolve Kubernetes service DNS names. With bridge network, containers couldn't resolve forgejo.forgejo.svc.cluster.local. Using host network gives containers access to the cluster's DNS resolver. Co-Authored-By: Paperclip <noreply@paperclip.ing>
This commit is contained in:
parent
65a293999f
commit
46fa658a4e
1 changed files with 2 additions and 2 deletions
|
|
@ -18,6 +18,6 @@ data:
|
|||
enabled: true
|
||||
dir: /data/cache
|
||||
container:
|
||||
network: bridge
|
||||
network: host
|
||||
privileged: false
|
||||
options: --user 1000:1000 --add-host forgejo.forgejo.svc.cluster.local:10.102.251.20
|
||||
options: --user 1000:1000
|
||||
|
|
|
|||
Loading…
Add table
Reference in a new issue