Add Resource Limits for vfc

resolving merge conflict and aligning with resource
template

bumping up small/large limits so pods actually run

Issue-ID: OOM-1166

Change-Id: Ied1a88f99f288544272e106677bba3f3131e48cb
Signed-off-by: GregSulek <gsulek@amdocs.com>
Signed-off-by: Mandeep Khinda <mandeep.khinda@amdocs.com>

1 files changed, 20 insertions, 18 deletions

diff --git a/kubernetes/vfc/charts/vfc-zte-sdnc-driver/values.yaml b/kubernetes/vfc/charts/vfc-zte-sdnc-driver/values.yaml
index 3ea6f8d77d..4c9dbaab10 100644
--- a/kubernetes/vfc/charts/vfc-zte-sdnc-driver/values.yaml
+++ b/kubernetes/vfc/charts/vfc-zte-sdnc-driver/values.yaml
@@ -26,6 +26,8 @@ global:
 # Application configuration defaults.
 #################################################################
 # application image
+flavor: small
+
 repository: nexus3.onap.org:10001
 image: onap/vfc/ztesdncdriver:1.1.0
 pullPolicy: Always
@@ -69,21 +71,21 @@ service:
 ingress:
   enabled: false
 
-resources: {}
-  # We usually recommend not to specify default resources and to leave this as a conscious
-  # choice for the user. This also increases chances charts run on environments with little
-  # resources, such as Minikube. If you do want to specify resources, uncomment the following
-  # lines, adjust them as necessary, and remove the curly braces after 'resources:'.
-  #
-  # Example:
-  # Configure resource requests and limits
-  # ref: http://kubernetes.io/docs/user-guide/compute-resources/
-  # Minimum memory for development is 2 CPU cores and 4GB memory
-  # Minimum memory for production is 4 CPU cores and 8GB memory
-#resources:
-#  limits:
-#    cpu: 2
-#    memory: 4Gi
-#  requests:
-#    cpu: 2
-#    memory: 4Gi
+
+# Configure resource requests and limits
+resources:
+  small:
+    limits:
+      cpu: 200m
+      memory: 500Mi
+    requests:
+      cpu: 100m
+      memory: 250Mi
+  large:
+    limits:
+      cpu: 400m
+      memory: 1000Mi
+    requests:
+      cpu: 200m
+      memory: 500Mi
+  unlimited: {}
\ No newline at end of file