Ingress-controller support on Kubernetes platform

Review Request #1236 — Created Dec. 16, 2025 and updated

pradeep
Ingress_controller
main
TWSD-1338
asrinivasan

Ingress-controller to support on kubernetes platform

below yaml files are tested.
apiVersion: v1
kind: Service
metadata:
name: service1
namespace: array-ingress
spec:
selector:
app: app-one
ports:
- port: 80
targetPort: 4343


apiVersion: apps/v1
kind: Deployment
metadata:
name: ingress-controller
namespace: array-ingress
spec:
replicas: 1
selector:
matchLabels:
app: app-one
template:
metadata:
labels:
app: app-one
spec:
containers:
- name: nginx
image: nginx:latest
ports:
- containerPort: 80


apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
name: ingress1
namespace: array-ingress
annotations:
# Required: Specify which Array device to use
arraynetworks.com/class: ARRAY-APV # or ARRAY-ASF

# Optional: Health Check configuration
apv.arraynetworks.com/healthcheck: |
  {
    "hc_type": "http",
    "ipv4": "8.8.4.4",
    "port": 8888,
    "hc_up": 4,
    "hc_down": 4,
    "retries" : 8,
    "interval": 8,
    "timeout": 8
  }

# Optional: Rate Limit configuration (APV only)
apv.arraynetworks.com/ratelimit: |
  {
    "max_cps": 12,
    "soft_bandwidth": 1012,
    "hard_bandwidth": 1012,
    "max_req": 12,
    "timeout": 12,
    "server_conn_reuse": true,
    "server_persistent_conn": true
  }
  spec:

ingressClassName: nginx # REPLACE with your ingress class name
rules:
- host: test.test1.com # REPLACE with your domain
http:
paths:
- path: /
pathType: Prefix
backend:
service:
name: service1
port:
number: 80

asrinivasan
  1. Please ensure to test two things 1) Add more replicas of ingress-controller and test if everything is working fine and no duplicate real service are created on APV 2) Test the same with ASF as well to ensure that is also working 3) Did you try increasing the replicas of nginx service and see if Real-services are changing accordingly?

  2. 
      
Loading...