This guide provides detailed instructions for increasing or decreasing memory limits for the NextGen Gateway components in a Kubernetes cluster using Helm. The steps include retrieving the current Helm chart version, updating memory limits, and verifying the changes.
- To begin, you need to retrieve the current Helm chart version for the NextGen Gateway. Run the following command:Example:
- Look for the version number after nextgen-gw in the output. For example, if the output shows nextgen-gw-1.7.1, then 1.7.1 is the chart version.
- Next, export the current Helm chart values to a file so you can modify them. Use the following command:
- Now, update the memory limits for the NextGen Gateway components. Use the command below, replacing
<chart_version>with the version you retrieved in step 1, and adjust the memory values as needed:Example Memory Allocation:- For a node with 8GB memory:
- vprobe: 4Gi
- postgres: 1Gi
- nativebridge: 500Mi
- squid-proxy: 500Mi
- For a node with 16GB memory:
- vprobe: 8Gi
- postgres: 2Gi
- nativebridge: 1Gi
- squid-proxy: 1Gi
- For a node with 8GB memory:
- Verify the Memory Limits:
- After updating the memory limits, you should verify that the changes have been applied successfully. Run the following command to check the limits on each container:
- Look under the Limits section for each container to ensure the memory limits have been updated according to your specifications.
Sample Output: