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

Feature request. Add checks for ingresses without Services. #2

Closed
kirill-korzun opened this issue Sep 9, 2019 · 3 comments
Closed
Assignees
Labels
enhancement New feature or request

Comments

@kirill-korzun
Copy link

Hi Emir,

This is pretty much a feature request rather than a bug; In our current environment we have a few dev clusters getting constant creation/deletion requests, and our CI isn't perfect, so time to time we face situation when we have a bunch of automatically created ingress objects being pointed to Service object don't exist anymore.

I'm just wondering if you can add such case to your sanity check steps and display/auto-delete ingress objects?

@emirozer
Copy link
Owner

emirozer commented Sep 9, 2019

great idea 👍

@emirozer emirozer self-assigned this Sep 9, 2019
@emirozer emirozer added the enhancement New feature or request label Sep 9, 2019
@emirozer
Copy link
Owner

emirozer commented Oct 8, 2019

note to self:

ingresses, err := kubeCli.NetworkingV1beta1().Ingresses(namespace).List(v1.ListOptions{})

packs a 404 in err. (with multiple unique clusters i tested with)

@emirozer
Copy link
Owner

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

No branches or pull requests

2 participants