Skip to content

Prefix tcpListener/tcpConnector names to avoid same-site collision with exposePodsByName. Added test in controller_test.go.#2381

Open
AryanP123 wants to merge 1 commit intoskupperproject:mainfrom
AryanP123:resource-name-fix
Open

Prefix tcpListener/tcpConnector names to avoid same-site collision with exposePodsByName. Added test in controller_test.go.#2381
AryanP123 wants to merge 1 commit intoskupperproject:mainfrom
AryanP123:resource-name-fix

Conversation

@AryanP123
Copy link
Contributor

Fixes #2058

…th exposePodsByName. Added test in controller_test.go

Fixes skupperproject#2058
Copy link
Contributor

@c-kruse c-kruse left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nice! This was a lot cleaner than I had initially thought.

I know it was me who suggested a resource-type.resource-name scheme, but I'd like to walk that back. We should definitely pick something that cannot be a in a k8s resource name. I'd lean towards /.

Also, the catch here that we should call out is that this does end up bubbling back to the user in site.status.network.services.listeners. Maybe not a deal breaker, but something we should be careful to consider and maybe document.

Thoughts on that @fgiorgetti?

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

Successfully merging this pull request may close these issues.

Listener and Connector in same site incompatible with exposePodsByName

2 participants