Page Comparison

Regular nodes count

Specifies the number of JCC deployed to run the SnapLogic container.

If HPA is enabled, then the minReplicas and maxReplicas counts are used from values.yaml

FeedMaster nodes count

Specifies the number of FeedMaster Pods to deploy.

Docker image of SnapLogic Snaplex image

Specifies the repository where the image resides and the tag indicating its version. Although you can specify a version of your Snaplex, we recommend entering the latest version for the most recently released SnapLogic build.

SnapLogic configuration link

Specifies the link to the SnapLogic JCC configuration file (also known as .slpropz).

SnapLogic Org admin credential

Specifies the secret (an encoded username and password) to authenticate the deployment

Enhanced encryption secret

Specifies the secret (an additional encoded username and password) to authenticate the deployment, available only to the user.

CPU and memory limits for the nodes

Specifies the upper limits and requests for the CPU and memory resources. You can set these values for only the upper limits. The lower limits are system-defined and cannot be modified.

Limits: The maximum amount of resources (CPU and memory) that a container can consume.
Requests: The minimum amount of resources that a container needs to function properly.

This ensures that the container is always scheduled on a node that can fulfill its minimum requirements.

Default file ulimit and process ulimit

Specifies the number of possible open file descriptors and processes for the JCC containers.

The value should be greater than the number of slots configured for the node (Maximum Slots under the Snaplex's node properties).

If not set, then the node defaults will be used.
(/etc/security/limits.conf).

Probes

Monitors the SnapLogic application.

Autoscaling

Sets autoscaling properties.

By default, enabled to False.

The HorizontalPodAutoScaler is enabled by setting this property to true.
Contact SnapLogic CSM for recommendations for this setting.

minReplicas
maxReplicas

minReplicas defines the minimum number of Pods that must be running.
maxReplicas defines the maximum number of Pods that can be scheduled on the node(s)

The general guideline is to start with 1:2 or 1:3 Pods per node.

targetAvgCPUUtilization

This is the average CPU utilization across all Pods. HPA will scale up or scale down Pods to maintain this average.

targetAvgMemoryUtilization

This parameter specifies the average memory utilization (as a percentage of the requested memory) that the HPA should maintain across all the replicas of a particular deployment or stateful set.

scaleDownStabilizationWindowSeconds

This parameter controls the amount of time the HPA waits (like a cool-down period) before scaling down the number of pods after a decrease
in resource utilization.

Termination Grace Period Seconds

The time to shut down a Pod gracefully before it gets terminated.

This is an upper limit for the time to gracefully shut down a Pod.

IPv6

Enabled to false by default. You can enable IPv6 for your connections if your infrastructure supports it.