-
Notifications
You must be signed in to change notification settings - Fork 17
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
support newer ingress apiVersion #14
Conversation
@lewismc is it possible to backport this to the 1.26 version too? |
from K8s version 1.22 you can only access the ingress api via the stable 'networking.k8s.io/v1' API
d0f1234
to
58b55f0
Compare
@lewismc I've made some more changes that'll allow you to backport this to 1.26. This is ingress template is basically what you get when executing |
ping @lewismc - really keen to get this deployed! :) |
@lewismc can you at least let us know if this project is dead, so I can fork it for our organisation? |
Hi @euven sincere apologies. It is not dead I was on vacation for a month. I apologize. I am going to work on granting all contributors commit rights to remove myself as the sole point of failure in term of accepting and reviewing incoming contributions. Thanks for your patience and sorry. I'll review right now, hopefully merge and then make a release. |
Tested with
Thank you @euven . Now I can get to work on
|
@euven I pushed a release to Artifactory for 2.9.0 and 2.9.0-full. |
Thank you very much @lewismc and apologies for all the pings while you were away on holiday (hope you enjoyed it!) - glad to hear this project is alive and well :) |
from K8s version 1.22 you can only access the ingress api via the stable
networking.k8s.io/v1
API