From 0fb204abb99564db4fdeb397fbd763bd2d61479f Mon Sep 17 00:00:00 2001 From: Steven Schattenberg Date: Fri, 26 Sep 2025 14:33:40 -0400 Subject: [PATCH] resource updates, readme updates --- README.md | 3 ++- charts/iag4/Chart.yaml | 2 +- charts/iag4/values.yaml | 10 ++++++---- 3 files changed, 9 insertions(+), 6 deletions(-) diff --git a/README.md b/README.md index e806ea4..98f2779 100644 --- a/README.md +++ b/README.md @@ -1,6 +1,7 @@ # Helm charts for Itential Automation Gateway 4 -This repo contains helm charts for running Itential Automation Gateway in Kubernetes. +This repo contains helm charts for running Itential Automation Gateway in Kubernetes. Requires +Helm version `v3.15.0`. ## Itential Automation Gateway (IAG) diff --git a/charts/iag4/Chart.yaml b/charts/iag4/Chart.yaml index e732a0a..2cff46c 100644 --- a/charts/iag4/Chart.yaml +++ b/charts/iag4/Chart.yaml @@ -10,7 +10,7 @@ type: application # This is the chart version. This version number should be incremented each time you make changes # to the chart and its templates, including the app version. # Versions are expected to follow Semantic Versioning (https://semver.org/) -version: 1.0.4 +version: 1.0.5 # This is the version number of the application being deployed. This version number should be # incremented each time you make changes to the application. Versions are not expected to diff --git a/charts/iag4/values.yaml b/charts/iag4/values.yaml index 465569f..5f38615 100644 --- a/charts/iag4/values.yaml +++ b/charts/iag4/values.yaml @@ -140,14 +140,16 @@ podSecurityContext: runAsUser: 1001 runAsNonRoot: true +# Consult the Itential Validated Designs to understand what the production recommendations are. +# https://docs.itential.com/docs/highly-available-architecture-server-specs#iag-server resourcesEnabled: true resources: limits: - cpu: "1000m" - memory: "256Mi" + cpu: "16" # production recommendation + memory: "32Gi" # production recommendation requests: - cpu: "1000m" - memory: "256Mi" + cpu: "4" + memory: "8Gi" # The liveness probe used to determine if the container is alive. If the liveness probe fails, # the kubelet kills the container, and the container is subjected to its restart policy. If a