Added toplevel manifests for SDC sample scenario 41/54841/1
authorEddie Arrage <eddie.arrage@huawei.com>
Tue, 3 Apr 2018 23:10:00 +0000 (23:10 +0000)
committerEddie Arrage <eddie.arrage@huawei.com>
Tue, 3 Apr 2018 23:22:10 +0000 (23:22 +0000)
commit7381d8f19074c2d1bff6982d096d2c23c599172b
treed22d3645cc7ff1201a6850c643f13fbecfda6372
parent67b7fb49e6ea6ac9c2547af263355e5f1aeade42
Added toplevel manifests for SDC sample scenario

- Added missing k8s manifest yaml files for overall service delivery
controller scenario - cannot be deployed coherently without this manifest
- One file for private docker registry and one for opnfv
public registry
- Outlined in JIRA ticket CLOVER-16 and validated per
description
- Includes ingress rule, community redis pod/service and deployments
for http-lb (v1/v2), snort-ids, proxy-access-controller,
and clover-server1-5
- All above pod/deployment naming matches default container
configuration
- Tested with istio manual injection

Change-Id: Ia03782b38020d744ab00c99adbf4832d15bbd9f3
Signed-off-by: Eddie Arrage <eddie.arrage@huawei.com>
samples/scenarios/service_delivery_controller.yaml
samples/scenarios/service_delivery_controller_opnfv.yaml [new file with mode: 0644]