Guide to Configuring TCP Service Forwarding with Ingress-Nginx in Kubernetes

Fri, 20 Dec 2024 00:00:00 +0000

This guide explains how to configure an Ingress-Nginx controller in a Kubernetes cluster to support TCP service forwarding, using MySQL service as an example.

Prerequisites

Kubernetes cluster installed
Ingress-Nginx controller deployed
Existing TCP service to expose (MySQL in this example)

Configuration Steps

Configure TCP Service Mapping

Create a tcp-services.yaml file to define TCP port mappings:

apiVersion: v1
kind: ConfigMap
metadata:
  name: tcp-services
  namespace: ingress-nginx
data:
  # Syntax: <external_port>: "<namespace>/<service_name>:<target_port>"
  3306: "default/mysql-primary:3306"

Apply configuration:

`1`	`kubectl create -f tcp-services.yaml`

If the ConfigMap already exists, edit directly:

1
2

kubectl edit configmap tcp-services -n ingress-nginx
# Add new mapping under data: <external_port>: "<namespace>/<service_name>:<port>"

Update Ingress Controller Configuration

Edit the Ingress-Nginx Controller Deployment:

`1`	`kubectl edit deployment ingress-nginx-controller -n ingress-nginx`

Add the following configuration to the controller’s args section:

1
2
3

args:
  # ... existing parameters ...
  - --tcp-services-configmap=$(POD_NAMESPACE)/tcp-services

Configuring Ingress Controller Service

Edit the Ingress-Nginx Controller Service:

`1`	`kubectl edit service ingress-nginx-controller -n ingress-nginx`

Add TCP service port configuration in the ports section:

ports:
  # ... Other existing port configurations ...
  - name: mysql-primary
    port: 3306
    protocol: TCP
    targetPort: 3306

Verification

After completing configurations, verify with following methods:

Check ConfigMap creation:

`1`	`kubectl get configmap tcp-services -n ingress-nginx -o yaml`

Confirm Ingress Controller status:

`1`	`kubectl get pods -n ingress-nginx`

Verify port exposure:

`1`	`kubectl get svc ingress-nginx-controller -n ingress-nginx`

Notes

Ensure target services (e.g., MySQL) are properly running in the cluster
Check for port conflicts
Additional security group/firewall rule configurations may be required for cloud providers

Guide to Setting Up Confluence with Docker

Wed, 22 Mar 2023 00:00:00 +0000

Required File Downloads:

1
2

wget https://minio-console.coderkang.top/files/atlassian-agent.jar
wget https://minio-console.coderkang.top/files/mysql-connector-j-8.3.0.jar

docker-compose.yaml

version: '3.8'
name: atlassian
services:
  confluence:
    image: atlassian/confluence-server:8.5.2
    container_name: atlassian-confluence
    restart: always
    environment:
      - TZ=Asia/Shanghai
      - JVM_MINIMUM_MEMORY=4096m
      - JVM_MAXIMUM_MEMORY=8192m
      - ATL_DB_TYPE=mysql
      - ATL_JDBC_URL=jdbc:mysql://db:3306/confluence?sessionVariables=transaction_isolation='READ-COMMITTED'
      - ATL_JDBC_USER=root
      - ATL_JDBC_PASSWORD=******
      - JAVA_OPTS='-javaagent:/opt/atlassian-agent.jar'
    ports:
      - 38090:8090
      - 38091:8091
    volumes:
      - ./application-data/:/var/atlassian/application-data/confluence/
      # - ./setenv.sh:/opt/atlassian/confluence/bin/setenv.sh
      - ./atlassian-agent.jar:/opt/atlassian-agent.jar
      - ./mysql-connector-j-8.3.0.jar:/opt/atlassian/confluence/confluence/WEB-INF/lib/mysql-connector-j-8.3.0.jar
    healthcheck:
      test: ["CMD", "curl", "-f", "http://localhost:8090"]
      interval: 10s
      timeout: 5s
      retries: 5
      start_period: 30s
    depends_on:
      db:
        condition: service_healthy

  db:
    image: mysql:latest
    container_name: atlassian-db
    restart: always
    environment:
      MYSQL_ROOT_PASSWORD: ******
      MYSQL_DATABASE: confluence
    command: --character-set-server=utf8mb4 --collation-server=utf8mb4_bin
    volumes:
      - ./application-db/data/:/var/lib/mysql/
      - ./application-db/conf.d/:/etc/mysql/conf.d/
    healthcheck:
      test: ["CMD", "mysqladmin", "ping", "-h", "localhost", "-u", "root", "-p******"]
      interval: 10s
      timeout: 5s
      retries: 5
      start_period: 30s

1
2

docker compose up -d
# The startup process may take some time as it needs to wait for the MySQL service to fully initialize

Access the webpage to obtain the Server ID.

docker compose exec -it confluence java -jar /opt/atlassian-agent.jar -m <Email> -n <Username> -o <Organization> -p conf -s '<Server ID>'

# Example:
# docker compose exec -it confluence java -jar /opt/atlassian-agent.jar -m CoderKang@hotmail.com -n CoderKang -o NiKo -p conf -s 'BHE8-N86V-SW29-TDDO'

Click “Next” after entering the information and wait…

📌 Important

If encountering issues during installation, after stopping the container:

Delete the application-db and application-data directories

Rebuild the container

MySQL Configuration on Kang's Blog