Overview
This section describes the different types of nextgen gateway installation procedures.
The NextGen gateway collector is currently deployed in the following three ways:
This section also includes:
- Installation of High Availability Gateway
- Installation of NextGen Gateway on Ubuntu VM
- Helm Based Deployment
- Kubernetes Dashboard
For advanced configuration, refer to the Collector Bootstrap Tool documentation.
Gateway Capacity Parameters
CPU | Memory | Capacity (resources/min) | Capacity (metrics/min) | |
---|---|---|---|---|
Large | 8 core | 16 GB | 400 | 3200 |
Medium | 4 core | 8 GB | 200 | 1600 |
The above capacity parameters are approximate and can vary depending on various factors, such as template frequency, resource type, network protocol, and the type of metrics.
FAQ’s
How do I add proxy settings to Node?
Step-1: Add the proxy settings to /etc/environments
.
HTTP_PROXY=
HTTPS_PROXY=
NO_PROXY=localhost,127.0.0.1,10.43.0.1,<NODE_IPs>
Step-2: Login again with the same user for the proxy settings to function properly.
Step-3: Now, install the k3s.Step-4: The proxy settings listed above will also be added to
/etc/system/systemd/k3s.service.env
.How do I change proxy settings at the node level after installing k3s?
Step-1: Edit the proxy settings in /etc/system/systemd/k3s.service.env file
.
Step-2: Now, use the following command to restart the k3s service:
systemctl restart k3s