Skip to content
Open
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 2 additions & 1 deletion README.md
Original file line number Diff line number Diff line change
@@ -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)

Expand Down
2 changes: 1 addition & 1 deletion charts/iag4/Chart.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -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
Expand Down
10 changes: 6 additions & 4 deletions charts/iag4/values.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -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
Expand Down