• vefimova's avatar
    Added ability for Docker containers to set usage of dns settings along with hostNetwork is true · fc8a37ec
    vefimova authored
    Introduced chages:
       1. Re-writing of the resolv.conf file generated by docker.
          Cluster dns settings aren't passed anymore to docker api in all cases, not only for pods with host network:
          the resolver conf will be overwritten after infra-container creation to override docker's behaviour.
    
       2. Added new one dnsPolicy - 'ClusterFirstWithHostNet', so now there are:
          - ClusterFirstWithHostNet - use dns settings in all cases, i.e. with hostNet=true as well
          - ClusterFirst - use dns settings unless hostNetwork is true
          - Default
    
    Fixes #17406
    fc8a37ec
Name
Last commit
Last update
.github Loading commit data...
Godeps Loading commit data...
api Loading commit data...
build Loading commit data...
cluster Loading commit data...
cmd Loading commit data...
docs Loading commit data...
examples Loading commit data...
federation Loading commit data...
hack Loading commit data...
hooks Loading commit data...
logo Loading commit data...
pkg Loading commit data...
plugin Loading commit data...
staging Loading commit data...
test Loading commit data...
third_party Loading commit data...
translations Loading commit data...
vendor Loading commit data...
.bazelrc Loading commit data...
.gazelcfg.json Loading commit data...
.generated_files Loading commit data...
.gitattributes Loading commit data...
.gitignore Loading commit data...
BUILD.bazel Loading commit data...
CHANGELOG.md Loading commit data...
CONTRIBUTING.md Loading commit data...
LICENSE Loading commit data...
Makefile Loading commit data...
Makefile.generated_files Loading commit data...
OWNERS Loading commit data...
OWNERS_ALIASES Loading commit data...
README.md Loading commit data...
Vagrantfile Loading commit data...
WORKSPACE Loading commit data...
code-of-conduct.md Loading commit data...
labels.yaml Loading commit data...