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

No clean-up when the egressip service is removed #23

Open
uablrek opened this issue Apr 2, 2019 · 1 comment
Open

No clean-up when the egressip service is removed #23

uablrek opened this issue Apr 2, 2019 · 1 comment

Comments

@uablrek
Copy link

uablrek commented Apr 2, 2019

When the service defined by service-name: in the StaticEgressIP is removed nothing is cleaned up. The egress-ip function remains fully operable.

Here is the manifest used;

apiVersion: v1
kind: Service
metadata:
  name: egressip-alpine
spec:
  selector:
    app: alpine
  ports:
  - name: probe
    port: 5001
---
apiVersion: staticegressips.nirmata.io/v1alpha1
kind: StaticEgressIP
metadata:
  name: egressip-alpine
spec:
  rules:
  - egressip: 15.0.0.13
    service-name: egressip-alpine
    cidr: 192.168.2.0/24

Then the service is removed with;

kubectl delete svc egressip-alpine
@uablrek
Copy link
Author

uablrek commented Apr 24, 2024

obsolete

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant