-
Notifications
You must be signed in to change notification settings - Fork 85
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
aardvark, netavark: support network scoped dns via network_dns_servers
#497
aardvark, netavark: support network scoped dns via network_dns_servers
#497
Conversation
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: flouthoc The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Tests are expected to fail without containers/aardvark-dns#252 |
libnetwork must allow to pass network_dns_servers so aardvark and netavark can consume it and enabled network scoped dns. Feature implemented at netavark and aardvark end * Netavark: containers/netavark#497 Signed-off-by: Aditya R <[email protected]>
libnetwork must allow to pass network_dns_servers so aardvark and netavark can consume it and enabled network scoped dns. Feature implemented at netavark and aardvark end * Netavark: containers/netavark#497 Signed-off-by: Aditya R <[email protected]>
libnetwork must allow to pass network_dns_servers so aardvark and netavark can consume it and enabled network scoped dns. Feature implemented at netavark and aardvark end * Netavark: containers/netavark#497 Signed-off-by: Aditya R <[email protected]>
libnetwork must allow to pass network_dns_servers so aardvark and netavark can consume it and enabled network scoped dns. Feature implemented at netavark and aardvark end * Netavark: containers/netavark#497 Signed-off-by: Aditya R <[email protected]>
libnetwork must allow to pass network_dns_servers so aardvark and netavark can consume it and enabled network scoped dns. Feature implemented at netavark and aardvark end * Netavark: containers/netavark#497 Signed-off-by: Aditya R <[email protected]>
42b5872
to
c8a49e6
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, just one small nit
test/testfiles/dualstack-bridge-network-container-dns-server.json
Outdated
Show resolved
Hide resolved
Aardvark and podman supports `network_dns_servers` which allows aardvark to configure a resolver at network level and all containers attached to a network honors this resolver. Needs: containers/aardvark-dns#252 Signed-off-by: Aditya R <[email protected]>
c8a49e6
to
46f9f59
Compare
/lgtm |
* Add support for `podman network update <>` ```console network update Description: update networks for containers and pods Usage: podman network update [options] NAME Examples: podman network update podman1 Options: --dns-add stringArray add network level nameservers --dns-drop stringArray remove network level nameservers ``` * Add support for `--network-dns-server` to `podman network create` Extends podman to support recently added features in `netavark` and `aardvark-dns` * containers/netavark#497 * containers/aardvark-dns#252 * containers/netavark#503 [NO NEW TESTS NEEDED] [NO TESTS NEEDED] Signed-off-by: Aditya R <[email protected]>
Aardvark and podman supports
network_dns_servers
which allows aardvark to configure a resolver at network level and all containers attached to a network honors this resolver.Needs: containers/aardvark-dns#252