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.

Sign up for GitHub

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

Jump to bottom

Ingresses can not be found on clusters running K8s 1.13 #51

Closed
djablonski-moia opened this issue Aug 20, 2019 · 3 comments
Closed

Ingresses can not be found on clusters running K8s 1.13 #51

djablonski-moia opened this issue Aug 20, 2019 · 3 comments
Labels
bug Something isn't working

Comments

@djablonski-moia
Copy link
Contributor




Describe the bug
When running popeye against a 1.13 cluster, in which the ingresses still need to have Γ piVersion: extensions/v1beta1`, it fails with the following message:

INGS (1 SCANNED)                                                               πŸ’₯ 1 😱 0 πŸ”Š 0 βœ… 0 0Ωͺ
β”…β”…β”…β”…β”…β”…β”…β”…β”…β”…β”…β”…β”…β”…β”…β”…β”…β”…β”…β”…β”…β”…β”…β”…β”…β”…β”…β”…β”…β”…β”…β”…β”…β”…β”…β”…β”…β”…β”…β”…β”…β”…β”…β”…β”…β”…β”…β”…β”…β”…β”…β”…β”…β”…β”…β”…β”…β”…β”…β”…β”…β”…β”…β”…β”…β”…β”…β”…β”…β”…β”…β”…β”…β”…β”…β”…β”…β”…β”…β”…β”…β”…β”…β”…β”…β”…β”…β”…β”…β”…β”…β”…β”…β”…β”…β”…β”…β”…β”…β”…
  Β· ingresses......................................................................................πŸ’₯
    πŸ’₯ the server could not find the requested resource.

To Reproduce
Steps to reproduce the behavior:

  1. Running a cluster with K8s 1.13, and existing ingresses, just run popeye -s ing
  2. See error

Expected behavior
Ingresses are being found & sanitized.

Versions (please complete the following information):

  • OS: Mac OSX Mojave (10.14.6)
  • Popeye [e.g. 0.4.3]
  • K8s [e.g. 1.13.0]

Additional context
I was able to fix this locally by using Ingress from k8s.io/api/extensions/v1beta1instead of k8s.io/api/networking/v1beta1, but this breaks compatibility with newer K8s versions. I don't know how to fix this properly... ☹️
@derailed derailed added the bug Something isn't working label Sep 15, 2019
@derailed
Copy link
Owner

@djablonski-moia Thank you for this report! I'll take a look and see how Popeye can support older resources. I think I have some ideas there. That said and given the various CVEs it might be wise to run newer k8s versions (if possible!!) as the Popeye currently does not scan for those (which could be a great addition...)

@derailed
Copy link
Owner

derailed commented Jan 7, 2020

@djablonski-moia Reverted to extensions group until networking is actually surfaced. Please see 0.6.0. Thank you!!

@derailed derailed closed this as completed Jan 7, 2020
derailed added a commit that referenced this issue Jan 8, 2020
@derailed
fix #46,#51,#60,#61,#62
5c44646
@calvinbui
Copy link

We use 1.13 on GKE as it's what Google considers 'stable'

Similarly I get the message to use networking which doesn't exist on 1.13

[POP-403] Deprecated Ingress API group "extensions/v1beta1". Use "networking.k8s.io/v1beta1" instead.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug Something isn't working
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@derailed @calvinbui @djablonski-moia