Bug 2055551 - Unable to create more than one egress IP per namespace
Summary: Unable to create more than one egress IP per namespace
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Networking
Version: 4.10
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: 4.10.0
Assignee: Ben Bennett
QA Contact: Anurag saxena
URL:
Whiteboard:
Depends On:
Blocks: 2055549
TreeView+ depends on / blocked
 
Reported: 2022-02-17 08:35 UTC by Patryk Diak
Modified: 2022-02-17 08:39 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 2055549
Environment:
Last Closed: 2022-02-17 08:36:33 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Patryk Diak 2022-02-17 08:35:38 UTC
+++ This bug was initially created as a clone of Bug #2055549 +++

Description of problem:


Version-Release number of selected component (if applicable): 4.9


How reproducible:
- Always


Steps to Reproduce:
1. Apply EIP similar to the following:
apiVersion: k8s.ovn.org/v1
kind: EgressIP
metadata:
  name: egressip-1
spec:
  egressIPs:
  - 172.18.0.33
  namespaceSelector:
    matchLabels:
      name: test
  podSelector:
    matchLabels:
      name: test-1
---

apiVersion: k8s.ovn.org/v1
kind: EgressIP
metadata:
  name: egressip-2
spec:
  egressIPs:
  - 172.18.0.44
  namespaceSelector:
    matchLabels:
      name: test
  podSelector:
    matchLabels:
      name: test-2

Actual results:
Only the first egress IP works

Expected results:
Both egressip-1 and egressip-2 should work


Note You need to log in before you can comment on or make changes to this bug.