Module for searching nodes running hostport services (CoreHA)

The module for searching for nodes with running hostport services (shturval-coreha) is designed for dynamically adding backends to HAProxy. The service is required if you are using an external balancer for Ingress.

The module is not critical for the operation of the platform; by default, it is installed in clusters in a disabled state. To enable, go to the Services and repositories section and open the Installed services page. Find Module for searching for nodes with running hostport services and change the value of the switch.

If there is no such service in the cluster, go to the Services and repositories section and open the Available charts page. On the shturval tab, select the shturval-coreha chart and click Install.

Select the required version of the chart, as well as the namespace kube-system. After selecting a chart version, the available “Service Configuration Options” (values) will be displayed on the right side of the screen. Enter the required parameters as customvalues ​​in the “Service Specification” block.

Please note! If you need to configure the search for Ingress Controller pods, you will need to make changes to the specification of the External Connection Control Module (shturval-ingress-controller).

Configuration helm chart shturval-coreha #

config:
  zoneName: <your-parameter-value>

Changes in the external connection management module #

When you need to configure the search for Ingress Controller pods and the Module for searching nodes with running hostport services (shturval-coreha) is running in the cluster, configure the Module for managing external connections:

1. Prepare a ShturvalServicePatch to apply to the specification (ssc) of the External Connection Control Module (shturval-ingress-controller), where add a label with the key ingress.cluster/name in customvalues, as in the example below.

apiVersion: ops.shturval.tech/v1beta2
kind: ShturvalServicePatch
metadata:
  name: <resource-name>
spec:
  shturvalServiceConfigName: shturval-ingress-controller
  customvalues:
    controller:
      labels:
        ingress.cluster/name: <your-parameter-value>
      hostPort:
        enabled: true # When enabled, ingress controller pods also use ports 80 and 443 on cluster nodes
      service:
        nodePorts:
          http: "<your-parameter-value>"
          https: "<your-parameter-value>"
        type: NodePort

2. Load the prepared ShturvalServicePatch into the cluster using import manifests.

Once ShturvalServicePatch is loaded, it will take time for the configuration to be applied. After completing the Ingress settings, the controller will work on host ports 30080/30443 and ports 80/443.

3. Set up the HAProxy configuration as in the example below using your parameter values.

resolvers coredns-cluster
    nameserver ns1 <api-server-vip>:<config.dns_port>
    accepted_payload_size 8192

backend cluster-prod01-dc1-ingress-http
    balance source
    mode tcp
    server-template daemonset 2 <label_value>.<namespace>.<config.zoneName>:80 check resolvers coredns-cluster init-addr none

4. To check if the settings are correctshturval-coreha, you can use the dig command from the balancer, using your own parameter values.

dig @<api-server-vip> -p 1053 <label_value>.<namespace>.<config.zoneName>

;; ANSWER SECTION:
default-nginx.ingress.cluster-prod01-dc1.shturval. 15 IN A  172.18.104.93
default-nginx.ingress.cluster-prod01-dc1.shturval. 15 IN A  172.18.104.92