Code Review / oom.git / commit
? search:
summary | shortlog | log | commit | commitdiff | review | tree
(parent: 0f3e134) | patch
DNS test server for ingress controller 42/101242/5
authorLucjan Bryndza <l.bryndza@samsung.com>
Thu, 6 Feb 2020 14:20:24 +0000 (15:20 +0100)
committerLucjan Bryndza <l.bryndza@samsung.com>
Mon, 17 Feb 2020 09:00:50 +0000 (10:00 +0100)
commite604acd6b77fda1c4850333df04ce7881afeecb5
tree9bbc93cc19d4af12b25d4aee48485d50f84dc957tree | snapshot
parent0f3e13456f6a311786d29e7a2a560070e3d96e81commit | diff
DNS test server for ingress controller

Testing ingress controller based on virtual hosts
requires a lot of entries in the /etc/hosts.
The better way is to create DNS server for testing purposes.

Signed-off-by: Lucjan Bryndza <l.bryndza@samsung.com>
Issue-ID: OOM-2289
Change-Id: I2ab104c7391e9634972931ac7e79bec5711d2b39
Signed-off-by: Lucjan Bryndza <l.bryndza@samsung.com>
kubernetes/contrib/dns-server-for-vhost-ingress-testing/README.md [new file with mode: 0644] blob
kubernetes/contrib/dns-server-for-vhost-ingress-testing/bind9dns/.helmignore [new file with mode: 0644] blob
kubernetes/contrib/dns-server-for-vhost-ingress-testing/bind9dns/Chart.yaml [new file with mode: 0644] blob
kubernetes/contrib/dns-server-for-vhost-ingress-testing/bind9dns/templates/NOTES.txt [new file with mode: 0644] blob
kubernetes/contrib/dns-server-for-vhost-ingress-testing/bind9dns/templates/_helpers.tpl [new file with mode: 0644] blob
kubernetes/contrib/dns-server-for-vhost-ingress-testing/bind9dns/templates/deployment.yaml [new file with mode: 0644] blob
kubernetes/contrib/dns-server-for-vhost-ingress-testing/bind9dns/templates/service.yaml [new file with mode: 0644] blob
kubernetes/contrib/dns-server-for-vhost-ingress-testing/bind9dns/templates/tests/test-connection.yaml [new file with mode: 0644] blob
kubernetes/contrib/dns-server-for-vhost-ingress-testing/bind9dns/values.yaml [new file with mode: 0644] blob
kubernetes/contrib/dns-server-for-vhost-ingress-testing/deploy_dns.sh [new file with mode: 0755] blob
Introduces the ONAP Platform OOM (ONAP Operations Manager) to efficiently Deploy, Manage, Operate the ONAP platform and its components (e.g. MSO, DCAE, SDC, etc.) and infrastructure (VMs, Containers).