Skip to content
This repository has been archived by the owner on Jan 22, 2021. It is now read-only.

Using a service name results in invalid port #32

Open
excieve opened this issue Dec 2, 2019 · 3 comments
Open

Using a service name results in invalid port #32

excieve opened this issue Dec 2, 2019 · 3 comments
Labels
bug Something isn't working stabilisation Issues required to stabilise the IC

Comments

@excieve
Copy link
Member

excieve commented Dec 2, 2019 •
edited
Loading

Using a service name instead of a port number in the ingress doesn't appear to resolve it and the API definition target ends up with port 0. Which also doesn't appear to be updated when changed in the ingress (controller doesn't detect that something's changed it seems).
@excieve excieve added the bug Something isn't working label Dec 2, 2019
@stale
Copy link

stale bot commented Mar 18, 2020

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs, please comment if you would like this issue to remain open. Thank you for your contributions.

@stale stale bot added the wontfix This will not be worked on label Mar 18, 2020
@stale stale bot closed this as completed Apr 1, 2020
@excieve
Copy link
Member Author

excieve commented Apr 13, 2020

This is not stale.

@excieve excieve reopened this Apr 13, 2020
@stale stale bot removed the wontfix This will not be worked on label Apr 13, 2020
@excieve excieve added the stabilisation Issues required to stabilise the IC label May 14, 2020
@joshblakeley
Copy link
Member

@excieve
Can you give an example ingress spec this happens for?

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
bug Something isn't working stabilisation Issues required to stabilise the IC
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@excieve @joshblakeley