search

F5Networks / k8s-bigip-ctlr

Repository for F5 Container Ingress Services for Kubernetes & OpenShift.
Apache License 2.0
364 stars 195 forks source link

Multicluster VS/TS not able to use same service name while using alternate Backends #3537

Open avinashchundu9 opened 2 months ago

avinashchundu9 commented 2 months ago

Setup Details

CIS Version : 2.17.1
Build: f5networks/k8s-bigip-ctlr:latest
BIGIP Version: Big IP v16.1.3.1
AS3 Version: 3.46
Agent Mode: AS3
Orchestration: K8S
Orchestration Version: 1.28
Pool Mode: Nodeport

Description

VS/TS not able to use same service name while using alternate Backends

Steps To Reproduce

1) Create your deployment and service with exact same name in cluster A and B 2) Deploy VS/TS with alternate backends and point into service that has the same name in both clusters. 3) In the pool member we will only see primary cluster members. But if we deploy it with different names we can all pool members from both the clusters.

Expected Result

We should be able to use the same service name in both clusters and use alternate backends with weight

Actual Result

Pool members only contain primary cluster nodes and mission secondary cluster nodes.

trinaths commented 2 months ago

Created [CONTCNTR-4853] for internal tracking.

charanm08 commented 2 months ago

Hi @avinashchundu9 can you please share the sample vs/ts spec for this issue. Can you please confirm Is CIS running in active-active mode ?

charanm08 commented 2 months ago

Hi @avinashchundu9 if possible can you please share a copy of sample vs/ts spec with the same config.

avinashchundu9 commented 2 months ago

Here are the YAML files:

apiVersion: "cis.f5.com/v1" kind: TransportServer metadata: labels: f5cr: "true" name: f5-hello-world-ts namespace: achundu spec: mode: standard virtualServerAddress: "IPaddress1" virtualServerPort: 8080 virtualServerName: f5-hello-world-ts pool: service: f5-hello-world-ts-sc servicePort: 8080 loadBalancingMethod: fastest-node monitor: type: tcp interval: 10 timeout: 10 weight: 70 alternateBackends:

charanm08 commented 2 months ago

Hi @avinashchundu9 as per the issue description, issue is with the alternateBackends. That is missing in the config Can you please share with that config.

avinashchundu9 commented 2 months ago

I updated the YAML file with an alternate backend. Please check.