Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[multicluster] Doing A/B on more than two clusters #3493

Open
alonsocamaro opened this issue Jul 18, 2024 · 2 comments
Open

[multicluster] Doing A/B on more than two clusters #3493

alonsocamaro opened this issue Jul 18, 2024 · 2 comments

Comments

@alonsocamaro
Copy link

alonsocamaro commented Jul 18, 2024

Setup Details

CIS Version : 2.17.1
Build: f5networks/k8s-bigip-ctlr:2.17.1

Description

Using the following VS configuration with CIS multicluster with HA and active-active configuration:

pools:
  - path: /shop
    service: route-b-ocp1
    servicePort: 443
    weight: 50
    alternateBackends:
    - service: route-b-ocp2
      weight: 50
    extendedServiceReferences:
    - clusterName: ocp3
      namespace: openshift-ingress
      service: route-b-ocp3
      servicePort: 443
      weight: 50

It is expected that CIS would create 3 pools with equal distribution, instead it creates two pools (one for each pool that is not a service in the extendedServiceReferences) and the endpoints for of the service inside the extendedServiceReferences is added to both pools.

Expected Result

It is expected that 3 pools would be created, one for each service regardless this is in the extendedServiceReferences or not.

Actual Result

  • 2 pools (undesired) and
  • not equal distribution using the above configuration
@alonsocamaro alonsocamaro added bug untriaged no JIRA created labels Jul 18, 2024
@alonsocamaro
Copy link
Author

Please consider #3494 when evaluating this bug

@alonsocamaro alonsocamaro changed the title [multicluster] Doing A/B on more two clusters [multicluster] Doing A/B on more than two clusters Jul 22, 2024
@trinaths
Copy link
Contributor

Created [CONTCNTR-4810] for internal tracking.

@trinaths trinaths added JIRA and removed untriaged no JIRA created labels Jul 27, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants