Skip to content

Install EgressGateway

This chapter mainly introduces how to install the EgressGateway component.

Prerequisites

  • To use EgressGateway within a DCE 5.0 cluster, it is necessary to combine it with Calico/Flannel/Weave/Spiderpool.

  • It is recommended to install EgressGateway v0.4.0 or higher. After installation, instances of the egress gateway can be created and use them in conjunction with egress gateway policies.

Steps

Confirm that your cluster has successfully connected to the Container Management platform, and then follow the steps below to install EgressGateway.

  1. In the left navigation bar, click Container Management -> Clusters , and then locate the cluster where you intend to install EgressGateway.

  2. In the left navigation bar, select Helm Apps -> Helm Charts , and find and click egressgateway .

    find egressgateway

  3. Choose the version you wish to install, then click Install . In the installation UI, fill in the required installation parameters.

    install

    fill in parameters

    The parameters in the above figure are described as follows:

    • Namespace : The namespace for deploying the EgressGateway component defaults to default . This can be changed to another namespace.
    • Feature -> Enable IPv4 : Supports enabling IPv4, which is enabled by default.
    • Feature -> Enable IPv6 : Supports enabling IPv6, which is disabled by default. If enabled, the pod network must be dual-stack to function properly.
    • Feature -> Tunnel IPv4 subnet : Sets the IPv4 subnet for the tunnel, which can use the default value. If changed, it must not overlap with the CIDR in the cluster to avoid network conflicts.
    • Feature -> Tunnel IPv6 subnet : Sets the IPv6 subnet for the tunnel, which can use the default value. If changed, it must not overlap with the CIDR in the cluster to avoid network conflicts.
    • Feature -> VXLAN Setting -> VXLAN name : Sets the name for the VXLAN, which can use the default value.
    • Feature -> VXLAN Setting -> VXLAN port : Sets the port for the VXLAN, which can use the default value.
    • Feature -> VXLAN Setting -> VXLAN ID : Sets the VXLAN ID, which can use the default value.
    • Feature -> Iptables Setting -> Backend mode : Sets the mode for iptables, with the default selection being auto mode. If changed, you can check the current mode of iptables by running “iptables –version” on the cluster host.

    fill in parameters

    The parameters in the above figure are described as follows:

    • Controller Setting -> Image Setting -> Image registry : Set the image name, which can use the default value.
    • Controller Setting -> Debug Setting -> Log level : Set the log level, which can use the default value, or you can select another level.
    • Controller Setting -> Prometheus Setting -> ServiceMonitor Setting -> Log level -> Install : Support enabling the installation of Prometheus monitoring, which is not installed by default.
    • Agent Setting -> Image Setting -> Image registry : Set the image name, which can use the default value.
    • Controller Setting -> Debug Setting -> Log level : Set the log level, which can use the default value, or you can select another level.
    • Controller Setting -> Prometheus Setting -> ServiceMonitor Setting -> Log level -> Install : Support enabling the installation of Prometheus monitoring, which is not installed by default.

  4. After completing the parameter settings, click OK to finish the installation. Once completed, you can refer to the creation of egress gateway instances and gateway policies for using the egress gateway.

Comments