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

Editing a Listener and changing the spec.host field creates a new service, but does not remove the old one #1930

Open
granzoto opened this issue Jan 28, 2025 · 0 comments
Assignees

Comments

@granzoto
Copy link
Contributor

Describe the bug
Create a listener using spec.host equals to backend-ha, then edits the listener and changes its value to backend.
Check that a new service named backend is created, but the old one, named backend-ha was not removed

How To Reproduce
Create two skupper sites
Create an accessgrant and an accesstoken, establish the connection
Deploy a workload ( backend ) in one site
Create the proper connector and listener for the service/workload

From the listener definition :
spec:
host: backend-ha

services Created:
NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S)
backend-ha ClusterIP X.X.X.X <none> 8080/TCP

Edit the listener and change the spec.host field.

This should start the creation of a new service, and also remove the old service

New host address in the listener definition :
spec:
host: backend

The new service is created as expected, but the old one remains untouched
NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S)
backend ClusterIP X.X.X.X <none> 8080/TCP
backend-ha ClusterIP Y.Y.Y.Y <none> 8080/TCP

Expected behavior
The new service should be created and the old one should be removed

Environment details

  • Skupper Version : v2-dev
  • Platform : Minikube
@granzoto granzoto changed the title Editting a Listener and changing the spec.host field creates a new service, but does not remove the old one Editing a Listener and changing the spec.host field creates a new service, but does not remove the old one Jan 28, 2025
@grs grs self-assigned this Jan 28, 2025
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

2 participants