standardizing SDC helm charts

all pods come up
robot health reports HTTP 500 -> mostly due to missing dmaap
resolving filebeat merge conflict
addressing CI comments

do we need a pv/pvc for the logs?

Issue-ID: OOM-747

Change-Id: Id6f1e57fdaf3cd6d9f75e8bc1e5bfde39b91235e
Signed-off-by: Mandeep Khinda <mandeep.khinda@amdocs.com>
Signed-off-by: Areli Fuss <af732p@intl.att.com>
(cherry picked from commit fe3e499547c91eadd71bde630594720b918c2af9)

1 files changed, 0 insertions, 27 deletions

diff --git a/kubernetes/sdc/resources/config/sdc-fe/FE_2_setup_configuration.rb b/kubernetes/sdc/resources/config/sdc-fe/FE_2_setup_configuration.rb
deleted file mode 100755
index 5c233a2207..0000000000
--- a/kubernetes/sdc/resources/config/sdc-fe/FE_2_setup_configuration.rb
+++ /dev/null
@@ -1,27 +0,0 @@
-jetty_base="/var/lib/jetty"
-template "catalog-fe-config" do
-   path "#{jetty_base}/config/catalog-fe/configuration.yaml"
-   source "FE-configuration.yaml.erb"
-   owner "jetty"
-   group "jetty"
-   mode "0755"
-   variables({
-      :fe_host_ip   => node['HOST_IP'],
-      :be_host_ip   => "sdc-be.{{.Values.nsPrefix}}",
-      :catalog_port => node['BE'][:http_port],
-      :ssl_port     => node['BE'][:https_port]
-   })
-end
-
-template "onboarding-fe-config" do
- path "#{jetty_base}/config/onboarding-fe/onboarding_configuration.yaml"
- source "FE-onboarding-configuration.yaml.erb"
- owner "jetty"
- group "jetty"
- mode "0755"
- variables({
-    :catalog_ip   => node['HOST_IP'],
-    :catalog_port => node['BE'][:http_port],
-    :ssl_port     => node['BE'][:https_port]
-})
-end