F5Networks
Multicluster VS/TS not able to use same service name while using alternate Backends
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
- Create your deployment and service with exact same name in cluster A and B
- Deploy VS/TS with alternate backends and point into service that has the same name in both clusters.
- 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.
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 ?
Hi @avinashchundu9 if possible can you please share a copy of sample vs/ts spec with the same config.
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: - service: f5-hello-world-ts-sc weight: 30 serviceNamespace: achundu
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.